0
Completed

Whitelisting Monobehaviours

cosmonaut 3 years ago updated by Lazlo Bonin (Lead Developer) 1 year ago 2

In NodeCanvas/FlowCanvas, the system handles project-defined MonoBehaviours by having the user choose to add them to the visual scripting system. This dramatically cuts down on rescan and search time because it doesn't add all units to the system by default.

It's a little extra work for the user to add Monobehaviours, but in larger projects the unit options rescan and search can get really heavy with things that we will never need to access through visual scripting. 

This feature would also let project managers neatly compartmentalize by strongly defining what types of objects should even be accessible through visual scripting. 

Bolt Version:
Unity Version:
Platform(s):
Scripting Backend:
.NET Version (API Compatibility Level):
Planned

Hi Cosmonaut!

Interesting suggestion. Unity object types in general are more numerous than MonoBehaviours (they include every component and asset type). A checkbox could be added to Automatically Include All Unity Objects and there could also be a similar one for enums (which are all included by default).

However, I believe this suggestion is more interesting: https://support.ludiq.io/forums/5-bolt/topics/686-partial-quick-unit-database-update/

Basically, it would scan the files (scripts and DLLs) in your project to only update the ones that have been changed or deleted since the last generation. That would mean a long first generation, but then very fast incremental updates. 

Either way, this is one of the priorities for the 1.2 cycle and I'll definitely implement one or more of these solutions soon.

Completed

Closing old issues! 

Partial unit database update was implemented in 1.3.