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 issue with {condition_begin}

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

    #16
    Re: Xdialog issue with {condition_begin}

    I've tried using an embedded xdlg, but that didn't quite work. And I couldn't set the focus to the control I wanted. I know I don't fully understand the internal workings here, but Cian Chambliss at Alpha Software suggested I use different variables for each condition, and that works. Seems to have helped A5 to disambiguate the different variables in the different conditions, as per Cian's help.

    I'm starting to agree with you that this was not a bug, rather I'd call it a "quirk" that you just have to work through. It just creates some extra complexity where (in my specific case) I must keep four different versions of each variable, and keep track of all user edits.

    I'm close to finishing my solution (it works "most of the time"!) and I'll post it when done. I had to dig much deeper than I originally expected!
    There are three kinds of people in the world: those who can count, and those who can't.

    Comment


      #17
      Re: Xdialog issue with {condition_begin}

      This probably will not work, but then again it might:
      Since you are trapping those shortcut keys, put a changed event in each of those conditional controls to do a "Shift-tab" thus returning you back to the previous control.

      Comment


        #18
        Re: Xdialog issue with {condition_begin}

        Here is the working solution (attached).

        I'm sure there was a simpler solution, but I got going down this path (using text objects and multiple variables) and couldn't stop. And it's slick, just as I hoped. (And it took A LOT MORE TIME than I wanted, as I feared!)

        The first thing I had to do was realize there were four different conditions, and so I had to create four sets of variables. The way AlphaFive works, if you display the same variable in each condition (especially where they can be repositioned), A5 gets hung up trying to find the proper version of the variable. I've decided this is NOT a bug, you just have to know what it does. So each had to have a different name and had to be readily identified, so I prepended "qq" and added the row number to each variable.

        Next, I had to be able to access the text cursor, so each variable had to be a pointer. In my third try, I realized creating a class would be easiest, so that's why you see it. I found that using class variable in xdlg controls works, as xdlg automatically works with the <text>.text property of each variable.

        The crazy part was realizing that every time a variable was modified, I had to update the three other versions. Sometimes, due to the desired logic, the control the cursor was in would disappear, so I had to choose the new destination (such as when you are editing the maiden name and then change the sex to "Male" - no longer a need to display the maiden name, so go to Last Name instead).

        The last change was with the alternate address fields. I decided to just jump to the main addr1 field, but I had to make it a text pointer so I could use ui_dlg_ctl_goto(), and it was as simple as changing 'dim addr1 as c' to 'dim addr1 as CurControl'.

        One other trick I learned: I had a few bugs I just couldn't reproduce easily, and so I wrapped an IF statement around a debug(1) at the correct point and put the logical variable into a check box at the top. When I had played around enough so that the problem reproduced itself regularly, I could click the debug check box and then press the CTRL-key sequence to trap the bug.

        If I had to do this all over again, I figure it would take less than 1/4 the time, maybe even less once I get a bunch more xdialogs under my belt. On to the next stage...
        There are three kinds of people in the world: those who can count, and those who can't.

        Comment


          #19
          Re: Xdialog issue with {condition_begin}

          Hi Eric,

          Many thanks for sharing this experience.
          An explanation like this is very instructive especially now that you've provided them with examples where progress is visible.

          We love these contributions very much.
          Now time for us to investigate!
          Be welcome.


          Ton
          Most things are simple but unfortunately only after the first time

          Comment

          Working...
          X