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 51204 - Set property on form editor properties always set null at design time.
Summary: Set property on form editor properties always set null at design time.
Status: CLOSED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker with 1 vote (vote)
Assignee: Jan Stola
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-05 15:19 UTC by jpfreire
Modified: 2006-03-24 10:11 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 jpfreire 2004-11-05 15:19:09 UTC
I have created a bean with one property that 
popup a JOptionPane when some property is set, 
showing it's value: it's allways null at design
time.

When I invoke property dialog ("...") and define
some object to be set to my property it calls my
method passing null as parameter.

How can I customize my object if the customizer
depends on the object being passed? 
I don't want to make my beans visual,
and I need the object so I can introspect it and
find out its properties to populate my
customizer with it's properties.
Comment 1 Tomas Pavek 2004-11-09 08:49:28 UTC
Thie problem here is that the "Form Connection" property editor just
provides code, but does not resolve the property values (e.g. another
bean instance). This should be fixed - agree.

However, I don't understand the last paragraph - what customizer do
you mean?
Comment 2 jpfreire 2004-11-09 10:12:12 UTC
my last paragraph is confusing, sorry for that.

It's a customizer I have created that depends 
on a property of the bean (an instance).
So without an instance been created it cannot do it's job. 
But if the other bean extends java.awt.Component it gets instantiated,
and my customizer can do it's job. But extending a component is not
an option.

Thank's.
Comment 3 Tomas Pavek 2004-11-09 14:30:34 UTC
Ok, so we could fix this for 4.1, but it's too late for 4.0 - we could
just make a patch for you.
Comment 4 jpfreire 2004-11-09 16:12:53 UTC
Thank you very much,

i'll be checking for the updates
on CVS.
Comment 5 Jan Stola 2005-01-06 14:26:08 UTC
Fixed.
Comment 6 Marek Grummich 2005-07-11 16:30:34 UTC
verified