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 killfocus event

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

    Xdialog killfocus event

    Why would this simple Xdialog code won't work??
    When I run it it doesn't show anything.

    dim vBirth as c

    screen=
    %screen%

    code=
    The Mexican

    #2
    RE: Xdialog killfocus event

    Hello Mario,

    Not an Xdialog expert, but check this out:

    ui_dlg_box("test",
    %dlg%, "ok"
    ui_msg_box("the value is",a_dlg_button)
    a_dlg_button = ""
    end if
    %code%)

    It appears that you are not handling all the events, leaving the a_dlg_button populated, hense closing the Xdialog box. I don't know why the events are cycling through several times.

    Good luck,
    Jim

    Comment


      #3
      RE: Xdialog killfocus event

      Geez,

      The multiple events are caused by my ui_msg_box() which of course takes focus away from the Xdialog box to display the message.............


      Jim

      Comment


        #4
        RE: Xdialog killfocus event

        the setfocus event is firing before the killfocus event and that is ending your xdialog prematurely.
        here is revised code that will do what you want:

        Code:
        dim vBirth as c 
        
        screen=""%screen% 
        Birthday| [15vBirth!vBirth_*]; 
        Name | [20.25vName]; 
        {lf}; 
        
        %screen% 
        
        code=""%code% 
        select 
        case left(a_dlg_button,7)="vBirth_"
        	if a_dlg_button="vBirth_killfocus" then
        	 	vName="Mario"
        	end if 
        	a_dlg_button=""
        end select 
        %code% 
        
        
        dlg=ui_dlg_box("TEST",screen,code) 
        end

        Comment


          #5
          RE: Xdialog killfocus event

          As a new reader to this thread, I think everybody has basically found the same thing but I'd like to try explaining the root of the problem a little more clearly for any new XDialog users...

          In the line:
          [15vBirth!vBirth_*];
          you have created an event trap "vBirth_*" that will generate various events whenever that object is acted on in any way. ("Generating an event" in this case basically means "assigning a value to the a_dlg_button variable" which is really a result of the event occurring.) Whenever you create event traps like this, you MUST handle all possible events for that object. However, the original script only handled the vBirth_killfocus event. Thus, as Peter pointed out, "the setfocus event is firing before the killfocus event" and, as Jim said, "you are not handling all the events, leaving the a_dlg_button populated, hence closing the Xdialog box."

          Comment


            #6
            RE: Xdialog killfocus event

            Gracias guys, Now I know what is going on.

            Mario
            The Mexican
            The Mexican

            Comment


              #7
              RE: Xdialog killfocus event

              I have modified my Xdialog code and it works fine now.
              But the only thing I am confused now is that the "killfocus" event is supposed to be generated when you leave the control.
              If I run this code the "killfocus" event is generated when you start typing on vBirth not when you "leave" the control. Isn't this the "change" event.??


              '***** code here********
              dim vBirth as c

              screen=
              %screen%

              code=
              The Mexican

              Comment


                #8
                RE: Xdialog killfocus event

                Mario
                You are missing the point
                The underscore and star ( _*) ([15vBirth!vBirth_*]) is what will generate all events for that object as Cal pointed out
                "vBirth_killfocus" is just a variable name (just as �abc� or �def�) which will only fire on the change event of that object. Use Peter�s example if you need it to fire at all events, if not you can use the following
                dim vBirth as c

                screen=
                Daniel Weiss
                EZ Link Software

                Comment


                  #9
                  RE: Xdialog killfocus event

                  Mario

                  When you modified your code, you changed the event response code to "vBirth_killfocus". When you use a full name, the documentation states the name is;

                  "EventName is the name of the event that is placed into a_dlg_button when the Change event occurs."

                  To trap the events, you need "vBirth_*" where the asterisk is replaced with the control_event. The documentation states;

                  "EventName_ControlEvent is placed into a_dlg_button when any type of ControlEvent occurs."

                  If you examine Peters example you will see how it works. You code could be modified as below;

                  screen=

                  Comment


                    #10
                    RE: Xdialog killfocus event

                    Thanks again, I am in the process of learning Xdialog and sometimes I get caught with ideas.



                    Thanks
                    Mario
                    The Mexican
                    The Mexican

                    Comment

                    Working...
                    X