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

The UI_Get_Short_Time() Function

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

  • The UI_Get_Short_Time() Function

    I find the UI_Get_Short_Time() function to be a very neat way to enter short time. The user can type in the desired time or move the hands of the clock whichever they wish. However, it presents one minor mystery. Namely, the "Cancel" button.

    It displays both an "OK" and a "Cancel" button. It returns the selected short time as a character. I cannot find any way whatsoever to determine whether the user hit the "Cancel" button. It always returns a character type shorttime.

    Is this a shortcoming of the function or am I missing something?

    Steve

  • #2
    Re: The UI_Get_Short_Time() Function

    Steve,

    I ain't got no UI_Get_Short_Time()? Are you sure that it's not one of your own UDFs?
    Peter
    AlphaBase Solutions, LLC

    Peter@AlphaBaseSolutions.com
    https://www.alphabasesolutions.com


    Comment


    • #3
      Re: The UI_Get_Short_Time() Function

      Peter,

      Just start typing it in the interactive and it will start to autocomplete.

      Steve,

      I'd call it a bug, just like you can't cancel ui_get_date_calendar().
      There can be only one.

      Comment


      • #4
        Re: The UI_Get_Short_Time() Function

        Originally posted by Stan Mathews View Post
        Peter,

        Just start typing it in the interactive and it will start to autocomplete.
        Hhmm...

        It does pop up in the interactive, but I get this:

        ? ui_get_short_time()
        ERROR: Not an executable file

        It's not in the help file?
        Peter
        AlphaBase Solutions, LLC

        Peter@AlphaBaseSolutions.com
        https://www.alphabasesolutions.com


        Comment


        • #5
          Re: The UI_Get_Short_Time() Function

          You have to supply at least the dialog title and default time, both character.

          ? ui_get_short_time("When",time())
          = "10:58:00 00 am"

          It's not in the help file?
          Something surprising to you in that?

          Actually, it is in the inline docs.

          ui_get_short_time() Function
          Prompts desktop user for a short time value.
          Syntax:
          C shorttime = ui_get_short_time(C dlgTitle ,C time [,L clockConnectHands [,N clockHourSnap [,N clockMinuteSnap [,L clockShowNumericInput ]]]])
          There can be only one.

          Comment


          • #6
            Re: The UI_Get_Short_Time() Function

            Originally posted by Stan Mathews View Post
            You have to supply at least the dialog title and default time, both character.

            ? ui_get_short_time("When",time())
            = "10:58:00 00 am"

            Something surprising to you in that?

            Actually, it is in the inline docs.
            You're right.

            I searched the function with the () so it didn't show.
            Peter
            AlphaBase Solutions, LLC

            Peter@AlphaBaseSolutions.com
            https://www.alphabasesolutions.com


            Comment


            • #7
              Re: The UI_Get_Short_Time() Function

              Thanks, Stan & Peter. I guess it is a bug. But I'll just live with it and accept it since it isn't causing any major grief - just refreshing the field with a time whether you cancel or not. I suppose the user can get used to that. Thanks again.

              Steve

              Comment


              • #8
                Re: The UI_Get_Short_Time() Function

                Hi Stan,

                Originally posted by Stan Mathews View Post
                Steve,

                I'd call it a bug, just like you can't cancel ui_get_date_calendar().
                No, it's not a bug. If you put in a default time (which you must, as the function didn't default to the current time in the function parameter list), then change the time in the dialog and hit cancel, you get the default time value. If you hit OK, you get the new value. And this is as it should be.

                What you are really missing is a 3rd button (should be optional) to abort the process that the function is part of.

                There is nothing (IMHO) more irritating than starting a process, say printing a report, getting a whole lot of inputs for the filter via ui, then half-way through the prompts, realizing that wasn't what you want, but still being forced to enter through many additional UI prompts.

                Having an abort method, though, is already there on this dialog. It is the upper-right close box "X". When you press this key, it returns the default time (wrong), as opposed to a null string (right way), which could have been used in a test after the ui dialog to decide what to do in the code on an abort.

                Examples I used for testing are
                ?ui_get_short_time("Get Time",time())
                ?ui_get_date_calendar("Get Date",dtoc(date()))

                Note that in ui_get_date_calendar(), that a mouse click on a day implicitly selects OK. However, if you use the cursor keys to move to a different date, it does not, and that's how you can check the difference between OK and cancel
                Regards,

                Ira J. Perlow
                Computer Systems Design


                CSDA A5 Products
                New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                CSDA Barcode Functions

                CSDA Code Utility
                CSDA Screen Capture


                Comment


                • #9
                  Re: The UI_Get_Short_Time() Function

                  I see your point. I suppose one could get a "null" result on cancel with.

                  Code:
                  ? ui_get_text("Nonsense","Enter some text")
                  = ""
                  
                  ? ui_get_date_calendar("Nonsense",dtoc({}))
                  = ""
                  
                  ? ui_get_short_time("Nonsense",time("00:00:00 00"))
                  = ""
                  There can be only one.

                  Comment


                  • #10
                    Re: The UI_Get_Short_Time() Function

                    Hi Stan,

                    Originally posted by Stan Mathews View Post
                    I see your point. I suppose one could get a "null" result on cancel with.
                    ? ui_get_date_calendar("Nonsense",dtoc({}))
                    = ""
                    In this case, the default date is always today's date (which means you can't preset it to something else)

                    Originally posted by Stan Mathews View Post
                    ? ui_get_short_time("Nonsense",time("00:00:00 00"))
                    = ""
                    ? ui_get_short_time("Nonsense",time("12:00:00 00"))

                    returns the same null value. In this case, I'd say the returned value of null is a bug, as you can never set the time to 12 midnight. Makes the function useless in my point of view (unless you correct it after leaving the dialog box)

                    I have replacements for these Alpha functions (as well as many others) that don't exhibit these anomalies, have defaults that should be there, and typically run cleaner and faster, but then I spend a lot more time on the replacements than the original coding.
                    Regards,

                    Ira J. Perlow
                    Computer Systems Design


                    CSDA A5 Products
                    New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                    CSDA Barcode Functions

                    CSDA Code Utility
                    CSDA Screen Capture


                    Comment


                    • #11
                      Re: The UI_Get_Short_Time() Function

                      ? ui_get_short_time("Nonsense",time("12:00:00 00"))

                      returns the same null value. In this case, I'd say the returned value of null is a bug, as you can never set the time to 12 midnight. Makes the function useless in my point of view (unless you correct it after leaving the dialog box).
                      Hi Ira,

                      I would prefer putting in the current time as the default rather than midnight. That is so that if they want to enter a recent time (say, 20 minutes ago), there would be only a minor adjustment. But using midnight as the default, they would have plenty of winding on the hands (or entry into the numerical portion of the dialog) which defeats the user-friendliness of this function. You may as well have a character-based user-entry field.

                      When using the current time as the default, I have no way of knowing whether they pressed "OK" or "Cancel". If I did have a way, I would blank out the field upon their pressing "Cancel".

                      Steve

                      Comment


                      • #12
                        Re: The UI_Get_Short_Time() Function

                        Originally posted by csda1 View Post
                        I have replacements for these Alpha functions (as well as many others) that don't exhibit these anomalies, have defaults that should be there, and typically run cleaner and faster, but then I spend a lot more time on the replacements than the original coding.
                        I for one, would really like to see those functions!
                        Robin

                        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                        Comment

                        Working...
                        X