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

Button properties - dashed lines on press

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

    Button properties - dashed lines on press

    I have been searching for about 2 hrs and cannot find any way to remove the dotted lines that appear when a button is pressed...

    It has been a while since I 'removed' that attribute while in V7.

    I can remember (altho possibly erroneously) changing that property but not where or how.

    It should not be a part of the form properties?????? But I have been there also.

    If anyone cares to point out the error of my 'searching' ways; please feel free.

    WWBB....
    D

    #2
    Re: Button properties - dashed lines on press

    Do you mean the tiny dotted lines that remain AFTER a button was last pressed and before focus is moved to another object on the form? If so, isn't that there as a visual cue for the user?

    Comment


      #3
      Re: Button properties - dashed lines on press

      May be, but it doesn't fit well into my 'visual cues'
      Knowing where you've been may not be that important as you move thru a menu or a form.....

      I can live with it, just doesn't look 'right' to me....
      D

      Comment


        #4
        Re: Button properties - dashed lines on press

        D, this hasn't bothered me, but then my vision isn't what it once was either :)

        Your button scripts can move focus to another object when they finish their work I suppose. In limited testing here this removes the dotted line from within the borders of the button. Maybe there's a more elegant solution, or an easier one, so I'll keep monitoring the thread.

        Regards,
        -- tom

        Comment


          #5
          Re: Button properties - dashed lines on press

          Just a follow-up to post the solution to the problem of the dotted lines....

          There is no way to get rid of those 'dotted lines' UNLESS you make the button NOT a tabstop..

          No tabstop, no dotted lines.

          D

          Comment


            #6
            Re: Button properties - dashed lines on press

            Thanks, D. That's good to know. -- tom

            Comment


              #7
              Re: Button properties - dashed lines on press

              Well; it might be good to know -- BUT it's wrong....
              I'm finding out that these pesky lines will SOMETIMES disappear if you make the button not a tabstop.

              Apparently what is happening is :

              I base all my menus on a dummy table a_menus.
              When I choose a button that is going to open a menu, the dots will not appear on the main menu. Since the sub menu is re-initiated each time it is called, there are no dotted lines to display.

              If I press a button that calls a form based on a table, dots appear..... and they will sometimes jump from the button I pressed to another button and it's always the same button (button12). It's at the top right of the main menu.

              I have no solution and am about to just let it go and live with the dots - or dashes or whatever.

              Just wanted to get the record straight.....................

              D

              Comment


                #8
                Re: Button properties - dashed lines on press

                D, when you say "menu" are you talking about a form that has buttons, or are you talking about the menu "for" a form, that lives at the top of the screen?

                Would help clarify things if you distinguish "menu form" from a "menu bar", since "menu" can refer to either. Thanks.

                Comment


                  #9
                  Re: Button properties - dashed lines on press

                  Sorry ---
                  put an answer on wrong thread...
                  be back
                  D
                  Last edited by dik_coleman; 07-18-2007, 10:12 PM. Reason: wrong thread

                  Comment


                    #10
                    Re: Button properties - dashed lines on press

                    D - I feel your pain. I HATE those dots. I'm going to guess that they jump to number 12 because something has to have focus.

                    I use hotspots instead of buttons, no dots.

                    - Elke

                    Comment


                      #11
                      Re: Button properties - dashed lines on press

                      Hot spots work just fine, but you need to put a text box UNDER the hotspot in order to get text on the button face and since the text box is UNDER the hotspot, you get no 'flyover effects' on the "button".

                      If the hotspot is UNDER the text box, it will not work.

                      Not necessarily bad, depends on what you want.

                      Thanx again
                      D
                      Last edited by dik_coleman; 07-20-2007, 10:16 AM. Reason: add

                      Comment


                        #12
                        Re: Button properties - dashed lines on press

                        Originally posted by dik_coleman View Post
                        Hot spots work just fine, but you need to put a text box UNDER the hotspot in order to get text on the button face and since the text box is UNDER the hotspot, you get no 'flyover effects' on the "button".

                        If the hotspot is UNDER the text box, it will not work.

                        Not necessarily bad, depends on what you want.

                        Thanx again
                        D
                        Put the fly over events on the hotspot object.

                        Comment

                        Working...
                        X