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.
If a java file is read-only, the behavior of the properties for that file is inconsistent. Sometimes its properties are enabled and an error message appears when the user tries to make a change. Sometimes the properties are disabled. In general, the properties are disabled if the selection is in the editor and enabled if the selection is in filesystems, but it varies a little. Maybe it has to do with when the property sheet is created for the node? The main point is that I think the property sheet behavior should be consistent for read-only files, and I think that the properties should be enabled in this case. Leaving the properties enabled will help the user know what to do. If the user makes a change, the IDE can bring up a dialog box saying the file is readonly (see bug 7511). And, if the file is under source control, the SCM can bring up a message asking the user to check the file out.
*** This issue has been marked as a duplicate of 7511 ***
I would like to re-open this. The problem here is that properties are sometimes left enabled even when the file is read-only. This is different from 7511, which deals with user feedback only, and has been changed to an enhancement.
Which properties behave this way ? File properties like "execution", "arguments" or properties for objects inside file (methods, fields, ...) ?
It's for stuff in the file, like "extends". I'm able to see the inconsistency most of the time this way: Mark the file read-only. Select the class node in the explorer. Properties are disabled. Now click the class declaration line in the editor. The same properties are suddenly enabled.
Yes, I see. BTW "extends" property relates to a class not to the file directly. I wanted to know if property sheet for the source file itself is broken or if the bug is only in nodes' properties.
Sorry I picked a bad example. :) Do you have the information you need now?
I'm seeing a difference, but it's just the other way around -- when I make a file read-only, the properties for node taken from the editor are OK, showing as disabled. Properties for nodes in the Explorer are always as they were before I changed file's R/O status. I cannot fix it because the filesystems does not provide a notification about r/o attribute change AFAIK. I'm changing this bug to an enhancement and linking it to the enhancement request for filesystems.
*** Issue 7511 has been marked as a duplicate of this issue. ***
Overtake.
Resetting assignee to default for all bugs reported against product java and assigned to moonko.