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 103195 - beansbinding init code in separate method
Summary: beansbinding init code in separate method
Status: NEW
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Binding (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-03 08:55 UTC by tprochazka
Modified: 2008-05-05 10:48 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 tprochazka 2007-05-03 08:56:00 UTC
Form editor now adding bindingContext.addBinding() code directly to initComponents() 
method. But I think, that much better would be add this to separate method, for 
example initBinding() and _allow manual editing here_.
Comment 1 tprochazka 2008-03-02 07:56:29 UTC
This is useful especially when I have method setModel() and getModel() in Form. I create instance of form and then call 
setModel(), but form created with Netbeans Call bind() method at the end of initComponents() method. U must call 
bindingGroup.unbind() and bindingGroup.bind() in setModel() method. I know, that I can move initComponents() to setModel
() from constructor. But this cause that form will be blank for long period (hibernate initialization, core 
initialization) I prefer open dialog as soon as possible with empty values with text “Initializing…” in status bar and 
bind all values after initialization.