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.
Summary: | Cursor not appearing correctly in edit window | ||
---|---|---|---|
Product: | editor | Reporter: | mclaborn <mclaborn> |
Component: | Painting & Printing | Assignee: | Miloslav Metelka <mmetelka> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | mmirilovic |
Priority: | P2 | ||
Version: | 7.0.1 | ||
Hardware: | Other | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Here is the screen shot demonstrating the problem.
Here is a screen cam showing the problem messages.log |
Description
mclaborn
2011-08-19 17:12:04 UTC
Created attachment 110115 [details]
Here is the screen shot demonstrating the problem.
I could also take a screen cam if that would help.
Created attachment 110119 [details]
Here is a screen cam showing the problem
This is really annoying.
This is a serious problem for me. I am spending a lot of time backtracking to fix typing errors because the cursor does not appear correctly. Could you attach your messages.log to this issue? Thanks. Created attachment 110750 [details]
messages.log
Here is a log taken during a time when the problem manifested. The log was at line 29221 right before I did the typing that demonstrated the problem.
Thanks for the info. I've tested in recent Dev builds using Times New Roman 18 which has an italic version narrower than the plain version. The caret correctly followed end of text when typing. Of course I can't eliminate the fact that for many fonts the italic versions are typically narrower than the plain versions - you would have to change the font in settings to some that has same widths for both italic and plain or avoid to use italic/bold versions. Fixed either by 197534 or an earlier fix. Please test in Dev build from http://bits.netbeans.org/download/trunk/nightly/latest/ and if it would not work for you please reopen the issue. *** This bug has been marked as a duplicate of bug 197534 *** The dev build you mentioned appears to have corrected the problem. Thank you. |