Gray out a disabled button

[gmeredith17]

Re: Gray out a disabled button

I'm not surprised. I don't recognize any of the functions you are using.

Stan the functions are in previous examples attached. See replies 9 and 10.

[[email protected]]

Re: Gray out a disabled button

Yeah, wrong code....my bad

It was simple adding the "button8.disable()" on the onarrive. It definitely disables that button; and I set the on depart to re-enable.

The crazy thing is that I can not get out of the focus on the browse that allows the button8.enable() to work.....

[Stan Mathews]

Re: Gray out a disabled button

"function is not recognized"

I'm not surprised. I don't recognize any of the functions you are using.

[[email protected]]

Re: Gray out a disabled button

Hi Stan,

I'm on a form with an embedded browse, so I guess that would be #2.

I added this xbasis to the onarrive:


ob_mode("button8",".f.") ' (object name, mode) - if mode =.t. then object will be set to ENABLED, if .f. then set to DISABLED
ob_fill("button8","gray-25","gray-50") ' (object name, fill color, fill accent color)
ob_flyover("button8","gray-25","gray-50") ' (object name, fill color, fill accent color)
ob_flyoverleave("button8","gray-25","gray-50") ' (object name, fill color, fill accent color)

and I get this error "function is not recognized" line 5

Ryland

[Stan Mathews]

Re: Gray out a disabled button

as long as a browse is open.

Are you opening the browse outside of the form (1) or do you mean while a browse, on a form, has focus (2)?

(1) A form has OnActivate and OnDeactivate events

(2) An embedded browse has onarrive and ondepart events.

[[email protected]]

Re: Gray out a disabled button

This is a follow on to this. I need to have a button disabled as long as a browse is open. Just not sure how to disable the button once the browse gets focus, and enable once the browse is out of focus......any ideas..Ryland

[Bob Whitaker]

Re: Gray out a disabled button

That kind of repeats what I normally do except as previously stated I have a conditional object on the form and place the buttons in the conditional object - in the "working" condition the buttons function as normal in the "disabled" condition I place an identical copy which has no events - is set to grey on grey and has the flyover settings disabled. I use the alignment tools and settings to ensure both versions are placed in exactly the same position. Using this methodology we can have different buttons available for different users based on their login security settings. But would be nice to be able to set conditions directly on the button though.

Bob

[danh]

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

[Bob Whitaker]

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

[gmeredith17]

Re: Gray out a disabled button

Thanks Mike.

[MikeC]

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.

[gmeredith17]

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.

[MikeC]

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.

[gmeredith17]

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.

[MikeC]

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 .