This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 44724 - Insertion caret no longer blinks
Summary: Insertion caret no longer blinks
Status: RESOLVED WORKSFORME
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: issues@editor
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2004-06-10 21:36 UTC by Jesse Glick
Modified: 2007-11-05 13:42 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2004-06-10 21:36:24 UTC
040610. It seems the insertion caret no longer
blinks. It stays solid. I think this is a recent
regression (not sure).

Note that I have Highlight Caret Row enabled.

JDK 1.5.0 b54, GTK.
Comment 1 Jesse Glick 2004-06-10 21:38:28 UTC
Also it seems that matching bracket highlighting got "stuck" and now
highlights just one brace in the current file, regardless of where I
move to.

I just changed some (unrelated) editor settings in Options with the
editor window open. Maybe that triggered that bug.
Comment 2 Jesse Glick 2004-06-10 21:40:40 UTC
Matching bracket highlighting does change if I type e.g.

new HashSet();

but then stays on the '(' after I move away.

Looks like some kind of timer or listener got stopped.
Comment 3 Jesse Glick 2004-06-10 21:47:08 UTC
Hmm, and code completion does not automatically display Javadoc after
a delay. I sense a pattern here.

Log file does not have any stack traces except ConvertToTextAction
during startup which is surely unrelated.
Comment 4 Jesse Glick 2004-06-10 21:48:41 UTC
And after restarting, all is well.
Comment 5 Miloslav Metelka 2004-06-11 12:13:01 UTC
Strange. I went through recent commits but none of them seems to be
related. Mato did a larger commit on 09/06 - removal of
"netbeans.debug.exceptions" but it should not be related. Mato, could
you please re-check the commit. I've already checked it briefly but
did not find anything suspicious.
 Anyway this has to be resolved into promoD.
Comment 6 Martin Roskanin 2004-07-22 15:16:05 UTC
I also didn't find anything suspicious in my commit. Jesse, are you
still able to reproduce it?
Comment 7 Jesse Glick 2004-07-22 18:42:48 UTC
I have not seen anything like it since. Although I have not changed my
editor settings since. Anyway editor code has changed, and I am using
a different OS, JDK, and L&F...