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

Radio Buttons of Xdialog Acting Weird

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

    Radio Buttons of Xdialog Acting Weird

    Hi All,

    Not being a big fan of ask variables, I typically just use one screen to get all the parameters I need for a printing from a list of reports/letters. In doing so, different layouts may prompt differently for date variables (e.g. "Date on Letter" vs "Service Start Date"). In the script below you will see that when you change the report selection the date prompts will change in wording as well as availability.

    Code:
    dim choices as C 
    DIM SHARED View_Print as C
    DIM SHARED nChoice as N
    DIM SHARED dFrom as D
    DIM SHARED dTo as D
    DIM SHARED dReport as D
    DIM SHARED dDatePrompt as C
    DIM shared bFrom as L
    DIM shared bTo as L
    DIM shared bReport as L
    DIM SHARED varC_result as C
    dim cNum as C
    choices=<<%ccc%
    Confirmation of Services
    Termination of Services
    Care Plan
    Transportation Request
    Blank Transportation Request
    While I Was Out
    Request for CCPED 100% Slot
    %ccc%
    nChoice = 1
    cNum = "1"
    bFrom = .F.
    bTo = .F.
    bReport = .T.
    cDatePrompt = "Service Start Date:"
    View_Print = "Print"
    ok_button_label = "&OK"
    cancel_button_label = "&Cancel"
    varC_result = ui_dlg_box("CCPED Provider Letters/Reports",<<%dlg%
    {region}
    {region}Print Option:{endregion}|
    {region}(View_Print:View);
    (View_Print:Print);{endregion};
    ;
    {region}Which Report:{endregion}|
    {region}(nChoice=choices!nChoices_*);{endregion}; 
    ;
    {region}{text=2,0cNum};{endregion};
    {text=20,0cDatePrompt}|	[%DATE;P=popup.calendar(dtoc(dReport));I=popup.calendar%.20dReport!dReport_*?bReport];
    From Date:|	[%DATE;P=popup.calendar(dtoc(dFrom));I=popup.calendar%.20dFrom!dFrom_*?bFrom];
    To Date:|	[%DATE;P=popup.calendar(dtoc(dTo));I=popup.calendar%.20dTo!dTo_*?bTo];
    {endregion};
    {line=1,0};
    {region}
    <*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
    {endregion};
    %dlg%,<<%code%
    if left(a_dlg_button,6) = "dFrom_" then 
    	if a_dlg_button = "dFrom_killfocus" then 
    		dFrom = ctod(dtoc(dFrom))
    	end if 
    	a_dlg_button = ""
    end if 
    if left(a_dlg_button,4) = "dTo_" then 
    	if a_dlg_button = "dTo_killfocus" then 
    		dTo = ctod(dtoc(dTo))
    	end if 
    	a_dlg_button = ""
    end if
    if left(a_dlg_button,8) = "dReport_" then 
    	if a_dlg_button = "dReport_killfocus" then 
    		dReport = ctod(dtoc(dReport))
    	end if 
    	a_dlg_button = ""
    end if 
    if left(a_dlg_button,9) = "nChoices_" then 
    	bFrom = .F.
    	bTo = .F.
    	bReport = .F.
    	cNum = alltrim(str(nChoice))
    	if nChoice = 1 .OR. nChoice = 4
    		bReport = .T.
    		cDatePrompt = "Service Start Date:"
    	else if nChoice = 2 .OR. nChoice = 7
    		bReport = .T.
    		cDatePrompt = "Letter Date:"
    	else if nChoice = 3
    		bFrom = .T.
    		bTo = .T.
    		bReport = .T.
    		cDatePrompt = "Client Approval Date:"
    	else if nChoice = 6
    		bFrom = .T.
    	end if 
    	a_dlg_button = ""
    end if
    %code%)
    Problem:
    When I select a report type by use of a mouse click all works fine. However, when I use the up & down arrows to navigate up and down the list, the choice number (nChoice) is thrown off. Is this a bug of V5? For testing purposes I added the choice number as a character just below the radio buttons. Since this script is not tied to a table or set, it can be run directly with no further downloads.

    Does it behave this way for other users? If so, is there a way to disable the up/down keys while in the Xdialog? Thanks in advance.

    Steve

    #2
    Re: Radio Buttons of Xdialog Acting Weird

    To be specific, with the above code select "Termination of Services" using your mouse. Upon doing so you will notice a "2" just below the radio buttons correctly indicating that nChoice = 2. Also, only the first date prompt will be enabled and labeled "Letter Date".

    Now select the third choice ("Care Plan") using your mouse. Upon doing so, all three date prompts will be enabled with the first one reading "Client Approval Date". Also, a "3" will appear below the radio buttons indicating that nChoice = 3.

    Now repeat the first step of selecting "Termination of Service" by use of the mouse. Then press the down arrow key once. You will notice that the report/letter selection has properly changed to the "Care Plan" selection. However, it behaves otherwise as if "Termination of Services" was selected: (a) the number below the radio buttons remains a "2", (b) only the first date prompt is enabled and (c) the first date prompt is labeled "Letter Date".

    Hence, while the arrow keys change the selection of the radio button insofar as the display, they do not seem to change the value of the associated variable.

    Comment


      #3
      Re: Radio Buttons of Xdialog Acting Weird

      While I do think that this is a bug of V5, I have gotten a workaround by replacing the radio buttons with a list box. When using the list box, it works correctly whether I select the report type with a mouse click or with up/down arrow keys.

      Comment

      Working...
      X