8 replies to this topic

[pscEx]

When working with the 'mandatory scripts' issue I got the feeling that the current solution of selecting / deselecting folders does not make much sence.

If you select / deselect a folder, all subfolders and their scripts are selected / unselected. Usually the result has to be manually adjusted.

My suggestion: Just select / deselect the folder and let the subfolders and subscripts untouched.

If during build, WinBuilder sees a deselected folder, it simply skips it w/o looking at all the childs.

Peter

[Galapo]

I really like this idea! But how would folders within folders work?

• Folder1
• script1
• script2
• script3
• Folder2
• script4
• script5

[/list][/list]
Regards,
Galapo.

[pscEx]

I really like this idea! But how would folders within folders work?

• Folder1
• script1
• script2
• script3
• Folder2
• script4
• script5

[/list][/list]
Regards,
Galapo.

In my idea, when any folder is deselected, everything below is not executed, regardless on checked or not.

Peter

[Galapo]

So scripts 4 and 5 in my example not run?

[Brito]

Why not publishing it as beta branch to see how it works?

I admit to have a few reservations regarding this proposed feature but I might also be wrong and would of course prefer to test it in action to evaluate if it works better or not than the current method along with other members.

This change might add (for example) the need for a right click menu whenever the user really wants to disable all scripts inside a folder or even remove some of the intuitive behavior.

This might as well prove to be an excellent improvement, let's test to see how it goes.

[Galapo]

And would 'Selected=always' override the folder deselection?

[pscEx]

And would 'Selected=always' override the folder deselection?

In my opinion: No.

See post #3:

In my idea, when any folder is deselected, everything below is not executed, regardless on checked or not.

This means also 'regardless on mandatory or not'

But again: Here is a lot of theory: I think this could be good for e.g. exclude / include e.g. the complete App folder etc.
Currently, If I exclude the App folder, everything is unchecked.
And if I want to include it again, it is rather laborious to go throug all scripts and decide on any of them whether to include or not.

Peter

[pscEx]

Why not publishing it as beta branch to see how it works?

I admit to have a few reservations regarding this proposed feature but I might also be wrong and would of course prefer to test it in action to evaluate if it works better or not than the current method along with other members.

This change might add (for example) the need for a right click menu whenever the user really wants to disable all scripts inside a folder or even remove some of the intuitive behavior.

This might as well prove to be an excellent improvement, let's test to see how it goes.

You can test tomorrow Monday night.
And in my opinion a context menu is not necessary.
To uncheck a folder implements the NON EXECUTE of all sub-folders and sub-scripts, regardless they are checked or not. So, to go back to the previous status, just re-check the folder.

Peter

[was_jaclaz]

In an "ideal" world (cannot say if there is a limit with the interface or list):
1) Checkbox for mandatory items would have a RED (instead of GREEN) tick
2) Left clicking a checkbox would toggle it on/off if GREEN
3) Shift+Left clicking a checkbox would toggle it on/off if RED
4) Left clicking a folder checkbox would toggle EVERYTHING under it on/off if GREEN, leaving untouched RED items
5) Shift+Left clicking a checkbox would toggle EVERYTHING under it on/off including RED items
6) a folder where only some items have been disabled should get a different colour tickbox, say YELLOW.

jaclaz