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 12283 - set property for two components -> generate code only for first
Summary: set property for two components -> generate code only for first
Status: CLOSED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: Josef Kozak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-05-18 17:18 UTC by Marian Mirilovic
Modified: 2003-06-30 18:33 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 Marian Mirilovic 2001-05-18 17:18:51 UTC 
[nb-dev](191),[jdk1.3.1](rc1)

Steps to reproduce:
- if you select more components with the same property
- try to change property by default Editor -> good code is generated
- if you now set property | set as User code

Changed property is generated only for first selected component and in place of
property value (second component) is visible code [RADConnectionDesignValue].
Comment 1 Josef Kozak 2001-08-01 16:50:18 UTC 
::: absolutely reassigned
Comment 2 Josef Kozak 2001-08-01 16:51:49 UTC 
PropertyPanel creates only one instance of FormCustomEditor even if 
there are many selected nodes. So now FormCustomEditor must handle 
(change selected editor for) all selected nodes in 
ComponentInspector. 
There is still one small general issue, FormEditor in some cases sets 
NON-string value into StringEditor, so ClassCastException is shown in 
console. We have to make huge changes in FormEditor later, the 
functionality is OK, it's a question of performance.

::: fixed in dev only
Comment 3 Marian Mirilovic 2001-08-06 09:04:07 UTC 
verified in [nb_dev](20010806)
Comment 4 Marian Mirilovic 2001-08-09 09:03:52 UTC 
because first fixing of this issue cause issue 14254 & issue 14270 i
verify this again:

verified in [nb_dev](20010809)
Comment 5 Quality Engineering 2003-06-30 18:33:31 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.