|Re: Setting variables for the "Disabled"-property [message #1720809 is a reply to message #1720702]
||Thu, 21 January 2016 08:48
| Ed Merks
Registered: July 2009
On 20/01/2016 12:06 PM, Tim Schmid wrote:
> Hey everyone,
> I just wanted to ask if it would be possible to allow variables (a
> Boolean) for the "Disabled"-property to be able to build up the setup
> even more generic.
No, not really. It seems simple to support at first glance, but the
whole process of gathering tasks, merging them, ordering them, and
evaluating all the variables involved is highly complex. One of the
first steps it to gather all the tasks; at this point, disabled tasks
are not gathered, so for example, a disabled compound tasks that could
contain a bunch of variables, could be disabled such that none of the
contained variables would gathered. Only later in the process are
variables evaluated such that the references to them are replaced with
the evaluation result.
> For example you could provide checkboxes in the variable screen of the
> installation to disable/enable tasks then, which is easier for the
> user of the setup than disabling/enabling the task itself in the
> confirmation screen (primarily because of the labels, which are not
> that cryptic).
With the current design, tasks that the user may or may not want to have
performed could be grouped in a separate (perhaps nested) project so
that they select that project's stream if they want those tasks, or
don't select it if they don't want it. I.e., the choice happens earlier
in the process when the streams are chosen...
> Thanks in advance and best regards,
Powered by FUDForum
. Page generated in 0.01933 seconds