Midgardsormr wrote: ↑Sat Oct 24, 2020 11:34 am
For the first, I don't think so. You wouldn't be able to create the macro itself if you couldn't reference the fuse through AddTool. What's the use case?
Hi Bryan, I know this doesn't sound like something very useful, but I'll try to explain what I have in mind.
I'm working on a set of about 15 fuses, they aren't very useful individually, but are designed to work together in a macro.
I just wouldn't want to clutter up the search-bar with all of those fuses.
I also thought that it would be an issue to reference the tools in a macro if they're "Invisible", but using the tag that @Tolosa Films
suggested seems to work fine. The fuses don't come up in a search, but work fine in the macro.
About the TilePic, It turns out that TilePics work differently than I thought.
Apparently, the TilePic that is embedded in the fuse is only displayed when there in no image coming into the fuse.
When there is an image, it just shows the image output of the fuse instead of the embedded TilePic.
Is there any way to make the embedded FusePic the one that is always displayed?
Also, are there any existing scripts that address TilePics?
Tolosa Films wrote: ↑Sat Oct 24, 2020 12:10 pm
For the first, have you tried adding 'REG_Hide, true,' to the FuRegisterClass tag list ?
I did that in a C++ plugin and it worked, but I do not know for a fuse.
Thank you @Tolosa Films
, this is exactly what I'm looking for.
REG_Hide = true
in the fuse, and it works perfectly.
Thank you so much guys!!
I really appreciate your help!!