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

xdialog auto advance and size of fields

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

    xdialog auto advance and size of fields

    I have three variables on an xdialog, all two characters long.

    Is it possible to have an autoadvance feature on the form, so that when the field is filled, it skips to the next field.

    Also, is it possible for the enter key to be used to move onto each field if required instead of tab, currently enter closes the form (it is focused on the ok button).

    Also! can I increase the visible width of the field rather than the actual width, so its still two characters in size, but larger on the form (as its rather cut off).
    Chris Tanti
    Technical Support

    Nuance & Fathom Ltd - The data-driven marketing agency

    #2
    RE: xdialog auto advance and size of fields

    Chris

    The answer to question 3, 5.10 will limit you to input 5 characters but the field will 10 characters wide.

    Sorry I cant help with the other points at this time.

    Keith Hubert
    London.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


      #3
      RE: xdialog auto advance and size of fields

      Thanks,

      Works great.
      Chris Tanti
      Technical Support

      Nuance & Fathom Ltd - The data-driven marketing agency

      Comment


        #4
        RE: xdialog auto advance and size of fields

        Chris:

        Auto advance is set in the field rules.

        From the control panel 'Table/Sets' tab, right click the table or set in question.

        Choose 'Edit Field Rules'.

        Click on the 'Data Entry' tab.

        Choose the field you wish to auto advance.

        Check off the 'Auto Advance' checkbox.

        Repeat the last two steps for any and all fields you wish.

        Comment


          #5
          RE: xdialog auto advance and size of fields

          George,

          That only applied to table data entry.
          My problem is with XDialog generated screens, a different thing altogether.
          Chris Tanti
          Technical Support

          Nuance & Fathom Ltd - The data-driven marketing agency

          Comment


            #6
            RE: xdialog auto advance and size of fields

            you have to use the key-trapping features of xdialog and do a lot of coding yourself. here is a short example that illustrates some of the issues you brought up:

            dim Address_1 as c
            dim Address_2 as c
            dim Dob as d
            dim First_Name as c
            dim Home_Phone as c
            dim Last_Name as c
            dim Marital as c
            dim Middle_Ini as c
            dim Sex as c

            sex_list=

            %list%

            control_count=w_count(controls_list,crlf())
            'ui_msg_box("control_count",""+control_count)
            dim control_array[control_count] as c
            control_array.initialize(controls_list)

            exclude=
            {endregion1};
            %dlg%,"
            a_dlg_button="Cancel"
            case else
            a_dlg_button=""
            curr_ctrl_number=control_array.find(curr_ctrl)
            if curr_ctrl_number=control_count then
            curr_ctrl_number=0
            end if
            next_control=control_array[curr_ctrl_number+1]
            next_control=left(next_control,len(next_control)-1)
            next_control=word(next_control,1,"!")
            next_control=word(next_control,1,"^")
            next_control=word(next_control,1,"#")
            if occurs("%",next_control)>0 then
            next_control=word(next_control,3,"%")
            end if
            while .not. isalpha(next_control)
            next_control=right(next_control,len(next_control)-1)
            end while
            ui_dlg_ctl_goto(dlg_title,next_control)
            end select
            case left(a_dlg_button,5)="add1_"
            if a_dlg_button="add1_killfocus" then
            Address_1=w_upper(address_1)
            end if
            a_dlg_button=""
            case left(a_dlg_button,5)="add2_"
            if a_dlg_button="add2_killfocus" then
            Address_2=w_upper(address_2)
            end if
            a_dlg_button=""
            case left(a_dlg_button,4)="dob_"
            if a_dlg_button="dob_killfocus" then
            valid_date=dtoc(dob)" / / "
            if .not. valid_date then
            dob={ / / }
            else
            dob=ctod(dtoc(dob))
            end if
            end if
            a_dlg_button=""
            end select
            %code%)
            if varC_result"OK" then
            end
            end if


            the enter key is trapped so it does not exit the xdialog, but instead advances field to field.
            you will see that the "middle initial" field auto-advances--i check to see when the field has a value and then advance to the next field.
            if you really want all the features, though, of a form, then you might as well use a form, no?

            Comment


              #7
              RE: xdialog auto advance and size of fields

              Oh my goodness!

              Yes, I think you are correct, I think I will try plan 2, and just create a pop up form!. Just wondered if it was possible. I am just starting to experiment with xdialog.

              Thanks Peter.
              Chris Tanti
              Technical Support

              Nuance & Fathom Ltd - The data-driven marketing agency

              Comment


                #8
                RE: xdialog auto advance and size of fields

                Peter,

                This is so cool it even gave me a diagnosis. I feel a lot better now. Thank you.

                Keith Hubert
                London.
                Regards
                Keith Hubert
                Alpha Guild Member
                London.
                KHDB Management Systems
                Skype = keith.hubert


                For your day-to-day Needs, you Need an Alpha Database!

                Comment


                  #9
                  RE: xdialog auto advance and size of fields

                  i foolishly just cut and paste from a larger script. trapping the "enter" key, at least, can be made much simpler for most field types.
                  e.g.

                  dlg_title="enter instead of tabs"
                  ui_dlg_box(dlg_title,
                  %dlg%,

                  Comment

                  Working...
                  X