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 17587 - Code Generation properties do not fire changes
Summary: Code Generation properties do not fire changes
Status: CLOSED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Pavek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-13 12:12 UTC by Jiri Skrivanek
Modified: 2001-11-19 15:47 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Jiri Skrivanek 2001-11-13 12:12:50 UTC 
Tested in build 20011112-2214.

- open form examples/advanced/MemoryView
- open Properties window for the text JLabel
- open second Properties window for the text JLabel
- switch to Code Generation tab and change some property
- value should be changed in second window but it doesn't
Comment 1 David Strupl 2001-11-13 14:04:26 UTC 
The node has to fire property change in order for the property sheet
to update (if there are two property sheets opened).
Comment 2 Tomas Pavek 2001-11-13 16:16:58 UTC 
Node.firePropertyChange(null, null, null) is not enough?
Comment 3 David Strupl 2001-11-13 16:30:24 UTC 
Should be enough but
1. please don't do it (it should force the property sheet to refresh
completely and it is very probable that it will blink) - please
supply at least the first parameter

2. do you really do it for properties jirka is talking about?if yes -
than it is really strange ...
Comment 4 Tomas Pavek 2001-11-13 16:38:51 UTC 
Yes, currently firePropertyChange(null, null, null) is called for 
these properties. I've tried to change it for "variableName" property
(providing property name and the values) and it works then. So I can 
fix it this way, but...
Comment 5 Tomas Pavek 2001-11-13 16:44:42 UTC 
Well, I have mystified you a bit. No firing method is currently 
called for variableName property. But even if I change it to call 
firePropertyChange(null, null, null), it doesn't work.
Comment 6 Tomas Pavek 2001-11-14 17:04:50 UTC 
I've made the fix mentioned above.
Comment 7 Marian Mirilovic 2001-11-15 14:10:43 UTC 
verified in [nb_dev](20011115)