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



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

Close listview on double click

  • Filter
  • Time
  • Show
Clear All
new posts

  • Close listview on double click

    I have a list view that is filtered by a variable. When an item is selected and oK is clicked it takes you to form based on the detail of the item. It is built in action script. I converted this to xbasic and now want to make the doubleclick function built by the conversion do the same action as the OK button.

    I can get it to go to the form, but the xdialog does not close and as it is modal remains on top. I can see in help where if was a modeless xdialog I can close it but there is no such command for the modal.

    Can this only be done with a modeless xdialog or am I missing a key process in how the xdialog works
    Mark Pearson
    [email protected]
    Youtube channel

  • #2
    Re: Close listview on double click

    Show us the relevant code.
    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.


    • #3
      Re: Close listview on double click


      ui_modeless_dlg_close() will close the dialog even though it is not a modeless dialog. With in the list view code you will see the 'OnDoubleClick' function. Use the example below replacing the RED BOLDED code with yours.

      FUNCTION OnDoubleClick as C(lv as P,listView as P,args as P)
      	WITH lv
      		ui_modeless_dlg_close([B][COLOR="Red"]YOUR DIALOG TITLE[/COLOR][/B])
      	END WITH	


      • #4
        Re: Close listview on double click

        Thanks Scott - That worked perfectly. I did not try it as it referred to modeless.
        Mark Pearson
        [email protected]
        Youtube channel


        • #5
          Re: Close listview on double click

          Just another way of doing things.

          When working with a modal xdialog you shouldn't really need to call anything to close it. You can but you don't need to. As long as the a_dlg_button variable is not blank when it hits the end of the %code% section, the xdialog will close.

          Here's how I do it - by setting an OK_pressed variable to .T. when ready to accept the entry and close the xdialog. If all requirements for closing the xdialog haven't been met, I simply reset a_dlg_button = ""
          clnt_list = <<%list%
          Client 1
          Client 2
          Client 3
          ok_pressed = .F.
          DIM dlg_result as C
          dlg_result = ui_dlg_box("CLIENT LOOKUP", <<%dlg%
          {font=MS Sans Serif,8,b}Other: {font=MS Sans Serif,8,n}[.15,1other_fld];
          {font=MS Sans Serif,8,b}Select Client:{font=MS Sans Serif,8,n};
          {justify=center}<*15OK> <15Cancel>
          IF left(a_dlg_button, 5) = "clnt_"
              IF a_dlg_button <> "clnt_dblclick"
                  a_dlg_button = ""
                  [COLOR=blue]'MOST of the time I do NOT use a double click to close an xdialog if 
                  'there are multiple fields to be filled in or multiple selections can 
                  'be made in the list simply because of the added confusion 
                  'for users and potential for mistakes.
                  'If other fields were available, an IF statement might be needed to 
                  'make sure it was properly filled in before changing "ok_pressed" to 
                  'True - just like in the last ELSEIF that checks for a_dlg_button = "OK"
          [/COLOR]        ok_pressed = .T.
              END IF
          ELSEIF a_dlg_button = "OK"
              IF other_fld = ""
                  msg = "Please enter some Other data or press 'Cancel' to quit."
                  ui_msg_box( "FIELD REQUIRED", msg )
                  a_dlg_button = ""
                  ok_pressed = .T.
              END IF
          END IF
          IF .not. ok_pressed
          END IF
          ui_msg_box( "SELECTION", clnt_sel )


          • #6
            Re: Close listview on double click


            Your 100% correct IF your just doing a plain xdialog, however, in Marks case, he was using the list view control. It is necessary in this case to explicitly close the dialog.

            The double click code is not in the "%code% section of the dialog, it is a function with in the object itself, kind of like a activeX control.

            If you play with one you will see what I mean.



            • #7
              Re: Close listview on double click

              Thanks for these insights. I thought that if I reset the a_dlg_button within the double click function, it would do as Cal describes, but it wouldn't. Adding the close did the trick
              Mark Pearson
              [email protected]
              Youtube channel


              • #8
                Re: Close listview on double click

                Sorry, I guess I wasn't paying enough attention. Thanks for correcting me.