wrapt natsort wat-inspector




Random nodes for ComfyUI I made to solve my struggle with ComfyUI. Have varying quality.
More Docs (can be shown directly in the UI if rgthree is installed).
Piping:
Highway: yet another implementation but overkill version of pipe and reroute.HighwayBatch: batching version of Highway.Junction: over-the-head data packing and unpacking sequentially.JunctionBatch: if Junction and ComfyUI batching have a kid.Merge: pipe and batch merging.Misc:
BoxRange: visualization of boxes. usefull for anything that requires boxes (which is x, y, width, height).ConditioningSetAreaPercentage and anything that have percentage size and have exact x,y,width,height input name are supported. More will come in the future.~~Beautify: the beautification of data for easy troubleshooting.Stringify: anything to string, optionally together.RandomInt: different from other implementation such that it generate number server side to works with Loop.Hub: widget management to the max.CastReroute: basically like Reroute but have ability to specify custom type. Useful when dealing with Highway, Junction and such.Cloud: Prompt/Data/etc management made “easy”.Tag: Data tagging mechanism.Control Flow:
Loop: very hacky recursive repetition by messing with ComfyUI internals.Hold: hold data between each loop execution.Count: simple counter to use with Loop.Switch: allows input/output switching. Will not evaluate unused inputs.“Execute anything” node:
ScriptNodeScriptRuleScriptAdded Tag node to allow better data management. Demo workflow:
Added Cloud and Switch node (still techincally in beta but whatever). Also added 0246.AlternateDOMWidget option.
Demo workflow are below:
Tons more nodes. Here’s the simple workflow image that showcase everything within this update.
For any nodes related to Script, *_order widget will determine script execution order, which depends on natsort. How it being sorted can be customized by doing things like INT, LOCALE within the _sort_mode widget.
Warning: The recent changes I have changed how Highway and Junction tracking types. Therefore the best way to mitigrate this is to just copy the _query or _offset, create a new Highway or Junction, paste the string then reconnect everything over. I’ve probably find a way to automate this.
I recommended you to play around with this sample workflow (edit 2024-01-20: kind of obsolete but should still works with some manual fixes):