Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



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

Screen Layout Design

  • Filter
  • Time
  • Show
Clear All
new posts

  • Screen Layout Design

    This is a pretty mundane question, I think. But, I am curious for a reason.

    When designing forms and their positioning on a computer screen, do most people leave the calling form open or close it, thus avoiding a multitude of open forms on the screen.

    Along with that, I am also curious about those making a living with Alpha application design, what is the typical computer (not mobile) monitor size encountered?

  • #2
    Re: Screen Layout Design

    I think the most common is 1024X768 BUT you will need to think about your users to really answer that. I think the best approach is to use a UX and a list control. You can use responsive layouts for the UX itself and multiple layouts for the list control. For me this seems to be the best approach because you can account for nearly all screen sizes as well as portrait and landscape making your application work on almost any device. I posted some responsive layout settings in another thread should be easy to search and find here if your interested. If you design for both from the get go - you'll save yourself a ton of work in the future if you ever decide you want to make it responsive!
    NWCOPRO: Nuisance Wildlife Control Software My Application: "Without forgetting, we would have no memory at what was I saying?"


    • #3
      Re: Screen Layout Design

      This may help?
      Glen Schild

      My Blog


      • #4
        Re: Screen Layout Design


        Other certainly seems to be the growing resolution.


        • #5
          Re: Screen Layout Design

          So, when calling forms, and taking into consideration a good user experience, what do most Alpha Designers do?

          Do the leave open, minimize, or close forms when calling? Is there any thing that suggests end users have one preference over another? Larger screen resolution numbers certainly give more options for leaving multiple screens open on the screen. Wouldn't that tend to have a total screen layout looking like a jigsaw puzzle? And I guess leaving them all open would possibly necessitate smaller font resolutions so us old folks have get right next to the screen.


          • #6
            Re: Screen Layout Design

            Since this was posted in desktop. UX is not a normally used solution, Most of my clients use 19" to 22" monitors, so I test all applications on a 17" laptop and feel the client will be compfortable.

            I make a lot of apps and/or repair same.

            I generally do not worry about whether past forms are closed except where a client has limited memory/diskspace.
            Dave Mason
            Skype is dave.mason46


            • #7
              Re: Screen Layout Design

              Thanks Dave.

              Do you leave them open on screen or minimize when deactivated and let the end user "find" them while minimized to reactivate them?


              • #8
                Re: Screen Layout Design

                I leave the little tabs open at the bottom on most apps so user can click to go from one to another, mostly
                Last edited by DaveM; 03-10-2019, 08:35 PM.
                Dave Mason
                Skype is dave.mason46


                • #9
                  Re: Screen Layout Design

                  I only leave the calling form open if it is a form mostly used for searching and displaying data. If the user wants to edit the selected record, I use a pop up form that the user must close when finished to return to the calling form. Navigation is usually restricted on the pop up form. In the case where I have a basic form that calls a more detailed view, then when the detail is opened I close the calling form if it is using the same table.

                  I also have a toolbar that I dock on the right side of the screen to show the open window list instead of using the window bar tabs at the bottom. And I do not use maximized forms ever, instead my windowed forms are sizeable.

                  But then I am a Quickbooks fan and like their UI for the desktop and have tried to mimic some of their features - however QB leaves everything open so the user must specifically close a form.

                  As for resolution, I favor smaller forms with larger fonts between 10-12 pts. But it all really depends on the type of application you are developing.

                  This is how my Payroll app looks when first opened:

                  Last edited by MoGrace; 03-14-2019, 12:45 AM.

                  Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford