Files open in SlickEdit locked for other applications!?

[hs2]

Oh dear - that's really weird !
@Dan: This should be handled better, right ?
I believe in you that this get's improved

HS2

[Dan]

Oh dear - that's really weird !
@Dan: This should be handled better, right ?
I believe in you that this get's improved

HS2

Well, certainly we're open to suggestions, but in general this option has worked out pretty well for us.  If we load part of the file we have to keep a handle to it open, and generally for very large files this is OK.  Usually files this large are log files or some sort of non-source files.

[hs2]

I agree - technically everything is fine.
I thought of a small hint in the settings dialog / help telling that 'partially loaded files are locked' too.

HS2

[Dan]

I agree - technically everything is fine.
I thought of a small hint in the settings dialog / help telling that 'partially loaded files are locked' too.

HS2

This I can certainly suggest.  Good idea.

[jbezem]

May I suggest an option/default behavior to open such files read-only? I often have such log-files, and if opened read-only (even if writable on disk), I have no trouble.
Frequently such log files (in my customary setups, using Lint, QA-C and various other checker tools) are written again and again in a separate context, and I do not want to close the file, just to reopen them again after the next run.
Currently I have created a macro for a certain extension to be opened read-only always (thanks, hs2!), but opening large files (esp. 'partial load') read-only would be very useful.

FWIW,

Johan