Watch, Follow, &
Connect with Us
Public Report
Report From: C++BuilderX/IDE/Code Editor    [ Add a report in this area ]  
Report #:  6544   Status: Reported
Editor Readonly-Option is missing
Project:  C++BuilderX/BC++ 2005 Build #:
Version:    1.0 Submitted By:   Peter Mandrella
Report Type:  Suggestion / Enhancement Request Date Reported:  12/2/2003 8:36:55 AM
Severity:    Commonly encountered problem Last Updated:
Platform:    All versions Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (1 Total Rating)
5.00 out of 5
Total Votes: None
In previous releases of C++Builder, there was an option to override the read-only status of an editor file, by pressing the right mouse key (or Alt+F10) in the editor window and then toggling the "read only" option. This was very useful to do temporary changes to code which should not be modified permanently.

In C++BuilderX I cannot find any way to override the readonly status. I would appreciate if this feature could be re-added.
Steps to Reproduce:

Gillmer Derge at 12/4/2003 8:23:48 AM -
Unfortunately this is more difficult to implement than it appears.  Java doesn't provide a way to make a file writable.  You can make it read only but you can't make it not read only.  Thus, you need to resort to something non-portable if you want this functionality, so I suspect it won't make it into C++BuilderX until it's supported in the Java API's.

The OpenTool below might work.  It's written for an older version of JBuilder, but as long as it doesn't use any JBuilder-specific features (it shouldn't need to), it should work with C++BuilderX too.

Peter Mandrella at 12/18/2003 7:39:02 AM -
Thanks four your reply, but you misunderstood the issue. The file on disk should stay read-only, but the copy of the file wich is loaded into the C++Builder editor should still be changeable (without being able to write the changes to disk). This is possible with C++Builder 4-6 and should be easy to implement even in Java.

Server Response from: ETNACODE01