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

Multiple Lines In ui Box

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

    Multiple Lines In ui Box

    I have done this before but for some reason it is not working. Whenever this box appears it only shows
    Enter Computer Number

    I am attempting to get it to read like this:

    Enter Computer Number
    0 For Chris Computer
    1 For Phil Computer

    computer=val(ui_get_number("What Is Your Computer Number","Enter Computer Number"+chr(10)+"0 For Chris Computer"+chr(10)+"1 For Phil Computer"))

    Where oh where have I gone wrong?

    Thanks

    #2
    RE: Multiple Lines In ui Box

    Philip,

    Chr(10) is a line feed. Chr(13) is a carriage return. Use Chr(13) as well, as in

    computer=val(ui_get_number("What Is Your Computer Number","Enter Computer
    Number"+chr(13)+chr(10)+"0 For Chris Computer"+chr(13)+chr(10)+"1 For Phil Computer"))

    I believe it will work with just the chr(13), but it is best to use both (for long term stability between versions)

    Regards,

    Ira J. Perlow
    Computer Systems Design & Associates
    [email protected]
    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


      #3
      RE: Multiple Lines In ui Box

      Interesting. I've never tried that with ui_get_number, etc.

      This technique works fine with ui_msg_box. However, it doesn't work with any other ui_... commands!
      For those not familiar, here's how it works:
      - Using either chr(10), chr(13), or the combination of chr(10)+chr(13) will create a single line feed in the middle of the string.
      - Using chr(10)+chr(10) or chr(13)+chr(13) will create a double line feed. (I use this a lot!) However, note that the combination of the two, chr(10)+chr(13), will only create only a single line feed.
      All the above not withstanding, my previous programming training (little as is was) tells me that Ira's right - the best form would still be to use the combination.
      EXAMPLE:
      ui_msg_box( "HEADER", "This is line one." +chr(10)+chr(13)+ "This is line 2.", ui_ok_cancel )

      Comment


        #4
        RE: Multiple Lines In ui Box

        Philip,

        I use multi-line message boxes a lot so I simplify things for myself by declaring a global variable "CrLf" in an autoexec script, which loads every time I bring up Alpha Five:

        DIM CrLf as B
        CrLf = CHR(13)+CHR(10)

        This way, I can throw it in whenever I need it. In addition, I declare a Tab [CHR(9)] variable as well because I have found it useful in some situations as well. You can simply put in CHR(13)+CHR(10) if you wish (I prefer using both as well, Ira, for the same reasons), but it just seems more convenient to use the variable. (CrLf is a hold-over from Visual Basic -- some might find it easier calling it "Newline", etc.)

        Regards,

        Geoff Hollander

        Comment


          #5
          RE: Multiple Lines In ui Box

          Ira,
          Still a NO GO...

          I even eliminated the chr(10) to see if there would be any changes and same old thing. Only the one line. Because this is a ui number box, would that make a difference than if it was a ui message box?

          Thanks

          Comment


            #6
            RE: Multiple Lines In ui Box

            Cal,
            Your statement...

            This technique works fine with ui_msg_box. However, it doesn't work with any other ui_... commands!

            Is this from your experience or is this documented somewhere?

            Thanks

            Comment


              #7
              RE: Multiple Lines In ui Box

              Philip, I've hit line length limits in the other ui dialogs (including ui_get_number), but not ui_msg_box. It does not surprise me that multiple lines are not supported. The title and caption text of the dialog box seem to assume that your prompts will fit within the allowable space in the dialog.


              My guess is that you're trying to use the dialog in ways that weren't anticipated when they were designed.

              Comment


                #8
                RE: Multiple Lines In ui Box

                Phillip,
                The ui_get_number and most of the other ui's except for ui_msg_box appear to be designed for one line with a limit of display characters. If it's essential to have a multi-line display message when you collect the number you could use a dialog form. Or a message box appearing just before the entry of the number.

                Comment


                  #9
                  RE: Multiple Lines In ui Box

                  It's not documented as far as I know. Your question made me curious so I opened the Code Editor's 'Interactive' window and ran a few tests of my own.

                  Comment

                  Working...
                  X