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

dynamic small list xdialog as buttons

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

    dynamic small list xdialog as buttons

    Hi,
    I don't know if this will have any use for anyone, but I thought I would throw it out there.

    I am lazy. I use alot of displays for the user to make choices. I have typically used list dialogs presented to the user from a form button for this purpose. With the form button :
    1. The xdialogs present the selection choices as a list in a list dialog to the user for selection.
    2. The user selects the item.
    3. The user presses the OK button.

    The great advantage in above approach is the input list size can be variable and list box will accomodate it with the list and a scroll bar to access the list items beyond the lists hard coded size. This can be changed with special coding but it is still is a three step process. Why not a two step process for small lists? Display an xdialog that dynamically presents selections as buttons instead of a list requiring list selection and a button press.

    The blue sort buttons compare the two ways for presenting the user choices dynamically in an xdialog, one as a list and the other as dynamic xdialog buttons. It works for small lists that may change. I thought I would throw it out there for fun. The Navigator button also works code that displays the dynamic xdialog as buttons.
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    #2
    Re: dynamic small list xdialog as buttons

    The above database got me in a never ending loop giving the message

    Code:
     That I should send the following line to Alpha technical - Source code (not on your machine) C:\Dev\a5v9\src\LANGUAGE\EXPR\sysevent.cpp at line 281.
    Beware!!

    some nice stuff in there though

    bug report sent

    Comment


      #3
      Re: dynamic small list xdialog as buttons

      Odd,
      I downloaded this on a few machines and I got no issues.
      Mike W
      __________________________
      "I rebel in at least small things to express to the world that I have not completely surrendered"

      Comment


        #4
        Re: dynamic small list xdialog as buttons

        Have not seen one of these type messages since version 5!! but it is there, just ran it again and have to use task manager to close Alpha 5

        Comment


          #5
          Re: dynamic small list xdialog as buttons

          Lance,
          I downloaded this to a few machines... no problem. However, there are two dim statements in lines #17 & 18 of the company_sort() UDF that should not be there:
          Code:
          dim shared vLenum as N
          dim shared vwide as N
          I have my xdialog font system settings to Arial,10, as in the script, so I do not see a vertical scroll bar in the list dialog.
          Mike W
          __________________________
          "I rebel in at least small things to express to the world that I have not completely surrendered"

          Comment


            #6
            Re: dynamic small list xdialog as buttons

            This tells me the Xexitlock script run on startup through the autoexec somehow is not running. The error you are seeing is from running the code on the exit button which is supposed to fulfill the can_database_exit() lock established in the Xexitlock script.
            Mike W
            __________________________
            "I rebel in at least small things to express to the world that I have not completely surrendered"

            Comment


              #7
              Re: dynamic small list xdialog as buttons

              Not having any problem here using version 8--I can use the form's "X" to close however but no errors.

              I have never used the system_event_drop() function but seems to me that maybe it should be
              Code:
              system_event_drop("database_exit", "1")
              instead of what you placed:
              Code:
              system_event_drop("database_canexit","1")
              Just a guess from my limited reading of it.


              ---Mike, in what version was this created??? --always nice to know when trying out samples and such!
              Mike
              __________________________________________
              It is only when we forget all our learning that we begin to know.
              It's not what you look at that matters, it's what you see.
              Henry David Thoreau
              __________________________________________



              Comment


                #8
                Re: dynamic small list xdialog as buttons

                Mike,
                The docs says system_event_drop("database_exit", "1") but that does not work in my hands. Only system_event_drop("database_canexit", "1") works for me. And you apparently.

                Lance,
                Run this and see if it works. If you get an error run it as ptr.database_canexit and see what happens.

                Code:
                 dim ptr as P
                ptr = system_event_data_get()
                ? ptr.database_exit
                This code originated in v7 and the example finished in v9. Thanks for the heads up re: the version being exampled. Usually it is in a particular forum so that needs not be said.
                Mike W
                __________________________
                "I rebel in at least small things to express to the world that I have not completely surrendered"

                Comment


                  #9
                  Re: dynamic small list xdialog as buttons

                  Ran the code as requested in the interactive window and got the following
                  Code:
                  ERROR: Unexpected internal Alpha Five error.
                  Please send the following information to technical support at Alpha Software.
                  Source code (not on your machine) C:\Dev\a5v9\src\LANGUAGE\EXPR\sysevent.cpp at line 444.
                  ptr.database_exit subelement not found.
                  Therefore what I am seeing is an internal Alpha 5 error, which was reported to them on Friday, no news yet

                  Comment


                    #10
                    Re: dynamic small list xdialog as buttons

                    Here are some tips based on my experience with the function 'SYSTEM_EVENT_DATA_GET()'. It exhibits some petulant behavior resulting in obscure error messages just like those mentioned above. The A5 documentation gives examples but they only work in the interactive panel. If you try them in your Xbasic script you will get an error of the type shown.

                    It's easy enough to create and delete system events using the Xbasic syntax 'ON_DATRABSE_...()' and 'SYSTEM_EVENT_DROP()'. Testing for events becomes somewhat more troublesome though as there appears to be no readily available syntax to do this.

                    What I have found though is that use of a pointer in conjunction with the function 'PROPERTY_TO_STRING()' circumvents the error messages, albeit at the expense of possibly needing to decipher the cryptic response. But that's not an insurmountable problem.

                    So here is an example:

                    Code:
                    Dim ptr as P
                    ptr=SYSTEM_EVENT_DATA_GET()
                    '
                    '  Syntax such as ptr.database_exit.1 only works in the interactive panel.  So ...
                    '
                    Dim varC_EventText as C
                    varC_EventText = property_to_string(ptr.database_exit.1)
                    if varC_EventText = ""		' No event registered.
                       ...
                    else				' Event is registered.
                       ...
                    end if
                    You have to be careful using 'SYSTEM_EVENT_DROP()' too. If you try dropping an event that does not already exist you will end up again with one of those obscure Alpha5 error messages. So you have to test for it first (as per my sample code above) before dropping.

                    IMHO I think some tinkering by the good folk at Alpha Software would help make 'SYSTEM_EVENT_DATA_GET()' a little more developer friendly.

                    Comment

                    Working...
                    X