This is a pretty general question but something I am always worrying about. I mess around a lot with GUI ideas and methods of interacting with my patches, most often with multi-touch via TUIO. Most MT apps are full screen so the input resolution is easily scaled to the display though which drives me nuts. Since I am always using some thrown together mixer, matrix, and whatever, I don't full screen.
To deal with this I made a patch to update the window location by hitting a thispatcher object with a metro, the routing the window rect, and location to a zl change, onto the scale update. My question is, am i putting too much work load on the thispatcher object?
The max to multi-touch patching system I use (MMF from Mathieu Chamagne) uses a JS to update where the UI objects are by banging a this.patcher JS which pings where the objects are. When i have tried throwing a metro on the JS so I can move objects freely and have the input update, it will crash max half the time. (And when I set the metro speed to slow it looses the natural feel of real time updates).
it's too bad I can't try and make something in C to handle this..for now though, am I unrealistic to want to be sampling this kind of scene data in real time?