Re: Should file_op delete really hang around for subsequent invocation by target_callback?
Thomas Leonard <[email protected]> Wed, 15 Oct 2014 08:45:39 +0100
| Newsgroups | gmane.comp.desktop.rox.devel |
|---|---|
| Message-ID | <CAG4opy9VXONk=p=truoXSpU8aBZR8Lf58t3P8O3yag+E0dPYiQ@mail.gmail.com> |
On 15 October 2014 04:46, Christopher Oliver <[email protected]> wrote: > If you type ctrl/x to a filer window with nothing selected, an action_delete is pending for a future selection. > This survives changes in window focus, and can cause quite unexpected results. E.g. click a directory you > want to visit, and watch it get blown away instead. Perhaps this should be active for only a short time, or > perhaps, leaving a filer window should cancel this pending operation. Otherwise, this seems like an obvious > disaster waiting to happen. I've already been bitten by this a couple of times. Pending delete's too much > like a loaded gun casually left lying around. Perhaps unloading it when not needed is the best/safest idea. Resetting it when the window loses focus seems reasonable. I imagine most people will have delete operations set to confirm first anyway though... -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho