Although writing fuses to make a modifier node seems easy, you'll often run into unexpected behavior, especially if you're not that familiar with writing code like myself. You'd need to take care of all the event handling and make sure that the node isn't modifying their incoming parameters, so I'm hoping to get some help from you guys along the way. This will be the place where I'll continue to post my modifier node experiments.The nodal workflow could do with an overhaul, to try and make it more consistent, dynamic and current (perhaps make it stand out more from the competition):
- Expose arbitrary input and output parameters in the flow node editor (work panel).
Expose modifiers too, and make them nodes, instead of hiding them in a tab in the control panel.
Make the horizontal size of nodes variable to fit longer names.
Make it possible to hide connections on a node in the work panel, to keep things clean if you wanted to (instead of using wireless nodes, especially since we are missing that über-intelligent wireless node that's driven by an input's datatype instead of a hard-coded one).
A selection function that allows filters/regular expressions.
Added in 43 minutes 28 seconds:
My first addition to this toolset is a simple node that will create text and pass it along through its output as such. I dubbed it "Text_Create":
If you want to use in an existing tool that accepts a modifier input, do Connect To and select these puppies from a nice menu. No need to rebuild expressions or whatever if you need it elsewhere.
By specifying the "REGID_DataType" in FuRegisterClass(), you'll end up with a node that's smaller than a regular one, so visually it will stand out too.