Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#24659 - [scite] considerably slower on key-repeats
Attached to Project:
Community Packages
Opened by David Rheinsberg (dvdhrm) - Thursday, 09 June 2011, 22:51 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 10 October 2011, 15:31 GMT
Opened by David Rheinsberg (dvdhrm) - Thursday, 09 June 2011, 22:51 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 10 October 2011, 15:31 GMT
|
DetailsAfter updating scite to 2.26-1 the editor is considerably slower and often unusable. I run this on Intel Atom and I use scite because it is very lightweight and fast. However, after the update scrolling via up/down buttons is VERY slow and the window doesn't get updated during scrolling but only when I release the buttons. Scrolling with pageUp and pageDown is also VERY slow and the window is repainted slowly.
All in all, the whole editor reacts much slower than before and working with it is nearly impossible. I cannot say whether this problem is with the new scite-update or whether a gtk2 update or similar caused this problem. I just know that this didn't happen with the 2.25 scite. Ah, I just realized that this problem does only occur with key-repeat events. If I repress a pageUp/pageDOwn or up/down very fast the editor reacts smoothly, however, If I hold the keys, the editor reacts very slow. Other GTK apps like xchat don't show this behaviour. regards David versions: gtk2-2.24.4-2 scite-2.26-1 |
This task depends upon
Closed by Jelle van der Waa (jelly)
Monday, 10 October 2011, 15:31 GMT
Reason for closing: Fixed
Additional comments about closing: upstream fixed it in 2.27
Monday, 10 October 2011, 15:31 GMT
Reason for closing: Fixed
Additional comments about closing: upstream fixed it in 2.27
Comment by Jelle van der Waa (jelly) -
Saturday, 11 June 2011, 22:19 GMT
check upstreams bugtracker
Comment by Jelle van der Waa (jelly) -
Monday, 10 October 2011, 10:00 GMT
What about the new version?
Comment by David Rheinsberg (dvdhrm) -
Monday, 10 October 2011, 11:15 GMT
Sorry, I forgot to close this task. I reported the bug upstream and it got fixed in 2.27. See http://sourceforge.net/tracker/?func=detail&aid=3315233&group_id=2439&atid=102439