No, as far as the current design is concerned, as pd calculates getrect for every object to see if the new mouse position is on top of something clickable. For this reason, abstracting your mega-patch into subpatches (where possible) is not only a good programming practice for the purpose of legibility and reusability, but also for performance reasons. HTH On Jan 7, 2015 6:19 PM, "Ed Kelly" morph_2016@yahoo.co.uk wrote:
On Wednesday, 7 January 2015, 11:55, Ed Kelly morph_2016@yahoo.co.uk wrote:
What about this...
When I am editing a huge patch like the Ninja Jamm patch, where everything is on the same level (i.e. as few sub-patches as possible) moving the mouse over the patch causes a CPU spike, regardless of whether I change, move or connect anything or not.
Could this be changed? I don't know all the guts of Pd, but if you could just move around the mouse pointer without having to wait for 20 seconds or so before you can do anything, it would save a lot of time.
I think I heard once that any change to the patch means that Pd has to re-draw the entire graph. IMHO surely moving the mouse should not require this? I wait to be corrected!
x Ed
Ninja Jamm - a revolutionary new music remix app from Ninja Tune and Seeper, for iPhone and iPad http://www.ninjajamm.com/
Gemnotes-0.2: Live music notation for Pure Data, now with dynamics! http://sharktracks.co.uk/
Pd-dev mailing list Pd-dev@lists.iem.at http://lists.puredata.info/listinfo/pd-dev
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list