Hello Tom,

how can I disable an invisible object completely?

There is a button defined, which should be displayed or not displayed in dependent of an incoming signal from simulink.
Although the button is hide, you can click on its area and then the button's function is invoked. I thought, I can disable this functionality in the button control but it doesn't function.
How should I do that?

Thx again.

Merinus

Hello Merinus,

To allow disabling of a button completely, put the button in card 0 of a Deck object from the decks.dsn models library. Then, to disable it, change the Deck's card animation to 1 (or any value other than 0). Then the button is not shown and it cannot be pressed.

The Deck object from decks.dsn has a "Deck Current Card" animation that you can link to a signal from Simulink if a signal determines when the button should be available or not available.

If the Simulink signal is 1 to make the button available and 0 to hide it, then put the button in card 1 of the Deck instead of card 0.

The Deck object from decks.dsn has a group in its card 0 through card 9 and the group just contains text instructions for novice users. After entering a card, just delete this group containing the instructions.

_________________
Tom Walton
Altia, Inc.

Hello Tom,

I think your suggestion may not help me, because the button I want to show/hide is a tab, which should display/not display a deck

When the incoming signal from simulink is 1, the tab should have the normal view and function (that means pressing on that, should change into the deck refered to this tab). When the signal is 0, this tab should change its view (for example grayed out) and should not be pressable anymore (that means there is no deck changing possible).

I hope, you have a solution for me anyhow (as always)

Thank you very much.

Merinus

Hello Merinus,

You can still put the contents of the "tab" in its own deck different from the deck it is controlling. So card 1 of the tab's Deck shows the normal view of the tab. This card contains the normal view of the graphics. The stimulus to press on the tab is on one or more of the objects in this card. Then card 0 contains graphics for the disabled look for the tab and no stimulus to press on it.

Do you mean you are using a Tab Bar object for the tabs (from the tabbars.dsn models library)? If so, then it is a matter of "catching" the tabSelected event with a control WHEN block and forcing it to change back to the previously selected option. The full capabilities of the Tab Bar object are described in the Altia Design User's Guide, Chapter 6 - Models Libraries, Section 6.6.11 - Tab Bar Object.

If none of this is making sense, you may want to send an email to support@altia.com to ask for more help if you have support for your Altia Design software.

_________________
Tom Walton
Altia, Inc.