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.
The i18n configuration is continuously lost after some changes to the gui like disabling a tab or another component. The 1st problem appears after closing the visual form. When i reopen the visual form and I inspect the i18n resourcebundle settings on a given component I find all fields empty except the Key. My form is quite complex, but not so much, it includes subforms available from other visual forms. All visual parts are correctly rendered and the software is error-free. I just wanted disable a tab as a default, and the result has been to loose all i18n :( I posted this bug before with Netbeans 5.5 but the technician was not able to reproduce the error. I hope this time will be easier to catch.
Reassigned to component "form".
Thank you for your report. I tried to reproduce your issue, my steps .... - create java project, add JFrame form - enable Automatic Internationalization form property - add JTabbedPane, add JPanel into pane, add JButton into panel ( Now bundle file contains key and value for a new button and initComponent() method contains code jButton1.setText(bundle.getString("NewJFrame.jButton1.text")); // NOI18N ) - disable tabbed pane >> source file still contains correct i18n stuff - disable panel >> source file still contains correct i18n stuff - disable button >> source file still contains correct i18n stuff - save form, close form, reopen form >> source file still contains correct i18n stuff Are my steps correct? Please, can you add simple steps to reproduce your issue? Product Version: NetBeans IDE 6.5 (Build 200811100001) Java: 1.6.0_10; Java HotSpot(TM) Client VM 11.0-b15 System: Windows Vista version 6.0 running on x86; Cp1250; cs_CZ (nb)
Reporter didn't provided required information for more than 14 days, I am closing this as worksforme. Unfortunately, we are not able to reproduce this behavior again :( We definitely need more info about this. As we cannot reproduce that using simple/default forms, and there are no similar issue reports, it seems that there is some specific problem in your concrete form. It would be great if you can possibly attach some simple project, where this problem can be observed. Or describe the steps to reproduce (confront it with jvagner's post). Feel free to reopen the issue then... Thanks