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

UI_MODELESS_DLG_BOX() Special naming convention

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

    UI_MODELESS_DLG_BOX() Special naming convention

    I would like an Xdialog box to close automatically when its "parent" form closes, or looses focus.

    Alpha Documentation states:

    To cause a modeless Xdialog to behave in this manner, you simply follow a special naming convention for the title parameter in the UI_MODELESS_DLG_BOX() command.

    Set the title to:

    :formname@:title

    where formname is the name of the form that is running, and title is the text that you want to appear at the dialog title.

    So I tried the following:

    Code:
    FUNCTION TestFunction AS C ( )
    DIM wjcparent as C
    DIM wjcformname as C
    
    wjcparent=topparent.Name()
    wjcformname="FORMNAME"
    
    ui_modeless_dlg_box(:wjcparent@:wjcformname,<<%dlg%
    Testname: [Testname];
    <OK>
    %dlg%)
    
    END FUNCTION
    Which results in : Variable "@:wjcformname" not found.

    Thanks in advance for any suggestions,

    Fred
    Last edited by AaronBBrown; 02-20-2007, 01:57 PM.
    Fred

    #2
    Re: UI_MODELESS_DLG_BOX() Special naming convention

    For clarification, you are pointing at this page in the help file?

    http://support.alphasoftware.com/alp...omatically.htm
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment


      #3
      Re: UI_MODELESS_DLG_BOX() Special naming convention

      That is correct.
      Fred

      Comment


        #4
        Re: UI_MODELESS_DLG_BOX() Special naming convention

        Fred

        I'd suggest that you make the first line of code in the function

        debug(1)

        Then you can step through the code and see the values that are in each variable. When you see something in the debug screen that you want to know the value of, right click it and choose watch..

        Or you can type the names of the variables that you want to watch in the lines at the bottom of the debug screen and see the values in the variables.

        Also the notice line in the help file talks about using topparent.name() to get the value of the formname - not to add "formname" to it.


        (Since you're from Wisconsin, you probably realize that I'm trying to teach you how to 'fish', rather than giving you the 'fish')
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment


          #5
          Re: UI_MODELESS_DLG_BOX() Special naming convention

          Nibble, nibble.
          Fred

          Comment


            #6
            Re: UI_MODELESS_DLG_BOX() Special naming convention

            Well Al, I'm hooked - reel me in.

            I originally had ui_msg_box displays in the code so I could track the values in the variables, but, following your sage advice I went the debug route.

            But I'm obviously brain dead today (why pick on today?) because your "bait" just isn't registering:

            "Also the notice line in the help file talks about using topparent.name() to get the value of the formname - not to add "formname" to it."

            How about adding a worm or two?
            Fred

            Comment


              #7
              Re: UI_MODELESS_DLG_BOX() Special naming convention

              Thanks fo your offline help, Al. Per your suggestion, I tried building the individual parameters in a string and then using that variable in the function:
              Code:
              FUNCTION TestFunction AS C ( )
              
              DIM wjcstring as C
               
              wjcstring = ":" + topparent.Name()+ "@:" + "Dialog Box Name"
              
              ui_modeless_dlg_box(wjcstring,<<%dlg% 
              Testname: [Testname];
              <OK>
              %dlg%)
              
              END FUNCTION
              Works great. Thanks again, Al. Sure is great to get that kind of super quality help.
              Last edited by AaronBBrown; 02-20-2007, 01:58 PM.
              Fred

              Comment

              Working...
              X