Hello, Enable/disable attribute concerne two different use case :
1- Generic problem related to some boolean already present in many components that may will interessant to have a generic solution to also have the possibility to use expression. 2- Evaluate enable at runtime, actually enable is used before test to filter component, and I think each case (listener, controller, sampler, ..) will be adapted especially to have this feature. I think this two concepts should be resolved in separate way. Best regards On Thu, Nov 25, 2021 at 9:45 PM Vladimir Sitnikov < [email protected]> wrote: > By the way, in order to make enabled/disabled state dynamic, TreeCloner > should > automatically convert "enabled expressions" into > IfController(condition="enabled expression") { originalComponent(...) } > > Then we won't need to touch executor logic, and we would get automatic > support for all the plugins. > WDYT? > > ---- > > >How would you trigger those modes? Another checkbox? > > It could be a checkbox in the menu. > Here's one of the discussions on that: > https://lists.apache.org/thread/lzdoljpwr9kzm4kqns9cyz1v45ppo19d > > >I think it is important to have the two boolean states plus a third form > >to be able to convert older checkboxes to such a new ui element without > >breaking the old save format. > > If checkbox + edit is UI only feature, then > "boolProp" => boolean value > string "true" => true > string "false" => false > else => treat as expression (third state) > > So far it looks ok. We should be able to read old files, and as we save we > could save it as "stringProp" always. > > Vladimir >
