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 field variable value not available within xdialog code section ?

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

    Xdialog field variable value not available within xdialog code section ?

    I swear this should work. The following code is a two field xdialog with a set focus event for the second field to evaluate the value put into the first field. The variable value for the first field is not being recognized during the xdialog code activity. I swear this used to be possible. It is available in the dialog, just press the test button after the cursor enters field 2, but it is not available with the field 1 killfocus or the field 2 setfocus events! What happened? Or am I mistaken?
    Code:
    'dialog structure
    	dim dlg_title as C="Stock Entry"
    	dim dlg_body as C
    	dim dlg_code as C
    	dim vR as C
    	
    'dialog field variables
    	dim global aaa_symb as C=""
    	dim vname as C=""
    
    	dlg_body = <<%dlg%
    	{background=#185,185,150}{xmargin=1,1}{ymargin=1,1}
    	{justify=left}{font=arial,8,bi}{frame=1,5}{font=Arial,10}
    	{region}
    	Symbol:	| [.12aaa_symb] ;	
    	Stock Name: | [.60vname!evnm_*];
    	{endregion};
    	{lf=.5};
    	{justify=center} <15OK> <15Cancel> <test>
    	%dlg%
    	
    	dlg_code=<<%code%
    	IF left(a_dlg_button,5)="evnm_"
    		if a_dlg_button="evnm_set_focus"
    			msgbox("Symbol","The symbol entered is: "+aaa_symb)
    		end if
    	   a_dlg_button=""
    	 END IF
    
    	IF a_dlg_button="test"
    		msgbox("Symbol","The symbol is: "+aaa_symb)
    	  a_dlg_button=""
    	END IF
    	%code%
    
    	vR=ui_dlg_box(dlg_title,dlg_body,dlg_code)
    	if vR="Cancel"
    		end
    	end if
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    #2
    Re: Xdialog field variable value not available within xdialog code section ?

    Try "evnm_setfocus" instead of "evnm_set_focus"

    Comment


      #3
      Re: Xdialog field variable value not available within xdialog code section ?

      Ditto ..

      Comment


        #4
        Re: Xdialog field variable value not available within xdialog code section ?

        Hi Gabriel,
        Nope. That wasn't it. That posted xdialog is code is workable directly in the IW without any tables or forms. So you can just copy and paste into IW and see if you can make it work. If you can... let me know.
        Mike W
        __________________________
        "I rebel in at least small things to express to the world that I have not completely surrendered"

        Comment


          #5
          Re: Xdialog field variable value not available within xdialog code section ?

          Yes Mike.. you are correct..you threw me in a loop with the mis-spelled event.
          I believe, pending (time permitting) further testing, it's a bug.
          The reason I say that is, and you as an avid reader of the message board might remember, there was a similar bug in the killfocus for which I submitted a report and Selwyn acknowledged it and mentioned that it will not be fixed (understandable).
          Here is a workaround (do not place the msg box for confirmation, it will throw your script in an endless loop, and yes and I am sorry, but it will not work on modal).
          Code:
          'dialog structure
          	dim dlg_title as C="Stock Entry"
          	dim dlg_body as C
          	dim dlg_code as C
          	dim vR as C
          	
          'dialog field variables
          	dim global aaa_symb as C=""
          	dim vname as C=""
          	dim txt as c=""
          	dlg_body = <<%dlg%
          	{background=#185,185,150}{xmargin=1,1}{ymargin=1,1}
          	{justify=left}{font=arial,8,bi}{frame=1,5}{font=Arial,10}
          	{region}
          	Symbol:	| [.12aaa_symb] ;	
          	Stock Name: | [.60vname!evnm_*];
          	| {text=40,txt}
          	{endregion};
          	{lf=.5};
          	{justify=center} <15OK> <15Cancel> <test>
          	%dlg%
          	
          	dlg_code=<<%code%
          	IF left(a_dlg_button,5)="evnm_"
          		if a_dlg_button="evnm_setfocus"
          			txt="The Symbol entered is: "+aaa_symb
          		end if
          	   a_dlg_button=""
          	 END IF
          
          	IF a_dlg_button="test"
          		msgbox("Symbol","The symbol is: "+aaa_symb)
          	  a_dlg_button=""
          	END IF
          	if a_dlg_button="cancel"
          		ui_modeless_dlg_close(dlg_title)
          		end if
          	%code%
          
          	vR=ui_modeless_dlg_box(dlg_title,dlg_body,dlg_code)
          	if vR="Cancel"
          		end
          	end if
          Last edited by G Gabriel; 06-26-2011, 01:18 PM.

          Comment


            #6
            Re: Xdialog field variable value not available within xdialog code section ?

            Thanks Gabriel,
            I guess I'll have to code the whole action within the code of a modeless dialog, or go for a completely different approach. I'll start with the whole different approach first.
            Mike W
            __________________________
            "I rebel in at least small things to express to the world that I have not completely surrendered"

            Comment


              #7
              Re: Xdialog field variable value not available within xdialog code section ?

              Mike, see if this works for you.
              I added a dummy event to field 1. this seems to wake up some part of the dialog code that there is a value there even though the test button has access to it. I noticed that after using the test button the focus event would show the value.
              Of course then we also need to deal with the event.
              Code:
              'dialog structure
              	dim dlg_title as C="Stock Entry"
              	dim dlg_body as C
              	dim dlg_code as C
              	dim vR as C
              	
              'dialog field variables
              	dim global aaa_symb as C=""
              	dim vname as C=""
              
              	dlg_body = <<%dlg%
              	{background=#185,185,150}{xmargin=1,1}{ymargin=1,1}
              	{justify=left}{font=arial,8,bi}{frame=1,5}{font=Arial,10}
              	{region}
              	Symbol:	| [.12aaa_symb[COLOR="#FF0000"]!dummyevent[/COLOR]] ;	
              	Stock Name: | [.60vname!evnm_*];
              	{endregion};
              	{lf=.5};
              	{justify=center} <15OK> <15Cancel> <test>
              	%dlg%
              	
              	dlg_code=<<%code%
              	IF left(a_dlg_button,5)="evnm_"
              		if a_dlg_button="evnm_setfocus"
              			msgbox("Symbol","The symbol entered is: "+aaa_symb)
              		end if
              	   a_dlg_button=""
              	 END IF
              
              	IF a_dlg_button="test"
              		msgbox("Symbol","The symbol is: "+aaa_symb)
              	  a_dlg_button=""
              	END IF
              	[COLOR="#FF0000"]If a_dlg_button = "dummyevent" then
              	    a_dlg_button = ""
              	end if[/COLOR]
              	%code%
              
              	vR=ui_dlg_box(dlg_title,dlg_body,dlg_code)
              	if vR="Cancel"
              		end
              	end if
              And just to add a bit of confusion. You said you could not get the killfocus event on field1 to work. But it works here.
              Code:
              'dialog structure
              	dim dlg_title as C="Stock Entry"
              	dim dlg_body as C
              	dim dlg_code as C
              	dim vR as C
              	
              'dialog field variables
              	dim global aaa_symb as C=""
              	dim vname as C=""
              
              	dlg_body = <<%dlg%
              	{background=#185,185,150}{xmargin=1,1}{ymargin=1,1}
              	{justify=left}{font=arial,8,bi}{frame=1,5}{font=Arial,10}
              	{region}
              	Symbol:	| [.12aaa_symb![COLOR="#FF0000"]evnm_*[/COLOR]] ;	
              	Stock Name: | [.60vname];
              	{endregion};
              	{lf=.5};
              	{justify=center} <15OK> <15Cancel> <test>
              	%dlg%
              	
              	dlg_code=<<%code%
              	IF left(a_dlg_button,5)="evnm_"
              		if a_dlg_button="[COLOR="#FF0000"]evnm_killfocus[/COLOR]"
              			msgbox("Symbol","The symbol entered is: "+aaa_symb)
              		end if
              	   a_dlg_button=""
              	 END IF
              
              	IF a_dlg_button="test"
              		msgbox("Symbol","The symbol is: "+aaa_symb)
              	  a_dlg_button=""
              	END IF
              	%code%
              
              	vR=ui_dlg_box(dlg_title,dlg_body,dlg_code)
              	if vR="Cancel"
              		end
              	end if
              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

              Working...
              X