On Wed, Feb 02, 2005 at 03:34:43PM +0100, Thoralf Schulze wrote:
Hi list,
graph on parent on parent eats cpu for breakfast: I tried to create an abstraction that graps on parent (with about 800x200 px) and doesn't have any gop-objects by itself, but holds a few more abstractions that themselves do have some gop-objects. With about 6 or 7 number2s / toggles / bangs and absolutely nothing else going on in the patches, the cpu usage climbed to a whopping 10-20 per cent, while it was idling at around 4-5 before. (Pentium IV/2.6ghz, win2k, pd 0.37)
I suspect a tcl/tk-issue here - is there any way of getting around this problem? I would really like to
might want to try TaskInfo (www.iarsn.com) just to see if it is wish.exe or pd.exe that is chewing the cpu. then add a "-d 3" flag to pd launch to see if excessive gui traffic is being generated. if it is, your best bet for now may be switching to an 'inspector' based system where you only have one set of toggles/sliders/whatever and change the context of what theyre displaying/affecting....ive had no issues with nested GoPs but theire mainly used for user input so dont generate much traffic..
keep this abstractions-in-abstraction-thingie, since the former are called with arguments, and I would like to know what's going on inside them ...