I am here to request that all node packs being maintained, and ComfyUI designed nodes, are from now on created with an Optional Use input/Output trigger signal for ease of execution ordering. If you need an example as to why then it should be simply noted that the execution order issue has not been solved by anyone yet. If a node does not have an output connection to run after its functioning to be fed into a “next operation” then it can not be a part of sequential processes. When things run in parallel which are dependent on previous functions it throws an error; obviously. I and Ai searches can not find a simple solution that has yet been created. A lot of work arounds have been noted, but the issue remains that order of operations is a no–brainer thing to have in your graph. I want to save to specific file, and then pull from that file for a next process. But the loader doesn’t have a trigger connection to cause the function “Run”. I think this describes why I would like this feature to be implemented and normalized for ComfUI designers/modders.
Next on the agenda: Normalize a ReadMe file section stating the particular logic for naming conventions in the node pack. I could attempt to edit these needed nodes myself, through research and testing, but “Save Image to Local” is not named as “SaveImageLocal.py”. No idea which of the many alternatively named node code files is the correct one. The only MixLab node named with Save in its file title is Save Mesh 3D. A simple statement of how you choose your specific nomenclature would be very useful for open source projects like ComfyUI Custom Nodes. Not hating, I am accustomed to being ahead of the times. It comes with the “i.Q.”. Its a ‘blessed burden’ as they might say. Now I have made the request, please all others Like, Subscribe, and Share so that it may get done. Normalize Simplified Naming Conventions.
Thank you for your time.