hiding a group does not hide its members

[dunbarx]

BOY DID THIS throw me for a while.

Hiding a group of controls hides the group but not the child controls of that group. The visible of the group is "false". The visible of the children are "true". You cannot see those controls, but their visible is nonetheless "true".

Is there a property where the visible is true but the "visible" is false?

Everyone but me knew that???

Craig

[Klaus]

Hi Craig,

sorry, don't get your problem?
Hiding a group will of course also hide its "content", no matter if the controls inside of the group are visible or not.



Best

Klaus

[dunbarx]

Ah. There is always the "showInvisibles" property. The dictionary states:

"Specifies whether invisible objects are shown anyway."

"Anyway"...

and

"Invisible objects that are temporarily shown with the showInvisibles property respond to mouse clicks and key presses as though they were visible.

"Visible"...

So there is a, er, gray area where invisible controls can be made visible. Hmmm, is that anything like setting their visible property to "true"? Yes it is. But that is not the same as having their visible property set to true, but still not seeing anything.

Craig

[dunbarx]

Klaus.

Code: Select all

Hiding a group will of course also hide its "content", no matter if the controls inside of the group are visible or not.

If I hide the content, I expect the "visible" property of that content to be "false", not true. Don't you?

I wanted to deal with the visible controls differently than the hidden ones. So after hiding the group that contained certain buttons, I stupidly wrote a handler:

Code: Select all

 repeat with y = 1 to the number of btns
 if the visible of btn y then do stuff to btn y

And what do you know? The hidden buttons all were subjected to having stuff done to them.

Craig

[dunbarx]

Klaus.

So say I have a card with four buttons. I group two of them and then hide that group. Can you suggest an easy way to act on the visible buttons but not the, um, er, you know, invisible ones?

Do I need a new property, the "cantActuallySeeButStillNonethelessVisibleIsTrue" property?

Craig

[dunbarx]

Unless I have this completely wrong, I will have to not simply hide the group, but rather move it off the card. Then the only visible buttons in play will be the ones that are actually visible.

Craig

[Klaus]

Klaus.

Code: Select all

Hiding a group will of course also hide its "content", no matter if the controls inside of the group are visible or not.

If I hide the content, I expect the "visible" property of that content to be "false", not true. Don't you?

No, I don't!
Their VISIBLE property is still TRUE, but we cannot see them, so I still don't get your problem.

[dunbarx]

I am posting a la Richmond.

Since moving them off the card is a real pain to manage I will set a custom property of each before hiding, and use that as a way to distinguish certain visible buttons from other certain visible buttons.

Craig

[dunbarx]

No, I don't!

Exclamation point?

But why? They are invisible buttons (at least to my eyes) that have their visible property still set to "true". I want to distinguish them from their, er, visible brethren when running another process.

The custom property will do the job, though unnecessarily complex. I suppose I could also not deal with any control that is owned by an invisible group.

You do not agree this seems odd?

Craig

[dunbarx]

Klaus,

I see your addition to your post. Recall I wrote earlier:

So say I have a card with four buttons. I group two of them and then hide that group. Can you suggest an easy way to act on the visible buttons but not the, um, er, you know, invisible ones?

I thought I could use the visible property to do that.

Nope.

Craig

[dunbarx]

Klaus.

Their VISIBLE property is still TRUE, but we cannot see them,

I know you are not joking. I cannot understand why.

Craig

[Klaus]

This is how LC works and may differ from real life!

Imagine it would be as you see it, then we would need to set the visible of ALL controls in the group to visible again,
but LC does this for us by ALSO hiding all controls when hiding the group but NOT changing their VISIBLE property.

So this behavior is completely logical to me.

[bn]

Craig,

try

Code: Select all

put the effective visible of button 1

tested in 10.0.0 RC1

Kind regards
Bernd

[Klaus]

"the effective visible"!!?
Go figure!

[SparkOut]

Ha, I was reading through this thread and starting to scroll through with the thought "I wonder if it's worth asking to check for the 'effective visible' of an object to test inheritance?"
Turns out it is! and was answered by the time I got to the bottom of the thread. (Or before, I mean it's not like I was reading at the same time as Bernd and Klausimausi posting.)