Sithu1988 / smart-highlighting-gedit

Automatically exported from code.google.com/p/smart-highlighting-gedit
0 stars 0 forks source link

Cursor sprite lags behind actual input location #9

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Extract the plugin to /usr/lib/gedit/plugins
2. Run the install script
3. Activate the plugin in Gedit

What is the expected output? What do you see instead?
Almost immediately after activating the plugin, the cursor graphic begins to 
lag behind the actual input location when using the arrow keys to navigate 
through a document.

After a short (~1 second) delay, the position of the graphic updates to the 
true cursor location.

What version of the product are you using? On what operating system?
smart-highlighting plugin v3.0.0beta2
Gedit 3.0.6
Gnome 3.0.2
Arch Linux

Please provide any additional information below.

Original issue reported on code.google.com by m...@bocoup.com on 20 Sep 2011 at 4:37

GoogleCodeExporter commented 8 years ago
I also use gedit3.0.6 with archlinux, but I can not find any problem as you 
post.

You can try to :
1. Disable all other plugins and run gedit on terminal.
2. If the problem remains, post the messages shown on the terminal.
3. If the problem disappears, enable the plugins one by one and find which one 
make the conflict.

Plese let me know the result or i can't help you to fix this.

Original comment by swatch.c...@gmail.com on 21 Sep 2011 at 1:21

GoogleCodeExporter commented 8 years ago
Thanks for the quick response. After disabling all plugins and running from the 
command line, I experience the same behavior. No messages are printed to the 
command line.

The behavior does not begin immediately upon opening the file. After moving 
around the document with the arrow keys, it eventually begins "lagging" behind. 
I am having trouble isolating the precise action that triggers the bug, but I 
can reliably reproduce it within the first 10 seconds of randomly moving around.

Once started, the behavior persists across tabs (both previously- and 
newly-opened) until gedit is re-started.

Original comment by m...@bocoup.com on 22 Sep 2011 at 3:54

GoogleCodeExporter commented 8 years ago
I believe it to be tied to gedit's built-in "Display line numbers" feature. 
When the feature is inactive, I cannot re-produce the bug. Once I activate it, 
I can reproduce the bug (again, by randomly moving around the file with the 
arrow keys). Once the cursor is lagging, turning off "Display line numbers" 
corrects the problem.

Original comment by m...@bocoup.com on 22 Sep 2011 at 3:57

GoogleCodeExporter commented 8 years ago
Thanks for your information, but I still can't re-produce this. 

Original comment by swatch.c...@gmail.com on 23 Sep 2011 at 1:39

GoogleCodeExporter commented 8 years ago
I have this issue also, and it does seem to be related somehow to the the 
"display line numbers" feature; when I disable line numbers, the cursor 
position seems to be updated properly.

My experience is slightly different from how the reporter described it; the 
cursor position never updates after ~1 second for me. In order to get it to 
update, I have to move the cursor somewhere else, or scroll the window content 
to trigger a repaint.

This is not a very reliably-reproduced problem, though. I'm still trying to 
determine what exactly triggers the issue for me.

Original comment by killa...@gmail.com on 25 Oct 2011 at 4:49

GoogleCodeExporter commented 8 years ago
Hi,
I agree. This problem seems to occur when the line numbers are enabled.

Original comment by kumar.aa...@gmail.com on 19 Jan 2012 at 8:19

GoogleCodeExporter commented 8 years ago
I can't do anything because I don't see the problem.
Any thing I miss?

Original comment by swatch.c...@gmail.com on 20 Jan 2012 at 5:06

GoogleCodeExporter commented 8 years ago
I can still reproduce it. I think it may be a bug in gtk3-sourceview, really.

Original comment by killa...@gmail.com on 20 Jan 2012 at 5:27

GoogleCodeExporter commented 8 years ago
Since no more information and I can't reproduce the issue, I will close this 
issue.

Original comment by swatch.c...@gmail.com on 29 Jan 2013 at 1:13