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 41415 - on selecting readonly propery
Summary: on selecting readonly propery
Status: VERIFIED DUPLICATE of bug 45709
Alias: None
Product: platform
Classification: Unclassified
Component: Explorer (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: _ tboudreau
URL:
Keywords:
Depends on: 29466
Blocks:
  Show dependency tree
 
Reported: 2004-03-26 15:42 UTC by santhosh
Modified: 2008-12-22 17:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
On Selecting Readonly Property (8.22 KB, image/gif)
2004-03-26 15:45 UTC, santhosh 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description santhosh 2004-03-26 15:42:42 UTC 
the text of readonly property is not clearly 
visible when selected.

I am using jdk1.5 with windows LAF. I don't know
whether this happens in other LAFs.

see the attached screenshot.
Comment 1 santhosh 2004-03-26 15:45:27 UTC 
Created attachment 14173 [details]
On Selecting Readonly Property
Comment 2 Lukas Hasik 2004-03-26 15:49:12 UTC 
santhosh, read priority guidelines, please
http://qa.netbeans.org/processes/bug_priority_guidelines.html
this one isn't P1 ! nor P2.

Do you mean development build or 3.6 by current version ?
Comment 3 _ tboudreau 2004-03-26 21:34:04 UTC 
This is an artifact of the way JLabels render disabled text on Windows.  It will be fixed 
when we integrate the HTML mini-renderer, which will take over the painting of disabled 
text.
Comment 4 santhosh 2004-07-02 06:26:51 UTC 
you can fix this very easily in TableCellRenderer implementation:
  // make the renderer disabled only when it is not selected
  setEnabled(isSelected || prop.canWrite());
Comment 5 _ tboudreau 2004-07-22 13:39:04 UTC 
Closing as duplicate of higher priority issue - already committed to fix in 4.0

*** This issue has been marked as a duplicate of 45709 ***
Comment 6 Marian Mirilovic 2005-07-12 10:17:39 UTC 
closed