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 popup date value not available while dialog is open

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

    xdialog popup date value not available while dialog is open

    The following example shows that the date value selected with the date popup does not seem to be available while the xdialog is open. Am I wrong, not coding something right, missing something subtle? Is there a work around?

    Code:
            dim vdate as d={}
    	dim vfield2 as d
    	ui_dlg_box("test",<<%dlg%
    	Purchase_Date: |{initial_focus} [%P=popup.calendar(dtoc(vdate));I=popup.calendar%.15vdate]   ;
    	Field2: | [.12vfield2!evf2_*];
    	{lf};
    	<OK>
    	%dlg%,<<%code%
    	
    	IF left(a_dlg_button,5)="evf2_"
    		if a_dlg_button="evf2_setfocus"
    			msgbox("focus set on field 2",dtoc(vdate))
    			vfield2=vdate+30
    		end if
    	
    		if a_dlg_button="evf2_killfocus"
    			msgbox("killfocus on field 2",dtoc(vdate))
    		end if
    
    	  a_dlg_button=""
    	END IF
    	%code%)
    
    	msgbox("Dates",dtoc(vdate)+crlf()+dtoc(vfield2))
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    #2
    Re: xdialog popup date value not available while dialog is open

    Mike, A number of these issues seem to have popped up lately (sorry for the bad pun). I am not sure if it is a bug or a idiosyncrasy of xdialog. I tested in v9 and get the same thing.

    Any way, I added a couple of bits that seem to get things going. The issue seems to be that the control that is supplying the value, in this case the date popup, needs to have an event assigned as well. It seems that this event wakes up the dialog to the fact that the value has changed. Of course now you need to deal with this event (xxx) but that is no biggy. If you had a number of controls where this was necessary then you could simply use the same event name which would be trapped in the one place.


    Code:
    dim vdate as d={}
    dim vfield2 as d
    ui_dlg_box("test",<<%dlg%
    	Purchase_Date: |{initial_focus} [%P=popup.calendar(dtoc(vdate));I=popup.calendar%.15vdate[COLOR="#FF0000"][B]!xxx[/B][/COLOR]]   ;
    	Field2: | [.12vfield2!evf2_*];
    	{lf};
    	<OK>
    %dlg%,<<%code%
    
    IF left(a_dlg_button,5)="evf2_"
    	IF a_dlg_button="evf2_setfocus"
    		msgbox("focus set on field 2",dtoc(vdate))
    		vfield2=vdate+30
    	END IF
    	
    	IF a_dlg_button="evf2_killfocus"
    		msgbox("killfocus on field 2",dtoc(vdate))
    	END IF
    	
    	a_dlg_button=""
    [B][COLOR="#FF0000"]else if a_dlg_button = "xxx"
    	a_dlg_button = ""[/COLOR][/B]
    END IF
    %code%)
    
    msgbox("Dates",dtoc(vdate)+crlf()+dtoc(vfield2))
    Or even just like this using the event prefix you already have.
    Code:
    dim vdate as d={}
    dim vfield2 as d
    ui_dlg_box("test",<<%dlg%
    	Purchase_Date: |{initial_focus} [%P=popup.calendar(dtoc(vdate));I=popup.calendar%.15vdate[COLOR="#FF0000"][B]!evf2_x[/B][/COLOR]]   ;
    	Field2: | [.12vfield2!evf2_*];
    	{lf};
    	<OK>
    %dlg%,<<%code%
    
    IF left(a_dlg_button,5)="evf2_"
    	IF a_dlg_button="evf2_setfocus"
    		msgbox("focus set on field 2",dtoc(vdate))
    		vfield2=vdate+30
    	END IF
    	
    	IF a_dlg_button="evf2_killfocus"
    		msgbox("killfocus on field 2",dtoc(vdate))
    	END IF
    	
    	a_dlg_button=""
    
    END IF
    %code%)
    
    msgbox("Dates",dtoc(vdate)+crlf()+dtoc(vfield2))
    Tim Kiebert
    Eagle Creek Citrus
    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

    Comment


      #3
      Re: xdialog popup date value not available while dialog is open

      I can see it for your first field OK. The second field is not set for a date popup. Is that the way you wanted it?
      -----------------------------------------------
      Regards
      Mark Pearson
      [email protected]
      Youtube channel
      Website

      Comment


        #4
        Re: xdialog popup date value not available while dialog is open

        Sorry - I missed the {initial focus} part and have the same issue. I was actually going to post a similar problem with the focus on the xdialog when starting. I have found that the setfocus to field does not work on startup at any time no matter what field gets even with it set to have initial focus
        -----------------------------------------------
        Regards
        Mark Pearson
        [email protected]
        Youtube channel
        Website

        Comment


          #5
          Re: xdialog popup date value not available while dialog is open

          Mike, I'm seeing the same thing as Tim, and solved it using a similar approach:

          Code:
          dim vdate as d={}
          dim vfield2 as d = {}
          ui_dlg_box("test",<<%dlg%
          Purchase_Date: |{initial_focus} [%P=popup.calendar(dtoc(vdate));I=popup.calendar%.15vdate[COLOR="#FF0000"]!popup_changed[/COLOR]] ;
          Field2: | [.12vfield2!evf2_*];
          {lf};
          <OK>
          %dlg%,<<%code%
          [COLOR="#FF0000"]if a_dlg_button = "popup_changed" then
              a_dlg_button = ""
              'msgbox("found","calendar control")
              if vdate <> {} then
                  vfield2 = vdate + 30
              end if
          end if[/COLOR]
          IF left(a_dlg_button,5)="evf2_"
          		if a_dlg_button="evf2_setfocus"
          			msgbox("focus set on field 2",dtoc(vdate))
          			[COLOR="#FF0000"]'vfield2[/COLOR]=vdate+30
          		end if
          	
          		if a_dlg_button="evf2_killfocus"
          			msgbox("killfocus on field 2",dtoc(vdate))
          		end if
          
          	  a_dlg_button=""
          END IF
          %code%)
          
          msgbox("Dates",dtoc(vdate)+crlf()+dtoc(vfield2))
          I don't know if the popup calendar control is "sleepy" or if this is a timing issue with the setfocus event firing too quickly, but the net result is that field2 gets focus before the selected calendar date is processed and stored in the second var.

          Hope this helps.

          Comment


            #6
            Re: xdialog popup date value not available while dialog is open

            Can you guys also check my observation on this for all fields

            I have found that the setfocus to field does not work on startup at any time no matter what field gets even with it set to have initial focus
            -----------------------------------------------
            Regards
            Mark Pearson
            [email protected]
            Youtube channel
            Website

            Comment


              #7
              Re: xdialog popup date value not available while dialog is open

              Tim, Tom.. Thank you. I thought in times past I had difficulties having the popup field fire an event, so I didn't try that route. I did think about timing and others, and tried to place a couple of added fields beyond the popup with events trying to capture the prior entered date through those, which didn't work. So, we'll chalk it up to a "sleepy" popup that needs a little event to make it's value available.

              Mark,
              I did not test the setfocus event on startup. I wouldn't ever go that route but instead I use the startup event to fire anything that needs to happen at startup instead of trying to fire it from the setfocus event of the initial_focus field. Example:
              Code:
              dim vdate as d={}
              dim vfield2 as d = {}
              dim dlg_title as C="Testing"
              ui_dlg_box(dlg_title,<<%dlg%
              {startup=ini}
              Purchase_Date: |{initial_focus} [%P=popup.calendar(dtoc(vdate));I=popup.calendar%.15vdate!popup_changed] ;
              Field2: | [.12vfield2!evf2_*];
              {lf};
              <OK>
              %dlg%,<<%code%
              
              IF a_dlg_button="ini"
              	ui_beep(UI_EXCLAMATION_BEEP)
              	ui_modeless_dlg_box("Startup",<<%dlg%
              	{position=4,2}{background=yellow}
              	{lf};	
              	This modeless xdialog is part of the startup event of the modal dialog;
              	{lf};
              	%dlg%)	
                a_dlg_button=""
              END IF
              
              IF a_dlg_button = "popup_changed" then
                    if vdate <> {} then
                      vfield2 = vdate + 30
              		sys_send_keys("{TAB}")
                  end if
              	a_dlg_button = ""
              end if
              
              IF left(a_dlg_button,5)="evf2_"
              	if a_dlg_button="evf2_setfocus"
              		ui_dlg_ctl_goto(dlg_title,"<OK>")
              	end if
              
               a_dlg_button=""
              END IF
              %code%)
              
              msgbox("Dates",dtoc(vdate)+crlf()+dtoc(vfield2))
              ui_modeless_dlg_close("Startup")
              Mike W
              __________________________
              "I rebel in at least small things to express to the world that I have not completely surrendered"

              Comment


                #8
                Re: xdialog popup date value not available while dialog is open

                Code:
                dim vdate as d
                dim vfield2 as c
                ui_dlg_box("test",<<%dlg%
                Purchase_Date: |{initial_focus} [%P=popup.calendar(dtoc(vdate));I=popup.calendar%.15vdate!evf2_*]   ;
                Field2: | [.12vfield2];
                {lf};
                <OK>
                %dlg%,<<%code%	
                	IF left(a_dlg_button,5)="evf2_"
                	vfield2=""
                		if a_dlg_button="evf2_killfocus"
                		vfield2=dtoc(vdate+30,"mm/dd/yyyy")
                		end if
                	  a_dlg_button=""
                	END IF
                %code%)

                Comment

                Working...
                X