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 221317 - Automatically generated internationalization files require explicit saving
Summary: Automatically generated internationalization files require explicit saving
Status: RESOLVED WONTFIX
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P3 normal with 1 vote (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-02 07:58 UTC by ytn01
Modified: 2015-09-09 17:47 UTC (History)
1 user (show)

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 ytn01 2012-11-02 07:58:46 UTC
It looks like automatically generated internationalization "Bundle.properties" files request to be saved when opening & closing them without making any changes.
I believe they should get saved implicitly after being generated.

Steps to Reproduce
Create a new Java project
Add a JFrame to it & Populate the JFrame with some components
Select the root node of the Form file from the Navigator window & check the "Automatic internationalization" property on
	Bundle.properties file will get generated in the project window
Open the Bundle.properties file, then close it without making any changes
IDE will ask to save the file



Product Version = NetBeans IDE Dev (Build 201210310001)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.7.0_09
Runtime = Java HotSpot(TM) 64-Bit Server VM 23.5-b02
Comment 1 Tomas Pavek 2015-09-09 17:47:30 UTC
It would seem that it should be possible to close the file without asking if it was already opened as changed, but I have no idea how to do it. Once opened, the editor check for modification on closing - and it has no idea how or for what purpose the file was created.

The workaround is to keep the file open till the GUI form that uses it is opened. Once the GUI form is saved, it saves the properties file as well. If the GUI form is closed without saving, it will also discard the changes in the properties file. So the GUI form automatically manages the modification state of the automatically associated properties file (but the properties editor itself if opened can't close without also closing the properties file - then the user must choose whether to save or not). I'd wish this could be done somewhat better, but I think it is only a minor obstacle for the user.