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

Possible to change Xdialog window size depending on the condition?

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

  • Peter.Greulich
    replied
    Re: Possible to change Xdialog window size depending on the condition?

    Modify Al's code as follows:

    dlg_Header=<<%Header%
    {position=remember=Header}
    {can_exit=exit}
    Married:| (40married!married);
    %Header%

    That will provide a less jumpy version of what you are doing.

    Note that the word "Header" in "{position=remember=Header}" is completely arbitrary.

    Note: In Al's example he is using "3" xdialogs by concatenating code1 to code2 & 3. So if your case uses just 2 xdialogs put "{position=remember=Header}" in both.
    Last edited by Peter.Greulich; 10-26-2018, 11:04 AM. Reason: Typo

    Leave a comment:


  • Davidowicza
    replied
    Re: Possible to change Xdialog window size depending on the condition?

    Thank you Al, that will work!

    Thanks again everyone!

    Leave a comment:


  • Al Buchholz
    replied
    Re: Possible to change Xdialog window size depending on the condition?

    You can do this as a modeless dialog.

    Here is a simple example using Xdialog as a String from the help file as a basis.

    Import the attached code to your workspace, run the script xdialogasastring and click the married button on and off.

    Note the dialog name changes, and the dlg_body is rebuilt based on the logical variable married.

    xdialogasstring.txt
    Last edited by Al Buchholz; 10-26-2018, 11:38 AM. Reason: replaced the attached code with Peter's edit included.

    Leave a comment:


  • johnkoh
    replied
    Re: Possible to change Xdialog window size depending on the condition?

    Hi Andy,

    The End user may not like to change the way you want to do. They want to have the most simple one.

    I think, the {embedded} is your solution. It will open a child xdialog as you have designed.

    Leave a comment:


  • MoGrace
    replied
    Re: Possible to change Xdialog window size depending on the condition?

    If the list doesn't appear until the LIST button is clicked, then Allen's idea is the best solution (add some Help text), because it is not obvious what the dialog is for.

    Leave a comment:


  • Davidowicza
    replied
    Re: Possible to change Xdialog window size depending on the condition?

    Thanks again for the help, but I still don't think what I am looking for is possible. I wanted to the dialogue window size to change as the user clicked "Other" or "list" but would just change the current window size that they were on. Looks like for {include} I would need to know the condition the user wanted before the window is created, which I would not, and {embedded} would just be opening up another window.

    Leave a comment:


  • johnkoh
    replied
    Re: Possible to change Xdialog window size depending on the condition?

    Hi,

    Try this code. it is using the "{Include}" to show an xdlg.
    There is another way, using "{Embedded}"

    'condition ===
    vShowBoxType="full" 'show listbox
    vShowBoxType="ddwn"

    '======================

    'conditional xdlg and will apply it with {include}.
    'It is required the condition at initial stage of the open an xdlg
    if vShowBoxType ="full" 'show listbox
    dlgOpt=<<%dlg%
    Make:| [.40,5vehicle_make^#a_vehicle_make!vehicle_make_killfocus];
    Model:| [.40,5cModel^#a_model];
    Year:| [%z%.8nYr] <15 other_button!other> ;
    %dlg%
    else
    'show ddwn box
    dlgOpt=<<%dlg%
    Make:| [.40cMake2];
    Model:| [.40cModel2];
    Year:| [%z%.8nYr] <15 list_button!list>;
    %dlg%
    end if

    heading_string="sample with {include}"

    DLGBODY=<<%DLG%
    {region}
    {text=65,1:heading_string};
    {endregion};

    {region}
    {include=dlgOpt}
    {endregion};




    {region}
    Color:| [.20cColor];
    Plate:| [.15cPlate];
    State:| [4cState];
    Priority:| [.20,2cPriority^#a_cPriority];
    {endregion};
    {line=1,0};
    {region}
    <15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
    {endregion};
    %DLG%

    ui_dlg_box("test",dlgbody)

    Leave a comment:


  • Davidowicza
    replied
    Re: Possible to change Xdialog window size depending on the condition?

    Darn. Ok thank you!

    Leave a comment:


  • Allen Klimeck
    replied
    Re: Possible to change Xdialog window size depending on the condition?

    You can't remove the space but you could replace the controls with a logo or helpful text.

    Leave a comment:


  • Davidowicza
    replied
    Re: Possible to change Xdialog window size depending on the condition?

    Thanks for the fast response Ronald but that is what I am currently doing. The list boxes for "Make" and "Model" and the text fields for "Make" and "Model" are conditionally replacing each other (I just pushed the text fields down a bit to make it look better). I want to actually make the window height smaller when the text fields appear since it does not take up as much room as the list boxes.

    Here is my code if it helps:

    {condition=x}
    {region}
    {text=65,1:heading_string};
    {endregion};
    {region=a}
    Make:| [.40,5vehicle_make^#a_vehicle_make!vehicle_make_killfocus];
    Model:| [.40,5cModel^#a_model]
    {endregion}
    {condition=y}
    {start_pos}
    {region=a}
    {lf=19};
    Make:| [.40cMake2];
    Model:| [.40cModel2]
    {endregion};
    {condition_end}
    {region}
    Year:| [%z%.8nYr]
    {condition=x}
    {region=b}
    {sp=21}
    <8=other_button!other>
    {endregion}
    {condition=y}
    {start_pos}
    {sp=32}
    {region=b}
    <8=list_button!list>
    {endregion};
    {condition_end}
    Color:| [.20cColor];
    Plate:| [.15cPlate];
    State:| [4cState];
    Priority:| [.20,2cPriority^#a_cPriority];
    {endregion};
    {line=1,0};
    {region}
    <15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
    {endregion};

    Leave a comment:


  • Ronald Anusiewicz
    replied
    Re: Possible to change XDialogue window size depending on the condition?

    This may help, from xDialog help files.

    https://documentation.alphasoftware....20controls.xml

    Leave a comment:


  • Possible to change Xdialog window size depending on the condition?

    Hello all!

    As I have been only working with alpha for about 4 months now, I am curious if it is possible to change the size of the window for Xdialogue boxes depending on the condition?

    It would just been more aesthetic to have the window not show huge blank areas whenever I have a condition that does not fill the previous conditions space.

    Example:

    dlgbox1.PNG

    dlgbox2.PNG

    As you can see there is a big blank area that I would like to hide when the condition changes.
Working...
X