GeneFC wrote:I have been testing the improvements, and they appear to work correctly. They definitely clean up a couple of quirks in the tool handling.
I have discovered one "improvement" that creates a bit of difficulty for me. In particular, the post processor operation appears to always process the entire job with all of its path operations instead of processing only the selected path operation(s). Is this intentional?
It is intentional, but that doesn't mean it's right
The job has become more complex and contains a lot of the context that operations are executing with. When you post-process a single operation, you probably don't really want to post the operation in isolation. It's more like you want to post process the job as though it only contained the one operation, and the proper tool. You still want the output to be aware of the type of machine selected, the tool controller settings, etc. but you don't want the other operation paths.
I can see two ways to do this.
1) Allow user to select a sub-object. If a subobject is selected, we post-process the job but exclude all the children except the selected one.
2) Always post-process the job like now and expect the user to dis-able any operations not desired. This would be more intuitive if spacebar toggling both hid the operation and toggled the active status.
How should I handle the condition where the user has Ctrl+selected multiple children? Do I need to be aware of the order in which multiple children were selected?
This is a good workflow issue and a good solution will make the system more intuitive and flexible. Feedback wanted but please try to think about the things other users, including newbies, might try and the kinds of mistakes that might be made.