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

onrowdoubleclick and named browse

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

    onrowdoubleclick and named browse

    How does one use a named browse (one that has been customized to show what you want) and also use onrowdoubleclick.

    The onrowdoubleclick event seems in the code editor to only be available to the default browse or an embedded browse.
    Any workarounds?
    And what's the difference between the default and an embedded browse?
    Thanks
    tc

    #2
    RE: onrowdoubleclick and named browse

    It's kind of buried there.

    Open the named browse in design mode, then
    click View/Code Editor
    When the code editor is in view click in the left "Container" drop dow box and select your named browse. Now you will see the events for the named browse.

    Finian
    Finian

    Comment


      #3
      RE: onrowdoubleclick and named browse

      Finnian,
      Thanks for the speedy reply. I read a previous thread about this where you had given the same advice, but the part about doing it to the browse itself (not the form edit) escaped me.
      There it is....
      Thanks,
      tc

      Comment


        #4
        RE: onrowdoubleclick and named browse

        Having found the event, I came up with the following:

        tbl=table.current()
        if var->driver_name=""
        'I tried to put a ui_msg here, unsuccessfully
        end
        end if

        if tbl.Is_Marked()
        ui_freeze(.t.)
        sys_send_keys("{ctrl-u}")
        tbl.change_begin()
        tbl.driver=""
        tbl.change_end()
        ui_freeze(.f.)
        else
        ui_freeze(.t.)
        sys_send_keys("{ctrl-m}")
        tbl.change_begin()
        tbl.driver=driver_name
        tbl.change_end()
        ui_freeze(.f.)
        end if
        end

        This works except...it requires DOUBLE doubleclick...

        Also, I tried this without the ui_freeze statements and it would mark the record but place the name somewhere else. Odd.

        Lastly, on the form that contains this browse is a button.
        Among other things on the On Push is:

        dim driver_name as c
        driver_name=ui_get_text("Driver","Enter the driver's name","","llllllll")

        This does not seem to set the variable. The only way I can get the previous script above to enter a driver name into the driver field is to declare the variable value in the Variable Definition window. Which is obviously not going to work for me.

        Thanks
        tc

        Comment


          #5
          RE: onrowdoubleclick and named browse

          If I use dim global, it works.
          Still having the Double Doubleclick problem.
          tc

          Comment


            #6
            RE: onrowdoubleclick and named browse

            If you only want to use the driver_name variable within the form, adding it to the form as a session variable and then using
            dim shared driver_name as c
            may help.

            I find using the var-> method for referencing variables to be confusing. It doesn't (or so it seems to me) give a sufficiently consistent syntax for setting/checking/verifying/manipulating variables.

            As a general rule when setting up variables to be used within a form I add them as layout variables to the form and will place the variable on the form, usually hidden. From that point I can use something like parentform:varname.text to refer to a character variable and, parentform:varname.value to refer to date, numeric and logical variables.

            One side benefit of this is that it cuts down on the need to use session/global variables since, if you can get a pointer to the form, you can then manipulate the given variable from anywhere without having to add to the list of globals, which I use extensively.

            Is your browse used for data entry? That would be my only guess on the double doubleclick. I generally only have dclick events on read only browses.

            Finian
            Finian

            Comment


              #7
              RE: onrowdoubleclick and named browse

              you are mixing form-level and table-level events on the same record.
              i think that is your problem with the double clicks. you can simplify your
              script as follows:


              if tbl.Is_Marked()
              tbl.change_begin()
              tbl.driver=""
              tbl.unmark()
              tbl.change_end()
              else
              tbl.change_begin()
              tbl.mark()
              tbl.driver=driver_name
              tbl.change_end()
              end if

              Comment

              Working...
              X