On Sat, Jul 26, 2008 at 5:17 AM, Jon A. Cruz <jon@...18...> wrote:
The main cause of extraneous warnings is a slight difference between the clock used for the GDK event marking and the real time. On my Mac, I observed that the skew was of a constant factor, so I added in an option to compensate for that. On my system the value was 0.9766 (and thus on my system after running for 85 seconds Inkscape would believe a latency of over 2 seconds had crept in).
Wow, are you saying I have to calculate this coefficient to 1e-4 precision and type it into prefs, just in order to suppress a warning?
I may have missed the explanation (sorry), but I still don't understand what the specific benefit of these warnings is. If they just tell me that Inkscape is running slow, then thank you very much but I can feel that very well without any warnings. Can they be used to pinpoint where exactly the slowness happens in the code? If so how, and how is it better than profiling?