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

xdialogs and entry

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

    xdialogs and entry

    I love the xdialog, but...

    One of the big factors in choosing alpha was the ability to "enter" through the tab order.

    Is there a way to get an xdialog to accept enters without closing?

    I put an xdialog in my app as a start up for username + password + a checkbox if a print was needed. 3 months later the users hate it because they have to use the tab key. They put in their user name hit enter to go to password and get tossed out of the program(which it should).
    Dave Mason
    [email protected]
    Skype is dave.mason46

    #2
    Re: xdialogs and entry

    Dave

    In your xdialog code take the "*" from in front of the OK button

    Code:
    'Create an XDialog dialog box to prompt for parameters.
    DIM SHARED Cust_id as C
    DIM SHARED cust_name as C
    DIM SHARED cust_contact as C
    DIM SHARED varC_result as C
    ok_button_label = "OK"
    cancel_button_label = "Cancel"
    varC_result = ui_dlg_box("Alpha Five",<<%dlg%
    {region}
    Enter Cust Id:| [.40Cust_id];
    Enter Customer Name:| [.40cust_name];
    Enter Customer Contact:| [.40cust_contact];
    {endregion};
    {line=1,0};
    {region}
    [COLOR="Red"]<15=ok_button_label!OK> <15=cancel_button_label!CANCEL>[/COLOR]
    {endregion};
    %dlg%)

    You can then use the enter key for movement through the xdialog

    Tom Baker

    Comment


      #3
      Re: xdialogs and entry

      Tom,

      Thanks! I will try it tomorrow
      Dave Mason
      [email protected]
      Skype is dave.mason46

      Comment


        #4
        Re: xdialogs and entry

        Dave, I hope Tom's right cause it sure sounds easier than what I recall having to do long ago. It's been a year since I worked with this but I recall having to trap the enter key with the {on_key} statement, and then shift focus dynamically using code in the xdialog. -- tom

        Later on...

        Here's an example I worked up for Martin 2 years ago. Time flies.

        Code:
        'Date Created: 07-Jan-2006 08:00:59 AM
        'Last Updated: 03-Feb-2008 01:43:56 PM
        'Created By  : Test1
        'Updated By  : Tom Cone Jr
        
        '----------------------------------------------------------------------
        'Illustration:  Use of ENTER key to tab through objects in an xdialog
        '----------------------------------------------------------------------
        
        
        'Martin, the basic strategy is to use the {On_Key} event to trap each Enter keystroke
        '        then have the script check to see which object has focus.  If it's a button
        '        do nothing.  If it's an input field, shift focus to the next field or
        '        object you want.  Sort of like manually building your own tab order in a form.
        
        DIM SHARED beginning as N
        DIM SHARED ending as N
        DIM SHARED varC_result as C
        ok_button_label = "&OK"
        cancel_button_label = "&Cancel"
        varC_result = ui_dlg_box("Changing Page Numbers",<<%dlg%
        {on_key=enter}	 {Comment=enter key treated like tab key, except for buttons}
        {region}
        Enter Beginning Page Number:| [%z%.4beginning];
        Ending Page Number:| [%z%.4ending];
        {endregion};
        {line=1,0};
        {region}
        <*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
        {endregion};
        %dlg%,<<%code%
        Reprocess_Keystroke:
        Select
        	Case "OK"$ui_dlg_ctl_current("Changing Page Numbers")   'OK button has focus
        	    if a_dlg_button = "enter" then	'ENTER was pressed, pass the OK on through
        	    	a_dlg_button = "&OK"
        	    end if
        	    
        	case "Cancel"$ui_dlg_ctl_current("Changing Page Numbers")  'Cancel button has focus
        	    if a_dlg_button = "enter" then	'ENTER was pressed, pass the Cancel on through
        	    	a_dlg_button = "&Cancel"
        	    end if
        	    
        	case "beginning"$ui_dlg_ctl_current("Changing Page Numbers")  'beginning control has focus
        	    if a_dlg_button = "enter" then	'ENTER was pressed, shift focus to ending control
        	    	a_dlg_button = ""  'prevent dialog from closing
        	    	ui_dlg_ctl_goto("Changing Page Numbers","[%z%.4ending]")
        	    end if	    
        
        	case "ending"$ui_dlg_ctl_current("Changing Page Numbers")  'ending control has focus
        	    if a_dlg_button = "enter" then	'ENTER was pressed, shift focus to OK button control
        	    	a_dlg_button = ""  'prevent dialog from closing
        		ui_dlg_ctl_goto("Changing Page Numbers","<*15=ok_button_label!OK>")
        		sys_send_keys("{TAB}")  'special handling required when moving focus to button
        	    end if	   
        End Select
        
        
        %code%)
        if varC_result = "OK"
        	ui_msg_box("","user clicked OK to close the dialog.  Begin pg no is: "+ltrim(str(beginning)))
        	end
        elseif varC_Result = "Cancel" then
        	ui_msg_box("","User clicked CANCEL to close the dialg")
        	end 
        end if
        Last edited by Tom Cone Jr; 02-03-2008, 02:47 PM. Reason: include sample code

        Comment


          #5
          Re: xdialogs and entry

          Here is the testing code

          It an exported script.

          I have tried it and it works.


          Tom Baker

          Comment


            #6
            Re: xdialogs and entry

            Tom and Tom.

            It worked great! Just removed the "*".
            Dave Mason
            [email protected]
            Skype is dave.mason46

            Comment

            Working...
            X