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

resizing or maximizing xdialog

  • Filter
  • Time
  • Show
Clear All
new posts

  • resizing or maximizing xdialog

    I am trying to maximize an xdialog to the current size of the Alpha5 window (whatever the current size happens to be)... but the maximize fills the entire screen and not just Alpha window size. The resize function does not seem to work (bug submitted). Here's my code:

    ui_modeless_dlg_box("Visible Xdialog", <<%dlg%
    <close> <resize> <maximize>

    if a_dlg_button="resize" then 'resize does not seem to work -submitted bug report
    ui_dlg_resize("Visible Xdialog",20,30)
    end if

    if a_dlg_button="maximize" then
    ui_dlg_maximize("Visible Xdialog")
    end if

    if a_dlg_button="close" then
    ui_modeless_dlg_close("Visible Xdialog")
    end if

  • #2
    Re: resizing or maximizing xdialog

    Maybe this will give someone else a hint and they will get farther than I did. (In other words, I couldn't find a way either.)

    I tried various things including using these functions to get current window sizes:


    The problem with the "size_get" function is that it returns "maximized" when maximized rather than the actual size. However, the size returned is in inches anyway so it isn't much use when everything else uses pixels.

    A minor comment on the code in your %Code% section:

    You used a series of IF statements and there is nothing wrong with that but in this case a series of ELSEIF statements would actually be clearer. The ELSEIF clarifies that only one of the statements will be true - or, if multiple statements might be true then only the first one will be acted on.

    This isn't a big deal until you (a) have to edit the code after not seeing it for a few months and (b) have a situation where one of the actions (typically the last one) is required to be a separate IF. For example, I have occasionally had to build %Code% for a modal xdialog where the value of a_dlg_button might get changed based on some other action and then a_dlg_button MUST be checked at the end for that value. In that case it's not obvious what's happening if it is just a series of IF statements. However, something like this makes it clearer:

    IF a=b
    <do something>
    ELSEIF a=c
    <do something else>
    ELSEIF a=d
    <do something else>
    ELSEIF a=e
    <do something else>
    <do something else>
    a_dlg_button = "OK"
    END IF

    IF a_dlg_button = "OK"
    <run validation checks>
    END IF

    When I see something like the above with a separate IF, it's a pretty good hint that something special is going on somewhere in the above ELSEIF routines. Without that separate IF I might never think to look above for a change to a_dlg_button since that's not a typical think to do. In most cases the a_dlg_button would only be "OK" if the user clicked the OK button but, in this case, there is one situation where a_dlg_button gets changed to "OK" in the previous code even though the OK button was not clicked.

    Of course, the above is only a suggestion. It isn't required and it doesn't make a lot of difference at the time you are writing the code. However, it is better coding technique and, although I personally never have to go back and edit code, I understand that many developers do and it can be a lot easier to decipher your original intent when you use ELSEIF when that's what you really intended anyway. (And, yes, those who prefer it can use SELECT .. CASE instead.)

    FWIW, it should also run a few milliseconds faster because it doesn't have to evaluate every IF statement after finding the first match. (Which usually won't matter unless it's in a loop that runs many times.)


    • #3
      Re: resizing or maximizing xdialog

      Same results regarding the xdialog resize function.

      If wanting the Alpha window size you can use the following to determine it even if maximized....
      = -4
      = -4
      = 1032
      = 742
      which makes the size 1028 x 738
      If ever needing to compare pixels and inches Alpha provides the following functions--not a direct conversion is all.
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau


      • #4
        Re: resizing or maximizing xdialog

        Thanks Mike! Now I just need to wait for the next update which, according to Selwyn, corrects the presently non-functioning ui_dlg_resize() function. :)