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 11823

Summary:	read-only files: property disabling inconsistent
Product:	java	Reporter:	Jan Benway <benway>
Component:	Source	Assignee:	Svata Dedic <sdedic>
Status:	NEW ---
Severity:	blocker	CC:	druiz, raccah
Priority:	P3
Version:	3.x
Hardware:	PC
OS:	Windows 3.1/NT
Issue Type:	ENHANCEMENT	Exception Reporter:
Bug Depends on:	15317
Bug Blocks:	7511

Description Jan Benway 2001-04-27 21:24:20 UTC

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.

Comment 1 Jan Becicka 2001-05-03 16:42:23 UTC


*** This issue has been marked as a duplicate of 7511 ***

Comment 2 Jan Benway 2001-05-22 00:49:22 UTC

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.

Comment 3 Svata Dedic 2001-06-06 09:37:31 UTC

Which properties behave this way ? File properties like "execution", 
"arguments" or properties for objects inside file (methods, fields, ...) ?

Comment 4 Jan Benway 2001-06-06 17:37:52 UTC

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.

Comment 5 Svata Dedic 2001-06-06 18:25:01 UTC

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.

Comment 6 Jan Benway 2001-06-06 18:27:28 UTC

Sorry I picked a bad example. :) 

Do you have the information you need now?

Comment 7 Svata Dedic 2001-09-10 12:11:48 UTC

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.

Comment 8 Jan Becicka 2005-10-12 15:56:38 UTC

*** Issue 7511 has been marked as a duplicate of this issue. ***

Comment 9 Rastislav Komara 2009-02-03 10:56:27 UTC

Overtake.

Comment 10 Jan Lahoda 2010-05-11 13:46:37 UTC

Resetting assignee to default for all bugs reported against product java and assigned to moonko.