Hi, I started playing around with inkscape 1.4RC to see what exciting things are being introduced.
When I am using the selector tool to move entire (very simple) paths, the screen update becomes unusually choppy and sluggish. It becomes very very fluid when I turn off the statusbar. I have a hunch that the text with the coordinates that is constantly updating when moving objects is the problem. When I hide the statusbar everything becomes silky smooth. Also if I set the threads to more than 1 (in the preferences) I seem to be having a performance hit in the screen refresh aspect of the program. All these however are NOT happening when I am moving just NODES around. It is only happening when I move entire paths. Anyone else noticing this? If so, can you try turning off the statusbar and see it you get a significant performance boost? The statusbar contains a lot of useful things. It would be nice to be able to turn off only the part that is causing the slow choppy screen refresh. Or finding out in the code what needs a little optimizing. Thank you.
Thank you for your reply. I tried creating an account. I stopped when it asked me for a phone number. I don't want to give that out. It would be great if someone who already has a GitLab Bug Reporting Account posted this as a bug on my behalf.
I don't want to waste anybody's time with my gitlab new user verification issue. I just wanted to bring this inkscape bug to other users attention. If other inkscape users are experiencing the same issue, and if the solution that I am presenting works for them too, then a bug has been identified and the possible culprit as well. It would be nice for the developers to become aware of it too.
Again I don't want to waste anyone's time with gitlab but if you take a look at this discussion on reddit: https://www.reddit.com/r/gitlab/comments/182orq6/cannot_create_new_account_without_phone_number/ it pretty much confirms what I was saying about phone number and credit card for verification of NEW gitlab users.
I only want to report the above mentioned inkscape bug. But I do not want to provide a cell phone number or a credit card in order to just report the bug. That's all.
If I have time today I'll try another test account to see if selecting "create new project" directs the registrant to the paid account. And, if some other kind soul has a couple minutes to try either way and add a comment to the linked topic, we might get more clarity on the matter. The project benefits greatly by users reporting bugs.
You mentioned: "The Inkscape Preferences>Interface main page has checkboxes to disable items in the status bar.If a disabling particular item is effective in improving performance, please let us know and I'll mention it on the bug tracker.Thank you." ● I have actually read the discussion under that post that you kindly directed me to. I have tried again disabling all the various options in that area. None of them improve the performance. I am only seeing a significant boost in performance when disabling the statusbar altogether. Perhaps it's not something within the statusbar, and it is the way the entire statusbar is drawn. I wouldn't be able to know. However the busiest part of the statusbaris the middle of the statusbar, to the right of the lock icon. Where it reads "move by", where you see some numbers constantly refreshing when you move entire paths. I attached a screengrab in my original post with the area noted with a green box, and an arrow pointing it out. I have created a keyboard shortcut, <RETURN>, to quickly toggle visibility of the statusbar, and the performance change is instantly very clear when it is hidden. Thank you again.
Thank you for the link. I read through it and it reminded me of the existence of the "enable developer mode" which I had forgotten.
I played around with the settings and for a few minutes I notices a significant reduction of the sluggishness (i.e. an improvement). I thought that maxing out the render tile size fixed everything, until I saved the scene and reopened it. Without changing anything, the same settings now produce the same sluggishness, and perhaps even worse. It is my impression that the "developer mode" is not particularly reliable for an end user and for production. They are probably useful for developer feedback.
Turning off "Use block update" as well as the "Show Redraw" helped me understand a little better what the various "developer mode" parameters do. I think I was actually able to tweak the settings to something fairly decent. The best performance however, remains when the statusbar is hidden.
See below a screengrab of the settings that I came up with. Perhaps they will be useful to others as well.
I had the luxury of time to check if there is a new version of INKSCAPE and found inkscape-1.4-beta_2024-04-22_62f545ba5e-x64 and gave it a try.
The slowdown due to status bar refresh (the way I understood it) seems to be completely fixed. That is really great. Performance is super from the little tests that I did.
The only area where I am still seeing a prohibitive performance hit is when using the gradient tool as I had described in a previous posting here:
This was the case with an earlier Release Candidate and it seems to remain an issue with the current beta on my particular old system.
However as I mentioned before the Gradients performance did not suffer at all in version 1.2.2. Hopefully that is something that the developers can examine and optimize in the future.
Beginners' Questions Inkscape 1.4 sluggish when STATUSBAR is visible
Inkscape.org
Hi, I started playing around with inkscape 1.4RC to see what exciting things are being introduced.
When I am using the selector tool to move entire (very simple) paths, the screen update becomes unusually choppy and sluggish. It becomes very very fluid when I turn off the statusbar. I have a hunch that the text with the coordinates that is constantly updating when moving objects is the problem. When I hide the statusbar everything becomes silky smooth.
Also if I set the threads to more than 1 (in the preferences) I seem to be having a performance hit in the screen refresh aspect of the program.
All these however are NOT happening when I am moving just NODES around. It is only happening when I move entire paths. Anyone else noticing this? If so, can you try turning off the statusbar and see it you get a significant performance boost? The statusbar contains a lot of useful things. It would be nice to be able to turn off only the part that is causing the slow choppy screen refresh. Or finding out in the code what needs a little optimizing. Thank you.
By all means, pleas report bugs on GitLab. With your help, the developers can resolve these issues, hopefully before release.
https://inkscape.org/forums/beyond/how-to-report-bugs-or-request-new-features/
Thank you for your reply.
I tried creating an account. I stopped when it asked me for a phone number. I don't want to give that out. It would be great if someone who already has a GitLab Bug Reporting Account posted this as a bug on my behalf.
Hi Copy Pasta,
You can send an email to the project to create an issue; check out the "Email a new issue to this project" button at the bottom of the issues section.
-- ltlnx
I'm not seeing any request for phone number. https://gitlab.com/users/sign_up
I don't want to waste anybody's time with my gitlab new user verification issue. I just wanted to bring this inkscape bug to other users attention. If other inkscape users are experiencing the same issue, and if the solution that I am presenting works for them too, then a bug has been identified and the possible culprit as well. It would be nice for the developers to become aware of it too.
Again I don't want to waste anyone's time with gitlab but if you take a look at this discussion on reddit:
https://www.reddit.com/r/gitlab/comments/182orq6/cannot_create_new_account_without_phone_number/
it pretty much confirms what I was saying about phone number and credit card for verification of NEW gitlab users.
I only want to report the above mentioned inkscape bug. But I do not want to provide a cell phone number or a credit card in order to just report the bug. That's all.
Thank you everybody.
I will investigate the bug.
I signed up for a test account on GitLab yesterday and did not hit any requests for cc or phone #. The screens I encountered are shown in the topic:
https://inkscape.org/forums/tutorials/signing-up-for-a-gitlab-account-to-report-bugs/
If I have time today I'll try another test account to see if selecting "create new project" directs the registrant to the paid account. And, if some other kind soul has a couple minutes to try either way and add a comment to the linked topic, we might get more clarity on the matter. The project benefits greatly by users reporting bugs.
Thank you.
I'm going to assume Windows, If the issue is MacOS or Linux, please indicate.
May be this: https://gitlab.com/inkscape/inbox/-/issues/7342
The Inkscape Preferences>Interface main page has checkboxes to disable items in the status bar.
If a disabling particular item is effective in improving performance, please let us know and I'll mention it on the bug tracker.
Thank you.
Hello Tyler,
● Yes. I am running inkscape 1.4RC on Windows
You mentioned:
"The Inkscape Preferences>Interface main page has checkboxes to disable items in the status bar.If a disabling particular item is effective in improving performance, please let us know and I'll mention it on the bug tracker.Thank you."
● I have actually read the discussion under that post that you kindly directed me to. I have tried again disabling all the various options in that area. None of them improve the performance. I am only seeing a significant boost in performance when disabling the statusbar altogether. Perhaps it's not something within the statusbar, and it is the way the entire statusbar is drawn. I wouldn't be able to know. However the busiest part of the statusbar is the middle of the statusbar, to the right of the lock icon. Where it reads "move by", where you see some numbers constantly refreshing when you move entire paths. I attached a screengrab in my original post with the area noted with a green box, and an arrow pointing it out.
I have created a keyboard shortcut, <RETURN>, to quickly toggle visibility of the statusbar, and the performance change is instantly very clear when it is hidden.
Thank you again.
Please open 'Help > About' and click on the little bug icon in the bottom right corner that copies the debug information to your clipboard.
Then paste the info here.
Thanks.
Hello Tyler,
Inkscape 1.4-dev (07fdc56, 2024-03-10, custom)
Compile (Run)
GLib version: 2.78.1
GTK version: 3.24.39 (3.24.39)
glibmm version: 2.66.6
gtkmm version: 3.24.8
libxml2 version: 2.11.5
libxslt version: 1.1.38
Cairo version: 1.18.0 (1.18.0)
Pango version: 1.50.14 (1.50.14)
HarfBuzz version: 8.2.2 (8.2.2)
OS version: Windows 7 SP17Vista SP2Vista SP1VistaXP SP3XP SP2XP SP1XP
Thank you.
Is this Windows machine 32 bit, or is a 64 bit processor?
64 bit / Intel® Core™ i7-2630QM Processor (Laptop)
12 Gigs Ram
May be this bug as well... it does have a comment on hiding the statusbar as a workaround.
https://gitlab.com/inkscape/inbox/-/issues/6979#note_961838585
Thank you for the link. I read through it and it reminded me of the existence of the "enable developer mode" which I had forgotten.
I played around with the settings and for a few minutes I notices a significant reduction of the sluggishness (i.e. an improvement). I thought that maxing out the render tile size fixed everything, until I saved the scene and reopened it. Without changing anything, the same settings now produce the same sluggishness, and perhaps even worse. It is my impression that the "developer mode" is not particularly reliable for an end user and for production. They are probably useful for developer feedback.
Turning off "Use block update" as well as the "Show Redraw" helped me understand a little better what the various "developer mode" parameters do. I think I was actually able to tweak the settings to something fairly decent. The best performance however, remains when the statusbar is hidden.
See below a screengrab of the settings that I came up with. Perhaps they will be useful to others as well.
I had the luxury of time to check if there is a new version of INKSCAPE and found inkscape-1.4-beta_2024-04-22_62f545ba5e-x64 and gave it a try.
The slowdown due to status bar refresh (the way I understood it) seems to be completely fixed. That is really great. Performance is super from the little tests that I did.
The only area where I am still seeing a prohibitive performance hit is when using the gradient tool as I had described in a previous posting here:
https://inkscape.org/forums/beyond/14rc-terribly-slow-gradient-refresh/
This was the case with an earlier Release Candidate and it seems to remain an issue with the current beta on my particular old system.
However as I mentioned before the Gradients performance did not suffer at all in version 1.2.2. Hopefully that is something that the developers can examine and optimize in the future.
Thank you.