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 70892 - [50cat] Change in parameterlist of c'tor is not seen by Visual Designer
Summary: [50cat] Change in parameterlist of c'tor is not seen by Visual Designer
Status: NEW
Alias: None
Product: javame
Classification: Unclassified
Component: Visual Designer (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Karol Harezlak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-01 19:43 UTC by ieising
Modified: 2008-05-05 09:54 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ieising 2006-01-01 19:43:11 UTC
[ BUILD # : 200512192030 ]
[ JDK VERSION : 1.6 ]

Hi,

Today I changed from one of the c'tors of a MyCanvas class the parameter list. The MyCanvas was previously added as a Custom Component to the pallete and dragged onto the flow-editor.

The new parameter is not picked up by the Visual Designer.
Btw I added the new parameter thru the refactoring tool, and got a warning that it doesn't work for guarded blocks. Since I can't edit the guarded blocks either I had to open good old Notepad and edit it there.

Iwan
Comment 1 Lukas Hasik 2006-01-02 09:07:08 UTC
You should be able to set the constructor parameters in Properties of the
displayable.

There is problem that refactored or changed component isn't updated in palette.
I had to remove and re-add the refactored component from/to palette. Then the
constructor parameters appered in Properties.
Comment 2 David Kaspar 2006-01-02 09:54:34 UTC
Unfortunately I have to say that this is a feature.

Live-update can cause problems in some cases of where the source code of a
component:
1) is broken then the component should temporarily disappear
2) constructor list of parameters is changed and the change is undo-ed then all
property values of contructor parameters should have the same values as before
...
Also the palette of not project sensitive, therefore it makes a problem when a
component has its source code in in 2 projects at the same time.
So technically it is not easy to implement in the current version of Designer.

Settings this issue as an Enhancement. The new Designer version should be able
to support it. But it is not strictly defined whether the update will be fully
automatical or whether there will be an indicator of modified component source code.
Comment 3 Lukas Hasik 2006-06-23 14:42:56 UTC
moving to mobility component
Comment 4 David Kaspar 2007-07-10 16:50:31 UTC
Designer 1 has been removed. Therefore reassigning to Designer 2 module.