in a local -read-only instance, one cannot distinguish (visually) between online & offline files
-read-only is only RO
in regard to Everything itself, to its' .db ...
it is not -read-only
in regard to changes that can physically be effected
when in -read-only mode, offline volumes are not grayed out
- should they not still be grayed out (or could they be grayed out)?
(better, an option, cause instances where no volumes
are local, all files would be grayed out, potentially less read-able?)
(if Everything only relied upon .ini, .ini would [potentially] indicate offline or not,
& with that appropriate volumes could be grayed or not to agree with a
non-read-only state)
now, you might be able to work around it, by setting up a Filter, where you manually deselect "known" offline volumes... but that means you have to know what is offline ahead of time.
so if I: & H: are offline, something like:
!I: !H: audio: distinct:so, what... -read-only does not then have the concept of "online:" (nor "offline:")?
so a Filter: like, audio: sort:name: distinct: online: is ineffectual.
hmmmm.
so i'd have to set up a filter of "known" /online/ volumes & then distinct: that.
or easier, i suppose, of known offline volumes & exclude those (from display), then distinct: that.
so, !I: !H: audio: sort:name: distinct:
(a work-around...)