Changing readonly at runtime [message #1772687] |
Wed, 13 September 2017 20:45  |
Eclipse User |
|
|
|
Hi All,
Quick question. Is it possible to dynamically disable or otherwise make read-only a channel at runtime?
Consider the scenario where (for example) I have "Vol+", "Vol-" and "Mute" channels (switches). If someone triggers the "Mute" channel, the I would like to disable the "Vol+" and "Vol-" channels (switches).
I can't seem to find a way of doing this, so am wondering if:
a) it is possible? or
b) I have a design flaw in my thinking in relation to interrelationships between channels!
Thanks,
Jabba
|
|
|
Re: Changing readonly at runtime [message #1772712 is a reply to message #1772687] |
Thu, 14 September 2017 08:46   |
Eclipse User |
|
|
|
Hi,
I have a question about the functional requirements you are describing: Why do you want to prevent the user from altering volume when on mute? From my physical remote controls I expect to either unmute and start at the lowest possible volume when I change volume during mute or change volume and stay muted. One scenario: I go on mute to better hear the surroundings and then press Vol+ to fade in the music/tv sound again.
What do you think?
Cheers,
Henning
|
|
|
|
Re: Changing readonly at runtime [message #1772916 is a reply to message #1772773] |
Mon, 18 September 2017 17:02   |
Eclipse User |
|
|
|
Hi Guys,
The volume / mute was just an example. I agree that it may not be a great one! David, you are correct in saying (better than I did!) that I basically want to be able to disable certain channels under certain circumstances (eg: where functionality is not available as a result of the state of another channel). For example (a real one this time!)...I am creating a binding for an alarm panel. I have a channel to indicate when system is ready to arm (eg: it reacts to zones being open or faults being present etc...). It doesn't make sense for the "Arm Alarm" channel to be available when the "Ready to Arm" one is in the "not ready" state. Obviously, there is no harm in the user clicking the arm button, but it will not cause the alarm to Arm as there are open zones etc... However, from a usability point of view, it would seem to be better to have the arm channel disabled so that the user doesn't inadvertently select that option and think that they have done something etc...
David, I am guessing from your reply that this scenario is not supported? Eg: Programmatically disabling channels? Any other ideas or suggestions on how to achieve same? I haven't looked (yet) at creating a site map for the binding, but maybe I can disable through Javascript on same? (very hacky though!).
Thoughts?
Jabba
|
|
|
|
Powered by
FUDForum. Page generated in 0.03419 seconds