Object Edit bugs

from Stardock Forums

I use oe from the command line quite a bit and there is an annoyance that I'd like to see addressed:  If I start oe with 'oe readme.txt', the readme.txt that opens is the one from the oe directory.  This occurs even when I am not in the oe directory or if I include the full path to the readme.txt I want to open as in 'oe "c:\a directory\readme.txt"  When I issue "c:\a directory\a different file.txt"  the correct 'a different file.txt' file does open correctly.

The other issue is with large files (20 mb text files or so).  When using large files, I will often get exceptions when using the search feature multiple times.

 

617 views 1 replies
Reply #1 from Stardock Forums Top

Technically a bug but I'd rather see as an enhancement request:

If you try to save a read-only file you should get a message telling you that (Or the option to "override" the read-only flag).

Right now OE defaults to the "save as" dialog, which is fine if you are aware of this behavior. At best this can be confusing.

Another nice and related feature: A "read-only file" visual flag (Easy stuff: just append "[Read-Only]" to the filename at the title bar!)