> I did have the Inspector open, but it's odd... if I'm in that macro level and > simply open the inspector/parameters, there is actually no performance hit at > all. However, if I move a patch on the Editor, then all hell brakes loose.
Right, because the inspector doesn't need to do anything (no redrawing) until a patch is selected that has an input changing. Once that happens (the sphere's a good example, since there are lots and they all have a different value), the inspector panel will redraw [Iteration] times to update the widgets. If you select a patch that doesn't have inputs that change per-iteration, the inspector won't need to do any redrawing, and things go back to normal. Selecting no patches (same as entering the macro, I believe?) requires no redrawing since there are no inputs to update per-iteration. Moving a patch implies selecting it (because you click it), which will cause the inspector to start showing inputs (per-iteration!) of that patch. That can get expensive rather quickly. If you close the inspector, do the problem go away? if so, that's the cause, and we can hash out whether or not that makes sense etc. But if you close the inspector, and there are still performance issues, I'd be interested to know details of what is required to reproduce it. -- Christopher Wright [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
