Re: [Inkscape-user] Inkscape-user Digest, Vol 26, Issue 9
i'm also interested on this about using Python as scripting language - specially after what i saw about Scriptographer on Adobe Illustrator, and how can Inkscape do the same with Python
maybe the less worse idea is trying to learn from what were made up to now? i'm as well having difficulties on coding picture filters with Python-Fu (Gimp)
--------------------
On Mon, Jul 28, 2008 at 11:14 PM, inkscape-user-request@lists.sourceforge.net wrote:
Send Inkscape-user mailing list submissions to inkscape-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/inkscape-user or, via email, send a message with subject or body 'help' to inkscape-user-request@lists.sourceforge.net
You can reach the person managing the list at inkscape-user-owner@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific than "Re: Contents of Inkscape-user digest..."
Today's Topics:
- Re: tablet stuff (Alexander Roalter)
- Re: tablet stuff (Aaron Spike)
- Python binding documentation for effects (Daniel Hornung)
- Fix for latency warnings (Jon A. Cruz)
- Re: [Inkscape-devel] Fix for latency warnings (bulia byak)
- Re: [Inkscape-devel] Fix for latency warnings (Jon A. Cruz)
- need help installing software for reading .ps files (Julie)
Message: 1 Date: Wed, 23 Jul 2008 01:09:02 +0200 From: Alexander Roalter <alexander@...2299...> Subject: Re: [Inkscape-user] tablet stuff To: Inkscape User Community inkscape-user@lists.sourceforge.net Message-ID: <4886688E.30003@...2299...> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alexander Roalter wrote: | Since upgrading to OpenSUSE 11, I got the following problem with | inkscape, both 0.46 and SVN: | | If I set the extended input preferences of the Stylus to 'Disabled', I | can use the pen as a mouse, draw etc. and move things around, but I | don't get any pressure sensibility. | | It I set the extended input preferences to 'Screen' or 'Window' | (preferrably to 'Screen'), I get pressure sensibility, but I cannot | select any object by simply clicking on it. I have to tap multiple times | on it in order for it to have the normal handles appear, and only then I | can move the object around. If I tap too often, I get the node | selection, which isn't what I want (at that moment). | | Any Ideas on why? Is this something the X input does differently when | XInput is set to screen so Inkscape does not register a press (or | doesn't register it in the right way?) or is the code in inkscape for | disabled and screen mode that much different so that selecting with | screen mode won't work as expected? | Since nobody seems to care, I took some investigation and found out the following:
If I patch inkscape in order to produce output in sp_select_context_root_handler and sp_select_context_item_handler and put a printf at case GDK_BUTTON_PRESS, GDK_ENTER_NOTIFY, GDK_LEAVE_NOTIFY on select_context_item_handler as well as GDK_BUTTON_PRESS and GDK_BUTTON_RELEASE at select_context_root (the latter two I'll be naming GDK_BUTTON_PRESS/RELEASE____root from now on, I get the following behavior:
if I draw a square with the rectangle tool and switch to select (F1), I can move the mouse over the rectangle and I get GDK_ENTER_NOTIFY If I move the mouse out of the rectangle, I get GDK_LEAVE_NOTIFY
If I press somewhere (outside of the rectanlge), I get GDK_BUTTON_PRESS____root, and when I release, I get GDK_BUTTON_RELEASE____root. This is also valid for the tablet.
If I press somewhere *in* the rectangle, with the mouse I get GDK_LEAVE_NOTIFY GDK_ENTER_NOTIFY GDK_BUTTON_PRESS
and if I release, I get GDK_BUTTON_RELEASE___root GDK_BUTTON_RELEASE___root (that's right, I get it twice), and the rectangle is selected.
If I do the same with the tablet, I get GDK_LEAVE_NOTIFY GDK_BUTTON_PRESS____root
and upon release GDK_BUTTON_RELEASE____root GDK_ENTER_NOTIFY
and nothing is selected at all.
Maybe someone with a bit more insight could help me out here. It might have to do something with GDK and/or its implementation of XInput, but this would not explain the different behavior, I mean pressing outside of the rectangle generates PRESS and RELEASE as expected, but if there's an object under it, why is there a leave notify *not* followed by a enter notify just as it is the case with the mouse?
Cheers, Alex -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkiGaI0ACgkQ1J0MF2u394ympQCeMy1jitHlZQx3uu/IZQgHjoy6 qjEAoLsbeCMBCpWCEbtDFEWQUD4/9G9u =X0LM -----END PGP SIGNATURE-----
Message: 2 Date: Tue, 22 Jul 2008 19:12:42 -0500 From: Aaron Spike <aaron@...476...> Subject: Re: [Inkscape-user] tablet stuff To: Inkscape User Community inkscape-user@lists.sourceforge.net, inkscape-devel inkscape-devel@lists.sourceforge.net Message-ID: <4886777A.7060908@...476...> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
This issue looks like it would be better suited to the devel list and perhaps the bug tracker.
Aaron Spike
Alexander Roalter wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alexander Roalter wrote: | Since upgrading to OpenSUSE 11, I got the following problem with | inkscape, both 0.46 and SVN: | | If I set the extended input preferences of the Stylus to 'Disabled', I | can use the pen as a mouse, draw etc. and move things around, but I | don't get any pressure sensibility. | | It I set the extended input preferences to 'Screen' or 'Window' | (preferrably to 'Screen'), I get pressure sensibility, but I cannot | select any object by simply clicking on it. I have to tap multiple times | on it in order for it to have the normal handles appear, and only then I | can move the object around. If I tap too often, I get the node | selection, which isn't what I want (at that moment). | | Any Ideas on why? Is this something the X input does differently when | XInput is set to screen so Inkscape does not register a press (or | doesn't register it in the right way?) or is the code in inkscape for | disabled and screen mode that much different so that selecting with | screen mode won't work as expected? | Since nobody seems to care, I took some investigation and found out the following:
If I patch inkscape in order to produce output in sp_select_context_root_handler and sp_select_context_item_handler and put a printf at case GDK_BUTTON_PRESS, GDK_ENTER_NOTIFY, GDK_LEAVE_NOTIFY on select_context_item_handler as well as GDK_BUTTON_PRESS and GDK_BUTTON_RELEASE at select_context_root (the latter two I'll be naming GDK_BUTTON_PRESS/RELEASE____root from now on, I get the following behavior:
if I draw a square with the rectangle tool and switch to select (F1), I can move the mouse over the rectangle and I get GDK_ENTER_NOTIFY If I move the mouse out of the rectangle, I get GDK_LEAVE_NOTIFY
If I press somewhere (outside of the rectanlge), I get GDK_BUTTON_PRESS____root, and when I release, I get GDK_BUTTON_RELEASE____root. This is also valid for the tablet.
If I press somewhere *in* the rectangle, with the mouse I get GDK_LEAVE_NOTIFY GDK_ENTER_NOTIFY GDK_BUTTON_PRESS
and if I release, I get GDK_BUTTON_RELEASE___root GDK_BUTTON_RELEASE___root (that's right, I get it twice), and the rectangle is selected.
If I do the same with the tablet, I get GDK_LEAVE_NOTIFY GDK_BUTTON_PRESS____root
and upon release GDK_BUTTON_RELEASE____root GDK_ENTER_NOTIFY
and nothing is selected at all.
Maybe someone with a bit more insight could help me out here. It might have to do something with GDK and/or its implementation of XInput, but this would not explain the different behavior, I mean pressing outside of the rectangle generates PRESS and RELEASE as expected, but if there's an object under it, why is there a leave notify *not* followed by a enter notify just as it is the case with the mouse?
Cheers, Alex -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkiGaI0ACgkQ1J0MF2u394ympQCeMy1jitHlZQx3uu/IZQgHjoy6 qjEAoLsbeCMBCpWCEbtDFEWQUD4/9G9u =X0LM -----END PGP SIGNATURE-----
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
Message: 3 Date: Thu, 24 Jul 2008 13:48:36 +0200 From: "Daniel Hornung" <daniel.hornung@...26...> Subject: [Inkscape-user] Python binding documentation for effects To: inkscape-user@lists.sourceforge.net Message-ID: <20080724114836.193100@...961...> Content-Type: text/plain; charset="iso-8859-1"
Hello, afaics, python is the recommended language for writing one's own extensions and effects. http://wiki.inkscape.org/wiki/index.php/PythonEffectTutorial gives a nice little overview, and http://wiki.inkscape.org/wiki/index.php/PythonModules provides a little bit more information. My question is: Is there a more comprehensive documentation somewhere about the several modules, classes and their methods and attributes? Or at least a brief summary how to iterate over objects, layers, nodes, etc and how to modify them?
Thanks, Daniel
Psssst! Schon das coole Video vom GMX MultiMessenger gesehen? Der Eine f?r Alle: http://www.gmx.net/de/go/messenger03
Message: 4 Date: Sat, 26 Jul 2008 01:17:21 -0700 From: "Jon A. Cruz" <jon@...204...> Subject: [Inkscape-user] Fix for latency warnings To: inkscape-devel <inkscape-devel@...84...> Cc: Inkscape User Community inkscape-user@lists.sourceforge.net Message-ID: <74C3C2BB-D4E7-4CE9-975B-45B6186E6DCE@...204...> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
For those seeing the recent event latency warnings, I've just put in a fix
** (inkscape:27965): WARNING **: Event latency reached 3.290566 sec
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).
We'll probably need to investigate this a bit more, but getting that factor in should let people with false warnings get things calibrated and see only good ones.
If you need it, look for the new setting under the misc pane.
Message: 5 Date: Sat, 26 Jul 2008 12:19:31 -0300 From: "bulia byak" <buliabyak@...155...> Subject: Re: [Inkscape-user] [Inkscape-devel] Fix for latency warnings To: "Jon A. Cruz" <jon@...204...> Cc: inkscape-devel <inkscape-devel@...84...>, Inkscape User Community inkscape-user@lists.sourceforge.net Message-ID: <3c78ff030807260819g553b8edcn18d7e74f5c4f5cbf@...156...> Content-Type: text/plain; charset=ISO-8859-1
On Sat, Jul 26, 2008 at 5:17 AM, Jon A. Cruz <jon@...204...> 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?
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
Message: 6 Date: Sat, 26 Jul 2008 11:16:43 -0700 From: "Jon A. Cruz" <jon@...204...> Subject: Re: [Inkscape-user] [Inkscape-devel] Fix for latency warnings To: Inkscape User Community inkscape-user@lists.sourceforge.net Cc: inkscape-devel <inkscape-devel@...84...> Message-ID: <4B1264D0-DEA3-4096-9633-05FC1488961E@...204...> Content-Type: text/plain; charset="us-ascii"
On Jul 26, 2008, at 8:19 AM, bulia byak wrote:
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?
No. I'm adding that calculation to be included in the warning itself.
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?
What it will do is flag things when events start to pile up, and list to what degree they are getting delayed. It can be *very* useful for things such as checking how different display options, filter settings, etc. affect things.
Mental can list more details of the usefulness, since he's the one who added it to begin with.
about inkscape and python:
http://www.inkscapestuff.org is missing a script field for people uploading there interesting stuff - i sent there a suggestion
http://ospublish.constantvzw.org/ is very focused on academical/professional usage of open-source graphic design tools, some posts at this blog is about Python scripting, and they used to be very open about ideas could be useful for open-source feature enrichenment in this area
----------------------------
On Tue, Jul 29, 2008 at 1:18 AM, Paulo Silva <nitrofurano@...155...> wrote:
i'm also interested on this about using Python as scripting language - specially after what i saw about Scriptographer on Adobe Illustrator, and how can Inkscape do the same with Python
maybe the less worse idea is trying to learn from what were made up to now? i'm as well having difficulties on coding picture filters with Python-Fu (Gimp)
On Mon, Jul 28, 2008 at 11:14 PM, inkscape-user-request@lists.sourceforge.net wrote:
Send Inkscape-user mailing list submissions to inkscape-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/inkscape-user or, via email, send a message with subject or body 'help' to inkscape-user-request@lists.sourceforge.net
You can reach the person managing the list at inkscape-user-owner@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific than "Re: Contents of Inkscape-user digest..."
Today's Topics:
- Re: tablet stuff (Alexander Roalter)
- Re: tablet stuff (Aaron Spike)
- Python binding documentation for effects (Daniel Hornung)
- Fix for latency warnings (Jon A. Cruz)
- Re: [Inkscape-devel] Fix for latency warnings (bulia byak)
- Re: [Inkscape-devel] Fix for latency warnings (Jon A. Cruz)
- need help installing software for reading .ps files (Julie)
Message: 1 Date: Wed, 23 Jul 2008 01:09:02 +0200 From: Alexander Roalter <alexander@...2299...> Subject: Re: [Inkscape-user] tablet stuff To: Inkscape User Community inkscape-user@lists.sourceforge.net Message-ID: <4886688E.30003@...2299...> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alexander Roalter wrote: | Since upgrading to OpenSUSE 11, I got the following problem with | inkscape, both 0.46 and SVN: | | If I set the extended input preferences of the Stylus to 'Disabled', I | can use the pen as a mouse, draw etc. and move things around, but I | don't get any pressure sensibility. | | It I set the extended input preferences to 'Screen' or 'Window' | (preferrably to 'Screen'), I get pressure sensibility, but I cannot | select any object by simply clicking on it. I have to tap multiple times | on it in order for it to have the normal handles appear, and only then I | can move the object around. If I tap too often, I get the node | selection, which isn't what I want (at that moment). | | Any Ideas on why? Is this something the X input does differently when | XInput is set to screen so Inkscape does not register a press (or | doesn't register it in the right way?) or is the code in inkscape for | disabled and screen mode that much different so that selecting with | screen mode won't work as expected? | Since nobody seems to care, I took some investigation and found out the following:
If I patch inkscape in order to produce output in sp_select_context_root_handler and sp_select_context_item_handler and put a printf at case GDK_BUTTON_PRESS, GDK_ENTER_NOTIFY, GDK_LEAVE_NOTIFY on select_context_item_handler as well as GDK_BUTTON_PRESS and GDK_BUTTON_RELEASE at select_context_root (the latter two I'll be naming GDK_BUTTON_PRESS/RELEASE____root from now on, I get the following behavior:
if I draw a square with the rectangle tool and switch to select (F1), I can move the mouse over the rectangle and I get GDK_ENTER_NOTIFY If I move the mouse out of the rectangle, I get GDK_LEAVE_NOTIFY
If I press somewhere (outside of the rectanlge), I get GDK_BUTTON_PRESS____root, and when I release, I get GDK_BUTTON_RELEASE____root. This is also valid for the tablet.
If I press somewhere *in* the rectangle, with the mouse I get GDK_LEAVE_NOTIFY GDK_ENTER_NOTIFY GDK_BUTTON_PRESS
and if I release, I get GDK_BUTTON_RELEASE___root GDK_BUTTON_RELEASE___root (that's right, I get it twice), and the rectangle is selected.
If I do the same with the tablet, I get GDK_LEAVE_NOTIFY GDK_BUTTON_PRESS____root
and upon release GDK_BUTTON_RELEASE____root GDK_ENTER_NOTIFY
and nothing is selected at all.
Maybe someone with a bit more insight could help me out here. It might have to do something with GDK and/or its implementation of XInput, but this would not explain the different behavior, I mean pressing outside of the rectangle generates PRESS and RELEASE as expected, but if there's an object under it, why is there a leave notify *not* followed by a enter notify just as it is the case with the mouse?
Cheers, Alex -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkiGaI0ACgkQ1J0MF2u394ympQCeMy1jitHlZQx3uu/IZQgHjoy6 qjEAoLsbeCMBCpWCEbtDFEWQUD4/9G9u =X0LM -----END PGP SIGNATURE-----
Message: 2 Date: Tue, 22 Jul 2008 19:12:42 -0500 From: Aaron Spike <aaron@...476...> Subject: Re: [Inkscape-user] tablet stuff To: Inkscape User Community inkscape-user@lists.sourceforge.net, inkscape-devel inkscape-devel@lists.sourceforge.net Message-ID: <4886777A.7060908@...476...> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
This issue looks like it would be better suited to the devel list and perhaps the bug tracker.
Aaron Spike
Alexander Roalter wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alexander Roalter wrote: | Since upgrading to OpenSUSE 11, I got the following problem with | inkscape, both 0.46 and SVN: | | If I set the extended input preferences of the Stylus to 'Disabled', I | can use the pen as a mouse, draw etc. and move things around, but I | don't get any pressure sensibility. | | It I set the extended input preferences to 'Screen' or 'Window' | (preferrably to 'Screen'), I get pressure sensibility, but I cannot | select any object by simply clicking on it. I have to tap multiple times | on it in order for it to have the normal handles appear, and only then I | can move the object around. If I tap too often, I get the node | selection, which isn't what I want (at that moment). | | Any Ideas on why? Is this something the X input does differently when | XInput is set to screen so Inkscape does not register a press (or | doesn't register it in the right way?) or is the code in inkscape for | disabled and screen mode that much different so that selecting with | screen mode won't work as expected? | Since nobody seems to care, I took some investigation and found out the following:
If I patch inkscape in order to produce output in sp_select_context_root_handler and sp_select_context_item_handler and put a printf at case GDK_BUTTON_PRESS, GDK_ENTER_NOTIFY, GDK_LEAVE_NOTIFY on select_context_item_handler as well as GDK_BUTTON_PRESS and GDK_BUTTON_RELEASE at select_context_root (the latter two I'll be naming GDK_BUTTON_PRESS/RELEASE____root from now on, I get the following behavior:
if I draw a square with the rectangle tool and switch to select (F1), I can move the mouse over the rectangle and I get GDK_ENTER_NOTIFY If I move the mouse out of the rectangle, I get GDK_LEAVE_NOTIFY
If I press somewhere (outside of the rectanlge), I get GDK_BUTTON_PRESS____root, and when I release, I get GDK_BUTTON_RELEASE____root. This is also valid for the tablet.
If I press somewhere *in* the rectangle, with the mouse I get GDK_LEAVE_NOTIFY GDK_ENTER_NOTIFY GDK_BUTTON_PRESS
and if I release, I get GDK_BUTTON_RELEASE___root GDK_BUTTON_RELEASE___root (that's right, I get it twice), and the rectangle is selected.
If I do the same with the tablet, I get GDK_LEAVE_NOTIFY GDK_BUTTON_PRESS____root
and upon release GDK_BUTTON_RELEASE____root GDK_ENTER_NOTIFY
and nothing is selected at all.
Maybe someone with a bit more insight could help me out here. It might have to do something with GDK and/or its implementation of XInput, but this would not explain the different behavior, I mean pressing outside of the rectangle generates PRESS and RELEASE as expected, but if there's an object under it, why is there a leave notify *not* followed by a enter notify just as it is the case with the mouse?
Cheers, Alex -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkiGaI0ACgkQ1J0MF2u394ympQCeMy1jitHlZQx3uu/IZQgHjoy6 qjEAoLsbeCMBCpWCEbtDFEWQUD4/9G9u =X0LM -----END PGP SIGNATURE-----
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
Message: 3 Date: Thu, 24 Jul 2008 13:48:36 +0200 From: "Daniel Hornung" <daniel.hornung@...26...> Subject: [Inkscape-user] Python binding documentation for effects To: inkscape-user@lists.sourceforge.net Message-ID: <20080724114836.193100@...961...> Content-Type: text/plain; charset="iso-8859-1"
Hello, afaics, python is the recommended language for writing one's own extensions and effects. http://wiki.inkscape.org/wiki/index.php/PythonEffectTutorial gives a nice little overview, and http://wiki.inkscape.org/wiki/index.php/PythonModules provides a little bit more information. My question is: Is there a more comprehensive documentation somewhere about the several modules, classes and their methods and attributes? Or at least a brief summary how to iterate over objects, layers, nodes, etc and how to modify them?
Thanks, Daniel
Psssst! Schon das coole Video vom GMX MultiMessenger gesehen? Der Eine f?r Alle: http://www.gmx.net/de/go/messenger03
Message: 4 Date: Sat, 26 Jul 2008 01:17:21 -0700 From: "Jon A. Cruz" <jon@...204...> Subject: [Inkscape-user] Fix for latency warnings To: inkscape-devel <inkscape-devel@...84...> Cc: Inkscape User Community inkscape-user@lists.sourceforge.net Message-ID: <74C3C2BB-D4E7-4CE9-975B-45B6186E6DCE@...204...> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
For those seeing the recent event latency warnings, I've just put in a fix
** (inkscape:27965): WARNING **: Event latency reached 3.290566 sec
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).
We'll probably need to investigate this a bit more, but getting that factor in should let people with false warnings get things calibrated and see only good ones.
If you need it, look for the new setting under the misc pane.
Message: 5 Date: Sat, 26 Jul 2008 12:19:31 -0300 From: "bulia byak" <buliabyak@...155...> Subject: Re: [Inkscape-user] [Inkscape-devel] Fix for latency warnings To: "Jon A. Cruz" <jon@...204...> Cc: inkscape-devel <inkscape-devel@...84...>, Inkscape User Community inkscape-user@lists.sourceforge.net Message-ID: <3c78ff030807260819g553b8edcn18d7e74f5c4f5cbf@...156...> Content-Type: text/plain; charset=ISO-8859-1
On Sat, Jul 26, 2008 at 5:17 AM, Jon A. Cruz <jon@...204...> 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?
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
Message: 6 Date: Sat, 26 Jul 2008 11:16:43 -0700 From: "Jon A. Cruz" <jon@...204...> Subject: Re: [Inkscape-user] [Inkscape-devel] Fix for latency warnings To: Inkscape User Community inkscape-user@lists.sourceforge.net Cc: inkscape-devel <inkscape-devel@...84...> Message-ID: <4B1264D0-DEA3-4096-9633-05FC1488961E@...204...> Content-Type: text/plain; charset="us-ascii"
On Jul 26, 2008, at 8:19 AM, bulia byak wrote:
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?
No. I'm adding that calculation to be included in the warning itself.
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?
What it will do is flag things when events start to pile up, and list to what degree they are getting delayed. It can be *very* useful for things such as checking how different display options, filter settings, etc. affect things.
Mental can list more details of the usefulness, since he's the one who added it to begin with.
participants (1)
-
Paulo Silva