thank you, this looks unfamiliar. any reason why i never came across this when building winforms with sharpdevelop. just curious why vvvv handles winforms this way.
would be nice to have some control over the window without providing my own window.
well, unfamiliar it may be. but it is the way to go if you need your own window for a vvvv plugin.
it is by design that vvvv provides window-handling for gui-plugins. so by default you get known vvvv-window-behavior. if you want to work around that you have to do as lined out above.
otherwise you can take control over a window by sending patch-messages…