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 129096

Summary: "Right margin" line does not repaint correctly
Product: editor Reporter: Petr Dvorak <joshis>
Component: Painting & PrintingAssignee: issues@editor <issues>
Status: VERIFIED DUPLICATE    
Severity: blocker    
Priority: P3    
Version: 6.x   
Hardware: PC   
OS: Solaris   
Issue Type: DEFECT Exception Reporter:
Attachments: The "Right margin" line does not repaint as it should

Description Petr Dvorak 2008-03-04 09:58:54 UTC
Product Version: NetBeans IDE Dev (Build 200803021202)
Java: 1.5.0_13; Java HotSpot(TM) Client VM 1.5.0_13-b05
System: SunOS version 5.10 running on x86; UTF-8; cs_CZ (nb)

The editor does not repaint the "right margin" line properly. Go to Tools > Options > Editor tab > Indentation sub-tab,
change the value of the Right margin property and confirm the dialog.

Be careful!! The editor DOES repaint the line correctly everywhere where the "Options" window was before it was
confirmed, so try to move the Options window out of the area of attention before you confirm it (or you can use the
Options window to draw nice pictures, like the one bellow).
Comment 1 Petr Dvorak 2008-03-04 10:02:37 UTC
Created attachment 57713 [details]
The "Right margin" line does not repaint as it should
Comment 2 Vitezslav Stejskal 2008-03-04 10:29:57 UTC
Reproducible in a dev build. It could be caused by problems with firing settings changes.
Comment 3 Jiri Prox 2008-04-11 00:46:04 UTC
moving opened issues from TM <= 6.1 to TM=Dev
Comment 4 Karthikeyan Rajeswaran 2008-05-27 02:45:56 UTC

*** This issue has been marked as a duplicate of 132695 ***
Comment 5 Petr Dvorak 2008-05-27 09:56:52 UTC
I don't think this is duplicate of issue 132695 as that one says it works for java editor (this one is reproducible in
java editor). But the essence of the problem might be the same.
Comment 6 Petr Dvorak 2008-09-23 12:47:43 UTC
Verified - this issue is fixed in today's build...