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 Boxes - Conference AVI

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

    XDialog Boxes - Conference AVI

    Does anyone have a 'complete' XBasic copy of the Conference AVI on XDialog Boxes - that they are willing to pass along to me????

    Trying to learn from it, but it is not complete and I cannot get the box to work.... Possibly I am missing some code that is not covered in the AVI, but was available on the Conference CD....

    Any help would be highly appreciated.
    D

    #2
    RE: XDialog Boxes - Conference AVI

    Specifically, I am having difficulty 'seeing' what goes on during data entry....
    The example (partially) shown deals ONLY with what happens when the user presses the 'OK' or 'Cancel' buttons on the bottom of the dialog box.....
    In a different thread, I'm working on trapping enter and escape and maybe CTL+C and the 'Pause/Break' key. Just so the user cannot just dump the dialog box....
    Back to the point -- I understand that the user can move from field to field using the TAB key, but I would think that the 'correct' code would "forcibly" handle the progresssion thru the various fields, making all the required field rule changes as fields are entered.

    A 'clear text' example would be:

    :if field_one focus and enter is pressed
    then go to field_two after formatting field_one properly
    (formatting = req'd fields are not blank, etc.)
    :if field_two focus and enter is pressed
    then go to field_three after formatting field_two properly
    :etc

    Then even if the user tabs back up the field selection, the code still works and THEN

    go into the code for what happens after the buttons that close the dialog box are pressed.....
    :if a_dlg_button = "OK" etc etc.....

    In my mind, if you don't control keyboard input at every stage of the input, you stand the chance that the user will 'short-circuit' the entire process.....

    Remember Brown's Law......

    D

    Comment


      #3
      RE: XDialog Boxes - Conference AVI

      Something like the following:
      Don't start telling me it's not right, I know it doesn't work correctly, this is just an example of what I'm trying to accomplish..... the problem with what's below is that it won't return to the unfilled field and wait for an input... still workin' on that!!

      'Date Created: 23-Jul-2004 01:00:38 AM
      'Last Updated: 23-Jul-2004 01:00:38 AM
      'Created By : Dick Coleman
      'Updated By : Dick Coleman

      ui_dlg_box("Trap Enter",""%dlg%
      {on_key=enter}
      {on_key=esc} '(Did not read this, just tried it!)
      First Name: | [.10v_fname];
      Last Name: | [.10v_lname];
      Address 2: | [.10v_adr2];
      City: | [.10v_city];
      "Close";
      %dlg%,""%code%

      '-----------------------------------------------------------------------------FIRST NAME FIELD---------
      field_1:
      if v_fname="" .and. a_dlg_button="enter" then
      ui_beep(ui_exclamation_beep)
      ui_msg_box("Required Field","Enter a First Name",ui_attention_symbol)
      a_dlg_button=""
      goto field_1
      end if

      if v_fname "" "" .and. a_dlg_button="enter" then
      'any formatting code goes here---------------------------------------------------
      goto field_2
      end if
      '-----------------------------------------------------------------------------LAST NAME FIELD--------------
      field_2:
      if v_lname="" .and. a_dlg_button="enter" then
      ui_beep(ui_exclamation_beep)
      ui_msg_box("Required Field","Enter a Last Name",ui_attention_symbol)
      a_dlg_button=""
      goto field_2
      end if

      if v_lname "" "" .and. a_dlg_button="enter" then
      'again formatting----------------------------------------------------------------
      goto field_3

      end if
      '-------------------------------------------------------------------------------ADDRESS 2 FIELD--------------
      field_3:
      if (v_adr2="" .or. v_adr2 "" "") .and. a_dlg_button="enter" then
      goto field_4
      'probably need two statements so can format if filled in------------------------------------
      end if
      '---------------------------------------------------------------------------CITY FIELD-------------------
      field_4:
      if v_city="" .and. a_dlg_button="enter" then
      ui_beep(ui_exclamation_beep)
      ui_msg_box("Required Field","Enter a City Name",ui_attention_symbol)
      a_dlg_button=""
      goto field_4
      end if

      if v_city "" "" .and. a_dlg_button="enter" then
      'more formatting----------------------------------------------------------------------------
      ui_dlg_ctl_goto("Trap Enter",""Close"")
      'goto the_end
      end if
      '---------------------------------------------------------------------------------CLOSE BUTTON-------------
      the_end:
      if (a_dlg_button="enter" .or. a_dlg_button="esc") .and. .not. ("Close"$ui_dlg_ctl_current(("Trap Enter"))) then
      a_dlg_button=""
      end if
      '------------------------------------------------------DONE------------------------
      %code%)

      Comment


        #4
        RE: XDialog Boxes - Conference AVI

        Tried 'ui_dlg_ctl_goto.......' but that won't work either...it still just falls thru to the 'if' command...
        Still looking for an input command somewhere...

        D

        Comment


          #5
          RE: XDialog Boxes - Conference AVI

          Email or call Richard, at Alpha.
          Cole Custom Programming - Terrell, Texas
          972 524 8714
          [email protected]

          ____________________
          "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

          Comment


            #6
            RE: XDialog Boxes - Conference AVI

            Richard

            Attached is a zip of the xdialog presentation I gave at the conference. In the zip is a pdf that was on the conference CD and an exported script that included the final script with all of the bells and whistles.

            Jerry

            Comment


              #7
              RE: XDialog Boxes - Conference AVI

              Thank you very much.....
              Looks like my weekend is now full...
              D

              Comment

              Working...
              X