Hi,
I think TyFlow can really benefit from being able to query selected events and operators in maxscript. It would need to be able to identity which tyFlow is active in the GUI as to not accidentally apply maxScript operations to unintended tyFlow Objects that also have selections already.
Here are some of the options this can create for users.
1. Create selected event align scripts - Can average out the selected events by Pos.Y to align horizontally, or X for vertically.
2. Create presets. One preset might be to create fast pre-configured filters for selected operators - so user doesn't have to keep typing in "Greater than 0 for custom float" for example - which is a super often filter I use in tyFlow.
3. Can connect multiple selected operators (send-out) to one event. Can for example, query selected operators and events where if the -1 event is the one you want to connect, iterate through that array of operators and event and connect to the last selected event - can be super useful for multiple connections.
4. Batch renaming of selected operators / events.
5. Can query the position of the selected operators and batch create multiple operators with configurations beneath these operators.
5a. Along with that - To create our own gui for fuzzy searching for tyFlow operators and appends below selected operators.
6. Keyboard shortcut binding to disable / reenable selected events/operators - this one would be particularly useful.
7. Editing multiple similar operator parameters at same time (since modifier in max blanks out when multiple operators are selected)
Along with these improvements, not just querying selections but also being able to select operators from tyFlow through scripted selection sets (which we can make probably with global variables for in the scene in maxScript). We can't have access to selection sets without first being able to query what operators / events were selected through maxscript though, but this could also lead to more options for users. Kindof how currently you can right click on operator and say "Select all (operator name)".
For the preset tool I'm thinking of making if this gets implemented, an additional idea that would be useful is to have a callback in max that is "current event/operator selection changed" that can register in max rollouts. Would be useful instead of having to create a "re-initialize selection query" button for a rollout, it would be a faster user experience to not have to hit that button if there is a callback that is registered back to max.
Just to be clear, yes, you can currently do all these operations by specifying the Object.event.operator but the tedious level of this makes it not worth even writing scripts for since you'd have to specify everything by name which is not really appropriate for scripting. Defeats the purpose.
Among other things I haven't thought of yet, but can find useful.
Thank you.
I think TyFlow can really benefit from being able to query selected events and operators in maxscript. It would need to be able to identity which tyFlow is active in the GUI as to not accidentally apply maxScript operations to unintended tyFlow Objects that also have selections already.
Here are some of the options this can create for users.
1. Create selected event align scripts - Can average out the selected events by Pos.Y to align horizontally, or X for vertically.
2. Create presets. One preset might be to create fast pre-configured filters for selected operators - so user doesn't have to keep typing in "Greater than 0 for custom float" for example - which is a super often filter I use in tyFlow.
3. Can connect multiple selected operators (send-out) to one event. Can for example, query selected operators and events where if the -1 event is the one you want to connect, iterate through that array of operators and event and connect to the last selected event - can be super useful for multiple connections.
4. Batch renaming of selected operators / events.
5. Can query the position of the selected operators and batch create multiple operators with configurations beneath these operators.
5a. Along with that - To create our own gui for fuzzy searching for tyFlow operators and appends below selected operators.
6. Keyboard shortcut binding to disable / reenable selected events/operators - this one would be particularly useful.
7. Editing multiple similar operator parameters at same time (since modifier in max blanks out when multiple operators are selected)
Along with these improvements, not just querying selections but also being able to select operators from tyFlow through scripted selection sets (which we can make probably with global variables for in the scene in maxScript). We can't have access to selection sets without first being able to query what operators / events were selected through maxscript though, but this could also lead to more options for users. Kindof how currently you can right click on operator and say "Select all (operator name)".
For the preset tool I'm thinking of making if this gets implemented, an additional idea that would be useful is to have a callback in max that is "current event/operator selection changed" that can register in max rollouts. Would be useful instead of having to create a "re-initialize selection query" button for a rollout, it would be a faster user experience to not have to hit that button if there is a callback that is registered back to max.
Just to be clear, yes, you can currently do all these operations by specifying the Object.event.operator but the tedious level of this makes it not worth even writing scripts for since you'd have to specify everything by name which is not really appropriate for scripting. Defeats the purpose.
Among other things I haven't thought of yet, but can find useful.
Thank you.