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 204856 - Inteferences in painting between Syntax Coloring and Mark Occurence
Summary: Inteferences in painting between Syntax Coloring and Mark Occurence
Status: RESOLVED DUPLICATE of bug 203827
Alias: None
Product: platform
Classification: Unclassified
Component: Text (show other bugs)
Version: 7.0.1
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Miloslav Metelka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-08 18:36 UTC by ngx472
Modified: 2012-06-06 13:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Image of bad drawing 1 see how KW are not highlighted on 2 first lines (56.21 KB, image/jpeg)
2011-11-08 18:36 UTC, ngx472
Details
Image of bad drawing 2 here 'from' KW is painted white on white! (57.99 KB, image/jpeg)
2011-11-08 18:36 UTC, ngx472
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ngx472 2011-11-08 18:36:06 UTC
Created attachment 113014 [details]
Image of bad drawing 1
see how KW are not highlighted on 2 first lines

I created a Mark Occurence Highlighter as per the tutorial
It worked pretty well up until version 7
Now the painting of the first elements is garbled
When I reverse the sequence of regions to highlight, it is the last tokens in the file to suffer
I spent 2 whole days on trying many tricks! none would do. 
It is a timing problem. 
Calling bag.addHighlight in invokeLater does not change anything.

The only stupid trick I found is to add a sleep(1ms), which I have difficulty to admit as a fix!

See images of garbled output

Thanks if you have any hint
Comment 1 ngx472 2011-11-08 18:36:38 UTC
Created attachment 113015 [details]
Image of bad drawing 2
here 'from' KW is painted white on white!
Comment 2 Miloslav Metelka 2012-06-06 13:10:25 UTC
This should be resolved by issue #203827. If the problem would persist please reopen the issue. Thanks.

*** This bug has been marked as a duplicate of bug 203827 ***