bulia byak wrote:
I'll see what I can do. Do you have any suggestions? Is there any way I should be measuring this, other than with a stopwatch?
If you know how to profile, it would be nice if you could create a node-editing-specific profile (e.g. start the program with a file with a complex path, then do dragging nodes for a pretty long time so that it makes the program loading time small by comparison, and then examine the profile to see what functions take the longest time). If you don't know how to profile, ask here, it's simple (though I don't remember all details :)
I don't know how to profile, but I'd be willing to give it a shot if someone wouldn't mind explaining it to me (and assuming it isn't over my head). I'm on Win2k.
Thanks, Michael