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

Improved "get_date" function.

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

    Improved "get_date" function.

    I don't like the way the ui_get_date() function works in v6/7 because it (a) requires the user to type the separator characters (a step backward from previous versions) and (b) that function has never allowed for more than one line of prompt text.

    Below is an xdialog solution. (Unfortunately it will lose its formatting when posted here. If you want a really good formatter to fix it, try the AIMS Script Formatter - it's free.)

    I've also attached a couple sample screenshots.

    Code:
    'Date Created: 14-Feb-2005 03:17:08 PM
    'Last Updated: 19-Oct-2006 02:38:05 PM
    'Created By  : Cal
    'Updated By  : Cal
    'SAMPLES - Can be unremmed to test function here but should be remmed before using the function from other scripts.
    '
    'in_text = <<%list%
    'This is some very long text that I want to display on the form and it will hopefully need to be word wrapped.
    '
    'Then i want to display something else that will also take up multiple lines when it is displayed when it is displayed.
    '%list%
    'ui_msg_box( "", dtoc( AIMS_Get_date("ENTER NEW COMPLETION DATE", in_text, date()) ))
    '
    'in_text = "This is the result with short text."
    'ui_msg_box( "", dtoc( AIMS_Get_date( "ENTER NEW COMPLETION DATE", in_text, date()) ))
    '****NOTE**** Do not create a new line in a crlf string unless you want to force a new line in the display.
    FUNCTION AIMS_Get_date as D ( Title_in as C, Prompt_in="" as C, Deflt_dt as A )
     'Set date val.
     DIM dt1 as D
     ON ERROR goto Is_char
     dt1 = Deflt_dt
     GOTO Start_calcs
     Is_char:
     dt1 = ctod( deflt_dt )
     
     Start_calcs:
     
     '--------------------------------------------------------------------
     'Determine width of display box.
     '--------------------------------------------------------------------
     'Set title width. (assume all caps)
     wsizet = len( trim( title_in ) ) * 2
     wsize = wsizet
     
     'Set base line count.
     ln_cnt = line_count( prompt_in )
     
     'Set a line count based on lines plus divide long lines into 90 char chunks.
     text_lines = 0
     blank_lines = 0
     max_line = 0
     FOR qx = 1 to ln_cnt
      this_line = word( prompt_in, qx, crlf() )
      line_len = len(trim( this_line ))
      IF line_len + 5 > wsize
       wsize = line_len + 5
      END IF
      IF line_len > 90
       wsize = 90
       text_lines = text_lines + ceiling( len(trim( this_line ))/90 )
       max_line = 90
      ELSEIF this_line = ""
       blank_lines = blank_lines + 1
      ELSE
       text_lines = text_lines + 1
       IF line_len > max_line
        max_line = line_len
       END IF
      END IF
     NEXT
     IF ln_cnt = 0 'No prompt so just make it long enough to handle the title.
      wsize = len( trim( prompt_in ) ) * 1.15 'Add a bit because different fonts react differently.
     END IF
     'Try to make sure the whole title shows up.
     IF wsizet > wsize 'only happen if wsizet > 90
      wsize = wsizet
     END IF
     IF (text_lines + blank_lines) > ln_cnt
      ln_cnt = text_lines + blank_lines
     END IF
     
     '--------------------------------------------------------------------
     ' Display it.
     '--------------------------------------------------------------------
     dlg_text = <<%dlg%
    {can_exit=ESC}
    {ysize=.3}{units=F}{sp};
    {region}
    {frame=1,5}
    {text=twidth,tlines:Prompt_in};{sp};
    [%DATE;P=popup.calendar(dtoc(dt1));I=popup.calendar%.17,1dt1!dt1_*];{lf};
    {endregion}
    {sp}{sp}{sp}
    {region}
    {sp};{sp};
    <*12OK>;
    <12Cancel>
    {endregion};
    %dlg%
    
     dlg_text = stritran( dlg_text, "tlines", ltrim( str( ln_cnt ) ) )
     dlg_text = stritran( dlg_text, "twidth", ltrim( str( wsize ) ) )
     
     DIM dlg_result as C
     dlg_result = ui_dlg_box( Title_in, dlg_text, <<%code%
    IF a_dlg_button = "ESC"
     a_dlg_button = ""
    END IF
    IF left( a_dlg_button, 4 ) = "dt1_"
     IF a_dlg_button = "dt1_killfocus"
      dt1 = ctod( dtoc( dt1 ) )
     END IF
     a_dlg_button = ""
    END IF
    %code% )
     
     IF dlg_result <> "OK"
      AIMS_Get_date = {}
     ELSE
      AIMS_Get_date = dt1
     END IF
     
    END FUNCTION  'AIMS_Get_date
    Last edited by CALocklin; 10-19-2006, 03:05 PM. Reason: Added .txt file - can't cut and paste from the Code section very well.

    #2
    Re: Improved &quot;get_date&quot; function.

    Ooops! A minor mistake on the FUNCTION line. The Deflt_dt as A should be:
    Deflt_dt="" as A

    This does two things: (1) the "as A" allows you to enter the default as either a character or date type and (2) adding the default Deflt_dt (="") makes it work more like the ui_get_date() function where the default value is optional. If you want the default date to always be "today" no matter where you use the function, change it to: Deflt_dt=date() as A

    Also note that the output from this xdialog method is an actual date - not a character value as it is in ui_get_date().

    FYI: Whenever a default value is specified in a list of function arguments, all arguments after that should also have a specified default. Another way of saying that is, all arguments with default values should be at the end of the argument list. (At least in v7 and earlier.) If this isn't done, since arguments must be entered sequentially, all values must be entered up through the last one without a default value. Alpha does not allow you to skip an argument just by typing commas. In other words, this would not work if you wanted to skip the prompt, which has a default value of "" (blank), using the function as originally posted: AIMS_get_date( "My Title", , "01/01/2006" )

    Comment

    Working...
    X