Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Help information on the use of "ControlGroup" container...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Help information on the use of "ControlGroup" container...

    Where can I find direct information concerning the various types of containers, when and where their events apply, how they affect the alignment of child elements, and assignment of events?

    These seem to be important topics, but nothing turns up with explicit information on the forums, help documentation, wiki, or video library.

    There appear to be several thousand other poorly documented topics as well.

  • #2
    Re: Help information on the use of "ControlGroup" container...

    Originally posted by mbunds View Post
    Where can I find direct information concerning the various types of containers, when and where their events apply, how they affect the alignment of child elements, and assignment of events?

    These seem to be important topics, but nothing turns up with explicit information on the forums, help documentation, wiki, or video library.

    There appear to be several thousand other poorly documented topics as well.
    Hello Mark,

    The "Explain Different Container Types" link in the Insert Container dialog will show you documentation for the different containers. The ControlGroup container changes the styling used to render the controls within it. It hides the border around the input controls and adds a divider line between each row of controls.

    Specifically, the ControlGroup adds a div around all the controls in the container with the class {dialog.style}ControlGroup and places each row of controls inside another div with the class {dialog.style}ControlGroupRow. The first row in the group also has the class {dialog.style}ControlGroupRowFirst. These classes are defined in the stylesheet for the UX Component. We recently published a video about applying custom CSS to the UX Component. It may or may not be of interest to you depending on what you're trying to accomplish: http://www.alphasoftware.com/video-l...t&search=style

    The "Containers" video provides an overview of all of the containers with the exception of Editor and EditorSet, which were added after this video was produced: http://www.alphasoftware.com/video-library/?v=3883

    Are you running into a specific issue? What are you trying to build?
    Sarah Mitchell
    Documentation | Alpha Software Corporation
    Get in the know! Join us for our Weekly Webinars: TransForm Tuesday and Wednesday's Alpha Anywhere Demo and Q&A
    Connect with us: Instagram | Twitter | Facebook | LinkedIn | YouTube

    Comment


    • #3
      Re: Help information on the use of "ControlGroup" container...

      Great Info, thanks!

      Originally posted by Beta Spark View Post
      Are you running into a specific issue?
      - Just my ignorance of the product!

      The custom CSS styles video is of great interest, and was responsible for helping me adjust the button and container styles (and I also totally hosed my .sass by placing an incompatible gradient style rule into the .css editor, so I learned way more than the video illustrated!)

      I am building a custom on-screen keyboard that is driven differently from the one created for the example videos. As elegant as the keypads in sample application are, they're too abstracted and integrated with the inspection project to use as a "drop-in" under the menu structure I am using which is based on an Alpha-supplied template.

      I have examined some excellent JavaScript OSK's by others, but the better ones tend to be a bit "heavy" since they have numerous features, and multiple localization files that are not needed for our project.

      By far, my largest goal is to get a better handle on passing data around, but a close second is to get layout and styling under control. While I was experimenting with the different container types, I noticed that the layout and/or styles of certain controls changed slightly, and I assumed this was due to the purposes for which Alpha built each container, but I really didn't see where to get detailed information.

      Your response has provided the epiphany I needed to get (this particular part of) the project under control, and for that I thank you!
      Last edited by mbunds; 05-11-2016, 03:29 PM. Reason: Inserted quote...

      Comment


      • #4
        Re: Help information on the use of "ControlGroup" container...

        Originally posted by mbunds View Post
        Great Info, thanks!

        - Just my ignorance of the product!

        The custom CSS styles video is of great interest, and was responsible for helping me adjust the button and container styles (and I also totally hosed my .sass by placing an incompatible gradient style rule into the .css editor, so I learned way more than the video illustrated!)

        I am building a custom on-screen keyboard that is driven differently from the one created for the example videos. As elegant as the keypads in sample application are, they're too abstracted and integrated with the inspection project to use as a "drop-in" under the menu structure I am using which is based on an Alpha-supplied template.

        I have examined some excellent JavaScript OSK's by others, but the better ones tend to be a bit "heavy" since they have numerous features, and multiple localization files that are not needed for our project.

        By far, my largest goal is to get a better handle on passing data around, but a close second is to get layout and styling under control. While I was experimenting with the different container types, I noticed that the layout and/or styles of certain controls changed slightly, and I assumed this was due to the purposes for which Alpha built each container, but I really didn't see where to get detailed information.

        Your response has provided the epiphany I needed to get (this particular part of) the project under control, and for that I thank you!
        Any time, Mark!

        A lot of documentation is scattered about in various locations - release notes, the wiki, help boxes in the product, pdfs, etc. We are actively pulling all documentation for the product into one central location.

        I did pass on your request for a keyboard editor. We are investigating how best to provide a custom keypad/keyboard control. Thanks!
        Sarah Mitchell
        Documentation | Alpha Software Corporation
        Get in the know! Join us for our Weekly Webinars: TransForm Tuesday and Wednesday's Alpha Anywhere Demo and Q&A
        Connect with us: Instagram | Twitter | Facebook | LinkedIn | YouTube

        Comment


        • #5
          Re: Help information on the use of "ControlGroup" container...

          Originally posted by Beta Spark View Post
          I did pass on your request for a keyboard editor. We are investigating how best to provide a custom keypad/keyboard control. Thanks!
          In hindsight, a "native Alpha" OSK replacement keyboard is probably the very first "TOF" add-on feature that should have been explored.

          I noticed early on that the the native OSK's on mobile devices were going to cause formatting and layout flow problems, but I assumed this was pretty much a "given," and Alpha had a handle on it.
          I can see now that this is no small order; the keyboard that works for MY project is going to fall short of someone else's needs, and when a "one-for-all" keyboard is completed, it will likely be too bloated for smaller projects.

          For the HMI touch-screen PC's on our drilling rigs, I created a universal keyboard containing its own display field. The program could call the keyboard into view, passing arguments that told the keyboard how to configure itself, how to validate input, and where the results were to be stored. This keyboard could appear as a plain number pad, hexadecimal number pad, calculator, set point entry pad, user/password entry, and various alphabetic keyboards:

          image012.png
          image011.png
          image027.png
          image028.png

          I can't find any screen shots of the keypad in calculator mode, but the full-alpha keyboard and the set-point entry keypad are the same project, using dynamic rendering of all controls, surfaces, and text. The borders, buttons, insets, and the "carbon-fiber" background are all generated procedurally on-the-fly the first time a mode-instance is launched, and then re-served from a cache of "baked" images for subsequent calls, unless the "fixed" control graphics are edited or otherwise changed.

          It was built using Microsoft Expression "Blend" which is a graphical WPF editor that served as the WPF screen/window/graphics front end for Visual Studio (now integrated), and it used MS C# .NET for its code-behind, and despite its flexibility, it was very lightweight and responsive.

          And not at all compatible with non-Windows mobile devices.

          Of course, we weren't fighting with any kind of native OSK, but this is the kind of thing I am working on for this project (minus the fancy animations included in the WPF project), and intend to make it easy to apply to other projects also.

          The first effort goes into creating a monolithic UX component that expands or contracts to the keyboard configuration desired. If that gets too heavy (or even if it doesn't), it will be split into modular sections that can be used in place of the master when all that functionality is not needed.

          Here's what I have so far:

          MRI_SW_SMALL.png

          Besides what you see here, the project has a few functional panel cards with text input controls performing look-ups, along with their list controls that perform filtering for other lists, but we have a long way to go from here. Right now, the keypad more-or-less "embedded" on this page, and simplistic as it is, it is beautiful now that you advised me about the layout (those buttons were scattered all over the screen before).

          The basic keys for "Employee ID" input are the only ones visible here, but it does have hidden sections containing buttons for basic operators, and the mating "FWD" pointer button is hidden in a container with the "Enter" button which shows after the user has input 5 characters. The control elements will be copied to an independent UX for further development after their basic functionality and style has been detailed a bit more.

          Comment


          • #6
            Re: Help information on the use of "ControlGroup" container...

            Originally posted by mbunds View Post
            In hindsight, a "native Alpha" OSK replacement keyboard is probably the very first "TOF" add-on feature that should have been explored.

            I noticed early on that the the native OSK's on mobile devices were going to cause formatting and layout flow problems, but I assumed this was pretty much a "given," and Alpha had a handle on it.
            I can see now that this is no small order; the keyboard that works for MY project is going to fall short of someone else's needs, and when a "one-for-all" keyboard is completed, it will likely be too bloated for smaller projects.

            For the HMI touch-screen PC's on our drilling rigs, I created a universal keyboard containing its own display field. The program could call the keyboard into view, passing arguments that told the keyboard how to configure itself, how to validate input, and where the results were to be stored. This keyboard could appear as a plain number pad, hexadecimal number pad, calculator, set point entry pad, user/password entry, and various alphabetic keyboards:

            [ATTACH=CONFIG]42009[/ATTACH]
            [ATTACH=CONFIG]42010[/ATTACH]
            [ATTACH=CONFIG]42011[/ATTACH]
            [ATTACH=CONFIG]42012[/ATTACH]

            I can't find any screen shots of the keypad in calculator mode, but the full-alpha keyboard and the set-point entry keypad are the same project, using dynamic rendering of all controls, surfaces, and text. The borders, buttons, insets, and the "carbon-fiber" background are all generated procedurally on-the-fly the first time a mode-instance is launched, and then re-served from a cache of "baked" images for subsequent calls, unless the "fixed" control graphics are edited or otherwise changed.

            It was built using Microsoft Expression "Blend" which is a graphical WPF editor that served as the WPF screen/window/graphics front end for Visual Studio (now integrated), and it used MS C# .NET for its code-behind, and despite its flexibility, it was very lightweight and responsive.

            And not at all compatible with non-Windows mobile devices.

            Of course, we weren't fighting with any kind of native OSK, but this is the kind of thing I am working on for this project (minus the fancy animations included in the WPF project), and intend to make it easy to apply to other projects also.

            The first effort goes into creating a monolithic UX component that expands or contracts to the keyboard configuration desired. If that gets too heavy (or even if it doesn't), it will be split into modular sections that can be used in place of the master when all that functionality is not needed.

            Here's what I have so far:

            [ATTACH=CONFIG]42013[/ATTACH]

            Besides what you see here, the project has a few functional panel cards with text input controls performing look-ups, along with their list controls that perform filtering for other lists, but we have a long way to go from here. Right now, the keypad more-or-less "embedded" on this page, and simplistic as it is, it is beautiful now that you advised me about the layout (those buttons were scattered all over the screen before).

            The basic keys for "Employee ID" input are the only ones visible here, but it does have hidden sections containing buttons for basic operators, and the mating "FWD" pointer button is hidden in a container with the "Enter" button which shows after the user has input 5 characters. The control elements will be copied to an independent UX for further development after their basic functionality and style has been detailed a bit more.
            Wow! Your keyboard and keypads look fabulous.

            This is great feedback, Mark! Thank you!
            Sarah Mitchell
            Documentation | Alpha Software Corporation
            Get in the know! Join us for our Weekly Webinars: TransForm Tuesday and Wednesday's Alpha Anywhere Demo and Q&A
            Connect with us: Instagram | Twitter | Facebook | LinkedIn | YouTube

            Comment

            Working...
            X