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 53626 - Settings dialog shows null instead of values
Summary: Settings dialog shows null instead of values
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Property Editors (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: Martin Krauskopf
URL:
Keywords: REGRESSION
: 54301 55630 56425 56509 56632 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-01-19 08:08 UTC by Milan Kubec
Modified: 2008-12-22 19:40 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
stacktrace of ColorEditor replacement (11.08 KB, text/plain)
2005-03-10 13:50 UTC, Martin Roskanin 		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 Milan Kubec 2005-01-19 08:08:15 UTC 
[dev-200501181900, JDK 1.5.0_02]

1) Open Tools | Options, select Editor Settings,
Java Editor, open Fonts & Colors customizer
2) Set any font to be Default, font is OK in
editor, but first font in the list is shown as
value in the customizer.
3) Set any bgcolor to be Default, color in editor
is OK, but both color values (fg and bg) are set
to null.
After reselecting the node Default all values are
displayed corectly.
Comment 1 Martin Roskanin 2005-02-14 12:42:56 UTC 
*** Issue 54301 has been marked as a duplicate of this issue. ***
Comment 2 Martin Roskanin 2005-03-10 13:48:57 UTC 
This works OK in build 16.01.2005
Starts failling in 17.01.

Problem seems to be in the replacement of inplaceEditor (please see attached
stacktrace). The ColorEditor is replaced during clicking on the red box from the
color palette (tab Swatches in color customizer). After ColorEditor replacement
the new instance is asked for "getAsText". As "color" value was set in the
previous instance, the "color" value is null in the current and it returns
"null" String.

Reassigning to beaninfo...
Comment 3 Martin Roskanin 2005-03-10 13:50:11 UTC 
Created attachment 20746 [details]
stacktrace of ColorEditor replacement
Comment 4 Milan Kubec 2005-03-14 09:31:36 UTC 
This is very annoying behavior, increasing prio to P2.
Comment 5 Martin Roskanin 2005-03-15 10:01:12 UTC 
*** Issue 56425 has been marked as a duplicate of this issue. ***
Comment 6 Jiri Rechtacek 2005-03-15 10:34:10 UTC 
Looks as regression of bugfix issue 52179. Assigned to author this change.
Martin, please review this fix and consider if causes this problem. Thanks
Comment 7 Martin Krauskopf 2005-03-15 11:07:09 UTC 
You are right. Started...
Comment 8 Martin Krauskopf 2005-03-16 08:18:44 UTC 
Since there are situations where it is inappropriate to update property editors
when they are being customized by custom editor component (see issue 52179) I
can't remove the whole code commited with issue 52179. I can just compare few
dumped stack traces and conditionally update property editor. It works for all
*known* cases now. So fixed. We can tune it more when something goes wrong (hope
not). If someone understand the property code vs. property editors better feel
free to enhance it  ;)

Checking in openide/src/org/openide/explorer/propertysheet/PropUtils.java;
new revision: 1.49; previous revision: 1.48
Checking in
openide/src/org/openide/explorer/propertysheet/ReusablePropertyModel.java;
new revision: 1.5; previous revision: 1.4
Comment 9 Martin Roskanin 2005-03-17 09:09:38 UTC 
*** Issue 55630 has been marked as a duplicate of this issue. ***
Comment 10 Martin Roskanin 2005-03-21 15:31:06 UTC 
*** Issue 56632 has been marked as a duplicate of this issue. ***
Comment 11 Martin Roskanin 2005-03-22 08:58:28 UTC 
*** Issue 56509 has been marked as a duplicate of this issue. ***
Comment 12 Milan Kubec 2005-03-23 08:43:12 UTC 
Verified in dev-200503221900.