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

Gray out a disabled button

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

    Gray out a disabled button

    How do I make a disabled button look disabled? I am using the command; topparent:btnNotes.disable() to disable it, and it works, but it doesn't change the way it looks. I would like it to look grayed out. What's the trick?

    Thanks, Dan
    - Dan Hooley
    - Custom Desktop or Web database development -

    #2
    Re: Gray out a disabled button

    Look in the help index for "Button" and under the list for "Properties". Or...

    http://support.alphasoftware.com/alp...Properties.htm

    There you will find all the different ways you can affect a button.

    Comment


      #3
      Re: Gray out a disabled button

      I've looked at all that. So I take it there is no easy "trick" to it... I'm going to have to roll up my sleeves and go to work if that is what I want. I was just hoping there was something simple that I was missing. I am surprised thats not built-in. I could do it 15 years ago in Access:)!! Come on Alpha!

      Dan
      - Dan Hooley
      - Custom Desktop or Web database development -

      Comment


        #4
        Re: Gray out a disabled button

        The nice thing about doing it this way is that you can make it look any way you want. Some want it different colors and some just "hide" it so that it appears to be gone. Plain and boring we can leave to Access. I like the ability to have it my way!

        :formname.controlname.object.enabled = .F. <-- You have this already
        :formname.controlname.font.color = "Gray-25" <-- You have to add this

        Doesn't seem too difficult!
        Last edited by Doug Page; March 06, 2009, 09:17 PM.

        Comment


          #5
          Re: Gray out a disabled button

          Might be something to ask for in the Wishlist forum--to have an option to check that would automatically create a default "gray-out" of a disabled field/button/etc.. That way we can have it both ways! Simple(r) and Custom.
          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


            #6
            Re: Gray out a disabled button

            :formname.controlname.font.color = "Gray-25"
            Doug, that would be great if it was just that simple. But what do you do about fly-over affects? We need a simple way to temporarily disable those so the button stays looking disabled even when the mouse is moved over it. Maybe I am missing something.
            - Dan Hooley
            - Custom Desktop or Web database development -

            Comment


              #7
              Re: Gray out a disabled button

              Dan - I agree with you but with a little work you can get the effect you want.

              You can put something like the code below in the onflyover and onflyoverleave events. Obviously it is down to you decide on the colours you want to use.

              Code:
              DIM SHARED button_mode AS C
              button_mode = parentform:Button1.object.enabled
              
              if button_mode="T" then 
              	this.border.color = "-L10System-ThreeDShadow"	  
              	this.fill.color = "-L5System-ButtonFace"	.
              	this.fill.accent_color = "+L5System-ButtonHighlight"	
              
              	else
              	
              	this.border.color = "-L10System-ThreeDShadow"	
              	this.fill.color = "gray-25"	'
              	this.fill.accent_color = "+L5System-ButtonHighlight"
              
              end if

              Comment


                #8
                Re: Gray out a disabled button

                If you are to do this for many buttons/fields/etc., I would suggest creating a UDF of this script so that if changed you only have to change the function that is called and not every script. Much, MUCH less maintenance!! And if you want different colors for various buttons/fields....well that could be incorporated into the function as an argument .
                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


                  #9
                  Re: Gray out a disabled button

                  Good idea Mike.

                  I've attached my attempt at this and would welcome others opinions, improvements or methods for achieving this as I'm sure it is a common enough requirement.

                  I've only tested it with buttons so the functions may need tweaking with other objects.

                  Comment


                    #10
                    Re: Gray out a disabled button

                    Hi Geoff,
                    Got back to this finally and took a few minutes to add to your functions...actually just made it into one function (ob_enable() )with an additional addin_help() function that if run prior will usually bring up the color picker for making choices....the addin_help() function can be placed in an autoexec or the addin folder as well.

                    I only used it for a button on the sample form as well so more testing would be necessary as you stated for other objects.

                    EDIT LATER:I made everything except for the first argument, which is for the object name, default to ".T." for enabling and "" for color. That way a value does not have to be placed in any argument but the first if so desired.

                    Last edited by MikeC; March 12, 2009, 01:56 AM.
                    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


                      #11
                      Re: Gray out a disabled button

                      Thanks Mike - very much appreciated.

                      additional addin_help() function that if run prior will usually bring up the color picker for making choices....the addin_help() function can be placed in an autoexec or the addin folder as well.
                      I can't seem to get this to work and seem to be having a bad 'help file' day. Any tips or guides to getting it to work? I haven't created aex files or addins before so starting from ground zero.

                      I made everything except for the first argument, which is for the object name, default to ".T." for enabling and "" for color. That way a value does not have to be placed in any argument but the first if so desired.
                      Thanks for that I wondered how it was done.

                      Comment


                        #12
                        Re: Gray out a disabled button

                        Geoff,
                        I got a bit tied up so just got on the board now...

                        The easiest way I get the addin.function_argument_help() functions to work is to make them into a function themselves as I did with the addin_help() UDF I made and then placing this function into the autoexec of the database I am using--that way the addin.function_argument_help() functions run on startup. Or have had decent luck creating an AEX from a database with an empty Code tab so that the only functions in the AEX are these help functions...this AEX then in placed in the "addins_installed" folder of your Alpha install folder (has been relocated in some versions so have to find it!! :) ). The AEX files in this folder are also run on startup.

                        Until you are used to it, it can be a PITA to do....but especially in this function it is nice to have the dropdown color-picker as you can then choose or even make your own color choices instead of doing so elsewhere and then typing it into the function.
                        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


                          #13
                          Re: Gray out a disabled button

                          Thanks Mike.

                          Comment


                            #14
                            Re: Gray out a disabled button

                            Another approach is to put the buttons inside a conditional object.

                            It would be great if there was a disable option in a buttons properties that automatically greyed it out.

                            Perhaps you should add it to the wish list !

                            Bob
                            Bob Whitaker

                            Comment


                              #15
                              Re: Gray out a disabled button

                              In the examples, the flyover affects still change the look of the button, even after it's disabled. I tried a similar approach and got the fly-over effects disabled, but ran into problems when using topparent.new_record() (unrelated function). It wouldn't go to the new record. Not sure why, didn't dig into it very far, but...

                              Here's another approach... see attached, far right buttons.

                              Essentially, it's putting another button on top (or underneath) of the button you want to disable, and setting the colors to the look you want, un-checking the fly-over effects, and then hiding one and showing the other. It takes another object, but very little coding.

                              Again, this works for buttons, not sure about other objects.

                              I agree this should be built-in, and would have thought it would have been addressed long ago. I would suggest another check box under fly-over affects in properties to check and then select the look you want when it's disabled.

                              Dan
                              - Dan Hooley
                              - Custom Desktop or Web database development -

                              Comment

                              Working...
                              X