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 installed 0.37 out of curiosity and it is noticeably quicker than 0.39 or the latest builds in these areas, if that helps any.
Yeah. 0.37 was a very different program internally. Much simpler.
That might depend on the number of fonts installed on your system.
I do have several fonts, but 0.39 pops up the Text Dialog in less than a second, while the Oct 22nd build takes about 14 seconds. I figured I'd break out the stopwatch for this one :)
OK, please submit this as a bug too. And if you can profile this too (open it several times in a row in one session) it would be very helpful.
If it's on Windows then it's no fault of ours. That's what Windows GTK uses I guess.
I don't mean to be contrary, since I don't really understand the implications of using GTK, but 0.39 displays menu fonts larger than the sept 24 or Oct 22 builds on my computer. This isn't a big deal (to me), but I do think the 0.39 font size looks better.
Oh then it must be a consequence of the new versions of libraries. Maybe Bob Jamison will have a comment on this.