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

Embedded xDialogs

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

    Embedded xDialogs

    Hi

    How do you refer the variables between the two or more Embedded xDialogs?

    I want to have this action; changing the Left side of the Embedded xDailog( xDialog7) then the variables will be shown at right side of the Embedded xDialog ( xDialog1 ).


    Embedded_xdialog.jpg Embedded_View.jpg

    #2
    Re: Embedded xDialogs

    make the variables GLOBAL, then they can be seen by anything in the database until you close it.

    Tom

    Comment


      #3
      Re: Embedded xDialogs

      Tom,

      Thank you and This is my scripts and I am not sure that I am on right way or not.

      xDialog script 1

      Code:
      'Put code here to DIM any variables used in your Xdialog.
      
      'Make a global_variable
      dim gv as p
      gv = global_variables()
      
      
      dim vParent as c
      dim vChilName as c
      dim vDate as d
      with gv
      
      'IMPORTANT: Do not change the dialog title. Place dialog content here...
      ui_modeless_dlg_box(dlgTitle,<<%dlg%
      {background=<Transparent>}
      {startup=init}
      {frame=1}
      {region}
      Date;| [.20vDate!Name_*];
      Name Send to child:| [.25vParent!Name_*];
      
      not share any more;
      Name get from child:| [%R%.25gv.vChildName];
      
      {endregion};
      {lf};
      
      %dlg%,<<%code%
      'Place code here for your event handlers...
      
      if left(a_dlg_button,4) = "Name" then
          if a_dlg_button ="Name_Change" then
          	ui_modeless_dlg_refresh(":Share:xdialog1")
              gv.vParent = vParent
              gv.vdate = vDate
             ui_modeless_dlg_refresh(":Share:xdialog3")
          end if
          a_dlg_button = ""
      end if
      
      %code%)	
      
      end with
      xDialog Script 2

      Code:
      'Put code here to DIM any variables used in your Xdialog.
      dim vChildName as c =""
      'Set a Global Variable containing the	
      dim gv as p
        gv = global_variables()
      with gv
      	gv.vparent = vParent
      	gv.vdate = vDate
      
      'IMPORTANT: Do not change the dialog title. Place dialog content here...
      ui_modeless_dlg_box(dlgTitle,<<%dlg%
                      {background=<Transparent>}		
      		{wrap=60}
      		This is an embedded dialog box that responds to the xDialog event sent to it from its parent. and receive from parent;
      		{lf};
      		Name for Child:; 
      		  [.50vChildName!vName_changed];
      		Name get From Parent:; 
      		  [%R%.50gv.vParent];
      		Record Date:| [.20gv.vDate];  
      		{lf};
      		Enter a name into the Name field and,  After  second, the "Parent" dialog box will be shown the child Name.;
      		{lf};
      		
      		%dlg%,<<%code%
      		'Place code here for your event handlers...
      		
      		if a_dlg_button ="vName_changed" then
      		    a_dlg_button =""
      		    ui_modeless_dlg_refresh(":share:xdialog3")
      		    gv.vChildName = vChildName
      		    gv.vDate = vDate
      		    ui_modeless_dlg_refresh(":share:xdialog1")
      		end if
      		
      		%code%)
                       end with
      Tom,
      It was fired fine until closed the A5. After open again I kept getting an error message and attached the screen shot here.

      If you can find an error or better way to write, please let me know.

      Thank you again

      Global_Run_error.jpg
      Last edited by johnkoh; 07-17-2012, 06:38 PM. Reason: attachment location

      Comment


        #4
        Re: Embedded xDialogs

        John,

        When you dim vParent, just dim it as :
        DIM GLOBAL vParent as C
        I have a feeling that somewhere along the way, your variable scope is getting confused.
        Others may argue, but I don't set a pointer to the different variable spaces. It just confuses me.

        Define your variabls as global in both scripts and just use the variable as defined. That should work.

        Code:
        'Put code here to DIM any variables used in your Xdialog.
        
        'Make a global_variable
        
        dim GLOBAL vParent as c
        dim GLOBAL vChilName as c 
        dim GLOBAL vDate as d
        
        
        'IMPORTANT: Do not change the dialog title. Place dialog content here...
        ui_modeless_dlg_box(dlgTitle,<<%dlg%
        {background=<Transparent>}
        {startup=init}
        {frame=1}
        {region}
        Date;| [.20vDate!Name_*];
        Name Send to child:| [.25vParent!Name_*];
        
        not share any more;
        Name get from child:| [%R%.25gv.vChildName];
        
        {endregion};
        {lf};
        
        %dlg%,<<%code%
        'Place code here for your event handlers...
        
        if left(a_dlg_button,4) = "Name" then
            if a_dlg_button ="Name_Change" then
            	ui_modeless_dlg_refresh(":Share:xdialog1")
               ui_modeless_dlg_refresh(":Share:xdialog3")
            end if
            a_dlg_button = ""
        end if
        
        %code%)
        Code:
        'Put code here to DIM any variables used in your Xdialog.
        dim GLOBAL vChildName as C
        'Set a Global Variable containing the	
        dim GLOBAL vParent as C
        dim GLOBAL vDate as D
        
        'IMPORTANT: Do not change the dialog title. Place dialog content here...
        ui_modeless_dlg_box(dlgTitle,<<%dlg%
                        {background=<Transparent>}		
        		{wrap=60}
        		This is an embedded dialog box that responds to the xDialog event sent to it from its parent. and receive from parent;
        		{lf};
        		Name for Child:; 
        		  [.50vChildName!vName_changed];
        		Name get From Parent:; 
        		  [%R%.50gv.vParent];
        		Record Date:| [.20gv.vDate];  
        		{lf};
        		Enter a name into the Name field and,  After  second, the "Parent" dialog box will be shown the child Name.;
        		{lf};
        		
        		%dlg%,<<%code%
        		'Place code here for your event handlers...
        		
        		if a_dlg_button ="vName_changed" then
        		    a_dlg_button =""
        		    ui_modeless_dlg_refresh(":share:xdialog3")
        		    ui_modeless_dlg_refresh(":share:xdialog1")
        		end if
        		
        		%code%)
        The variables are defined in Both scripts as global, so there shouldn't be any confusion.

        Tom

        Comment

        Working...
        X