On 9/5/06, John Bintz <jcoswell@...1414...> wrote:
The most noticeable (and frustrating) delays for me were in node handle manipulations.
I agree - for node editing interruptibility is rarely useful, simply because it redraws the entire path, and most often the segment you're editing is not in the top strip, which means it gets redrawn very unfrequently. Indeed, in this situation forced redraws should help.
a better approach would be to force _some_ of the redraws to be complete and let others be interrupted. For example, after every 5 interrupted redraws insert one forced complete one. I think this will be the best approach overall. What do you think?
I think that would be a good approach. Would you envision this being enabled/disabled on a per-tool/per-event basis or as something more global to be handled exclusively by SPCanvas?
I think we can use an API similar to what you already added:
sp_canvas_force_full_redraw_after_interruptions (canvas, 5)
where the numeric parameter is the number of _consequential_ _interrupted_ (not just interruptible) redraws after which a complete redraw is forced. Can you please code this?
Then, I'd propose that we start using this call in node tool, trying to find the best value of the numeric parameter. If this works out, we may look into adding it in other places too, where needed. However I'm against adding it indiscriminately in each place where we process motion events.