Moved away from single .py file addon, refactored everything into an acceptable structure.
I'm not sure if it's conventional to split things up like this, but it fractionalises things in a way I like, so screw it
main init now accesses (sub)modules from 'menus', 'operators', 'panels'.
each module has it's own init. this is a little rough, but it means that we can split the topmenu and panelclasses since we need both for the purely cosmetic f3 search behaviour (raw operator obsfucation, instead it searches in topmenu and it will return a much more aesthetic 'VV Tools > Category > Operator'
Jokes aside this is actually very useful for usability, since you can just search 'vv (x)' to find what you want
I have done minor debug on everything - i'm fairly certain it's all working, but there is a chance something is broken ofc.
Moved away from single .py file addon, refactored everything into an acceptable structure.
I'm not sure if it's conventional to split things up like this, but it fractionalises things in a way I like, so screw it
main init now accesses (sub)modules from 'menus', 'operators', 'panels'.
each module has it's own init. this is a little rough, but it means that we can split the topmenu and panelclasses since we need both for the purely cosmetic f3 search behaviour (raw operator obsfucation, instead it searches in topmenu and it will return a much more aesthetic 'VV Tools > Category > Operator'
Jokes aside this is actually very useful for usability, since you can just search 'vv (x)' to find what you want
I have done minor debug on everything - i'm fairly certain it's all working, but there is a chance something is broken ofc.