Here’s my take on this.
I\ve been using that VBScript component for a long time. Quite convenient for me but I still find the way dynamo does things to be more convenient.
Here’s where it gets interesting though.
When I use
Wormhole.gh on Rhino 5, the GH canvass would become transparent but I can still move around the GH canvass without my actions passing through the main rhino window.
The downside of course is that I still have to leave a small portion of the rhino window for orbiting and panning purposes.
Interestingly enough, this is reversed in Rhino6, i.e., when using
Wormhole.gh you can access (i.e. pan, orbit) through the GH canvass.
The obvious downside however is that you can’t use the GH at all since you can’t double-click into the canvass (dragging components is possible of course, but that’s inconvenient).
I think it might be possible to assign a Keymap that toggles this (i.e., mouse actions can pass through canvass), coupled with maybe a blur in the GH background canvass to indicate it is in canvass mode and fully transparent to indicate it is in viewing mode. Is this possible @stevebaer ?
No need to be apprehensive about the idea though, because I’m sure it would be ‘optional’ if it would be implemented.