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 3960 - PropertyEditorSupport does not work perfectly.
Summary: PropertyEditorSupport does not work perfectly.
Status: CLOSED WORKSFORME
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P4 normal (vote)
Assignee: Jon Koplin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1999-09-21 22:17 UTC by Jon Koplin
Modified: 2003-07-02 15:42 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Koplin 1999-09-21 22:17:55 UTC
[IAN] Caused by the fact, that getJavaInitializationString is not implemented in PropertyEditorSupport, and thus must be implemented by property editors if code generation is needed. This bug does n
ot have to do anything with netbeans.

Note that this works perfectly in the BDK, so it`s probably a bug in NetBeans

Unpack editor.tar (in Attachments) into a directory.
Try to change the "the property" property of the myBean class in the Component Inspector.
It does not generate code for you properly.  No code gets generated.


However, it does work properly if you:

1.  Click on the "..." next to the property.  It will give you a dialog that says that the MessageEditor does not support custom editing.

2.  Switch to the String Editor tab and type something in there.  You will notice then
that the code will add a line generated
myBean1.setMessage("whatever you put here");

3.  Then, if you want you can change it using the drop-down
box in the Component Inspector.
Comment 1 Marek Grummich 2000-07-25 09:22:59 UTC
Priority is changed to P4 (normal).
Comment 2 Quality Engineering 2003-07-02 15:34:25 UTC
Resolved for 3.4.x or earlier, no new info since then -> verify.
Comment 3 Quality Engineering 2003-07-02 15:42:57 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.