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.
090127, JDK 6u11. In recent builds I have noticed that whenever a *.properties file is saved (or modified on disk and reloaded), the caret jumps to the end of the buffer. Minor but a frequent irritation.
*** Issue 158322 has been marked as a duplicate of this issue. ***
*** Issue 158695 has been marked as a duplicate of this issue. ***
Same behaviour for 6.5 withh all patches applied. Regards
This is still in NB 6.7M2...
*** Issue 159474 has been marked as a duplicate of this issue. ***
*** Issue 160189 has been marked as a duplicate of this issue. ***
I found where problem is: PropertiesEditorSupport adds 2 file change listeners EnvironmentListener to property file. Result is that code in CloneableEditorSupport is confused and sets incorrect caret position after reload. I fixed this problem in CloneableEditorSupport but still due to 2 events document is reloaded 2 times. So please create and add only one file change listener. Probably caused by copying code from DataEditorSupport. One registration is at Environment constructor and second one at Environment.changeFile. First one can probably be removed but make sure there is then always at least one file change listener. For CloneableEditorSupport I filed issue #160252.
I fixed issue #160252 so cursor will stay now at correct place when file is saved. Still there are 2 file change listeners in PropertiesEditorSupport so please fix it.
I thought part of the point of fixing the weird loaders usage in the properties module was to simplify the code so that bugs like this would vanish. Yet I see that there is still a special FileEntry subclass, a special editor support rather than the standard DataEditorSupport, etc. It is likely that all of this junk can simply be deleted. Then the *.properties data object would just be a pretty generic data object with only two features of note: 1. A DataNode with children showing keys, refreshing with live document edits, maybe permitting edits from the nodes themselves. Not trivial, but straightforward. 2. An OpenCookie which shows a grid that can load related *.properties from the same folder (or more generally from the ClassPath.EXECUTE, in case localizations are kept in separate source trees or even separate projects). Pure GUI, no special support needed from the loaders layer.
Agree, but it was also certain request for certain feature. And I was thinking about how to make it, but probably at some point forgot about simplifying the code. So anyway it is a subject of separate issue. This issue is fixed by changeset 78b556301c25
*** Issue 161689 has been marked as a duplicate of this issue. ***
Please consider include it in the next 6.5 patch. Really annoying issue. Regards
The status whiteboard "65fixes4-candidate" has been removed. At this time our proactive patches for the NetBeans 6.5.x IDE have concluded. If you own a Sun service plan contract for NetBeans, you may wish to contact Sun Service http://www.sun.com/contact/support.jsp to request a fix via the product defect escalation process. For more information on purchasing a Sun service plan contract for NetBeans, refer to the service plan item "Sun Software Service Plans (S3P) for Developers" in the Sun Service table found on our NetBeans Support Resources page http://www.netbeans.org/kb/support.html
v.
*** Issue 162247 has been marked as a duplicate of this issue. ***