If/Then/Else no longer available in sdef? [message #1142440] |
Thu, 17 October 2013 16:21  |
Eclipse User |
|
|
|
Has support for If/Then/Else been removed from the sdef? If so what is the preferred way to implement this functionality? I checked the migration guide but may have missed it.
Along the same line... what is the preferred way to disable an actuator? I have tried adding a Condition class but this does not seem to affect the behavior.
|
|
|
Re: If/Then/Else no longer available in sdef? [message #1142447 is a reply to message #1142440] |
Thu, 17 October 2013 16:28   |
Eclipse User |
|
|
|
Hi Paul,
Now I believe the correct thing to use is Visible when expressions. They are much nice than if/then/else and makes the SDEFs more readable IMHO.
For disabling the Actuator are you wanting it to not be visible in UI or just simpled 'disabled/grayed'?
|
|
|
Re: If/Then/Else no longer available in sdef? [message #1142482 is a reply to message #1142447] |
Thu, 17 October 2013 17:00   |
Eclipse User |
|
|
|
Quote:Now I believe the correct thing to use is Visible when expressions.
That's right. A few of the constructs in sdef where we have functional overlap have been eliminated in 0.7 code line recently. I am still working on updating the migration guide.
|
|
|
Re: If/Then/Else no longer available in sdef? [message #1142533 is a reply to message #1142440] |
Thu, 17 October 2013 17:41   |
Eclipse User |
|
|
|
Thanks guys for the confirmation... that's the path I was suspecting.
Quote:For disabling the Actuator are you wanting it to not be visible in UI or just simpled 'disabled/grayed'?
Suggestions on either case (visible or) would be helpful. I kept thinking there should be a 'visible when' on the actuator.
|
|
|
Re: If/Then/Else no longer available in sdef? [message #1142540 is a reply to message #1142533] |
Thu, 17 October 2013 17:48   |
Eclipse User |
|
|
|
There is visible-when support for the actuator, but it looks like the sdef editor is missing that property. Could you open a bug?
As for the option of controlling enablement, you take care of that in your action handler implementation via the setEnabled method.
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04541 seconds