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

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

Maximizing form window

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

    Maximizing form window

    I have several main forms that I am trying to keep maximized all of the time they have focus. To do so I have set an oninit event for each form to maximize window. (Note: I have also removed all toolbars, etc., from the main forms to give kind of a "clean page" look.)

    My problem is that one of the forms has a button that pops up a little form with an embedded browse. I have set the popup to only fill a small amount of the screen (so that most of the data on the underlying form can still be viewed). When I close the popup window, the underlying form is no longer maximized. I know that general behavior of windows in alpha is to be maximized if the preceding form was maximized, and not if the preceding window was not. However, I am hoping that there is some way around that.

    As usual, any suggestions would be appreciated. This forum is terrific.

    #2
    RE: Maximizing form window

    Instead of the oninit event, use the onactivate or have the try having the onexit of the "little form" maximize the main form.
    There can be only one.

    Comment


      #3
      RE: Maximizing form window

      1) Did you use Xbasic or the dialog genie to create the button? If the genie, a form can be opened as a dialog w/o putting code on the form's OnInit and OnActivate events. Works for me all the time, every time.

      2) Try compacting the database.

      3) Look at all the forms' events, etc and check your code. Is there anything that minimizes a form?

      4) When you are in the control panel, did you set the database properties by clicking File and then Database Properties. One of the options is a check box for maximizing A5. I check this as a matter of SOP.

      My forms are all maximized unless I put a button on a form to open another form as a 'dialog'. It pops up on the screen with the previous form in the background. The previous form does not change in size.

      Assuming you've done the above and it's not helping, the best way to isolate a problem like this is by trial and error. Try this:

      1) Put a button on a form that has the tool bar, etc and, using the genie, add the codes to open the form as a hidden dialog. You will need the following snippits:

      a. Open Form/Browse - You will need to select 'another form' and set the options tab to hidden dialog.
      b. Activate Form/Browse - Again, select another form option.
      c. Show the Form/Browse - Again, select another form option.

      Depending on what the form is supposed to show or do, you may need to add other snippits as well such as setting a field value or entering a new record, etc.

      Hope this helps,

      kenn
      TYVM :) kenn

      Knowing what you can achieve will not become reality until you imagine and explore.

      Comment


        #4
        RE: Maximizing form window

        Ken,

        Your suggestion about opening the form as a dialog seems to be the secret handshake for this problem. I tried the other workarounds without success, but modal dialog box works beautifully.

        It did take me a few minutes to figure out that I would need to add a button to my form to be opened as a dialog. Since that form is "all about the browse" and not about buttons, I added an invisible button that does nothing. That did it, the error message from xdialog disappeared and viola.

        Thanks again.

        Bob

        Comment


          #5
          RE: Maximizing form window

          Ken,

          If I could ask a follow-up question. Opening the form as a dialog works great for handling the screen positions, etc., but how do I get the data on the popup form to match with the data on the calling form? When I open as a regular window there is an option to match the data on the called form with a field on the calling form, but there is no such option (that I have seen anyway) when opening as a dialog.

          Thanks.

          Bob

          Comment


            #6
            RE: Maximizing form window

            Answered my own question. I will post here in case anyone else ever needs the information. If you create the popup dialog through the xdialog action scripting event, you must have a button on the form (even an invisible one), and you have fewer options that if you create it through the "open form or browse" action scripting event. If you use the latter, one of the choices (behind the "options" tab) is to open as a dialog box. If you choose that, you don't need a button on the form and you now have the lovely list of options that includes drawing the focus of the called form to the same record as in the calling form.

            And, of course, the popup form as a dialog does not mess the maximization of the calling form, which was the point of the whole thing from the beginning.

            Comment

            Working...
            X