Michael Dewberry

Hi! Yes, enabling other package authors to leverage hardware and software grids is definitely a long-term goal and we've had [some discussions about it](https://github.com/monome/serialosc/discussions/65). You have correctly identified the issue...

Dynamo appears blurry even if all monitors are set to 125% DPI, so I'm not totally certain it's even handling system DPI awareness correctly.

These modules use OSC, a network protocol, to communicate with the serialosc server to provide device support for local and remote devices. This involves opening a listening port for messages...

I'll leave this issue open because it should be possible in the future to only open this port on the local interface to avoid the firewall dialog. If people want...

This workaround seems to prevent the behavior: ``` ofxFenster* pWin = ofxFensterManager::get()->getActiveWindow(); ofFileDialogResult result = ofSystemLoadDialog("Load Model", false, ""); ofxFenster* pDummy = ofxFensterManager::get()->createFenster(0,0,1,1); ofxFensterManager::get()->setActiveWindow(pDummy); ofxFensterManager::get()->setActiveWindow(pWin); ofxFensterManager::get()->deleteFenster(pDummy); ```

For 2013 we ended up building an OSC-based joystick control scheme based first on junXion, then on our own Max patch Bleepstick (https://github.com/Dewb/BleepStick). This served us well for 2D content...

Just-merged PR DynamoDS/Dynamo#8182 adds a run button to the editor window and allows you to have multiple windows open at once.

Many other very good enhancement ideas in this thread. I hope to have time to address a couple of other frequent requests before 2.0, but I can't promise anything yet.

Still reproducible in 2.4.0.

Dynamo has a global console, and there are some other requests to have Python node `print()` statements go to that console; what are the advantages of having a separate console...