The script allows you to browse all Fusion (and Resolve) classes it can find, including all properties and methods. It does this by looking at three things:
- Fusion's built-in script documentation,
- The global
- The binary files (yes, it's a simple and probably unreliable hack)
Since classes found in the binaries don't come with a class hierarchy, not all classes will be placed correctly. In case I can't match a discovered class with a documented class I simply place it in the root. I assume there might also be instances where classes that have the same names are actually different classes in BMD:s source code and are meant for different contexts. But Fusion script writers are probably used to the fact that not all methods work in all areas of Fusion anyway.
To make a distinction between documented information and information discovered in the binary files I call the different sections "Properties", "Methods", "Discovered Properties" and "Discovered Methods".
When would I use it?
I think the biggest benefit is when creating Fuse scripts. The Operator, Image, and Request classes have a lot of stuff in them that isn't in the built-in documentation. You can also use it when you want to find out which attributes are applicable to an input control, like the MultiButtonControl. UIManager classes are in there too of course, but they don't have any parameter info so you have look them up on Qt.
Since version 1.2.1 I believe I've reached the end of the road in regards to what information can be "easily" extracted from Fusion. But before I put it in Reactor I thought I would ask for some feedback.
What do we call these? I'm currently calling them Tag Maps (mostly) since that's their name in the global table. But VFXPedia calls them attributes. TagList as I understand it is a specific class representing a Tag Map (collection of attributes).
Keep the "Filter class name" text box?
I'm thinking I should get rid of it. I never use it since you can type the first characters of a class in the TreeView and navigate there instantly. In the Nested View the filtering is incredibly slow when you remove the filter. And there are a few bugs in there as well.
Download Fusion 9 and Fusion/Resolve 16+ supported (Resolve 15 probably works as well). Windows, macOS, Linux.
- Fixed: Startup crash in Resolve/Fusion v17.1 caused by class types that are no longer available
- Fixed: Classes containing only ignored discovered methods (like _cast) caused properties to be skipped
- Fixed: FuPath methods weren't being discovered
- Fixed: The Plugins path was incorrect for Fusion on Windows
- New: Additional properties discovered automatically
- New: Several more files are probed for methods and properties
- Fixed: Some PreviewControl classes weren't showing in the nested view
- New: Tag Maps and Enum Maps
- New: Additional methods that aren't documented in the help system are now discovered automatically
- Fixed: Fusion v9 window layout issue
- Fixed: Fusion v9 didn't show property types when available
- Fixed: Fusion v9 error when registry entries contained tables, added workaround for dumptostring() bug
- Added support for showing registry entries associated with a class