xffm issues

[Danny]

Hi!

Am Mon, 2003-08-18 um 22.56 schrieb edscott wilson garcia:
> On Mon, 2003-08-18 at 15:39, Danny wrote:
> > Hi!
> > [...]
> > > Why impossible? All I have to do is drop on a write protected volume.
> > 
> > Uhm, well yes, but the move cannot succeed at all, then ? So why start
> > moving in that case anyways? Or did I miss something?
> 
> Never underestimate what the user will try to do...

lol true :)

> [...] 
> > You are right, what I am doing is backing up... but what I'm getting at
> > is the general way of moving something, which I think is quite similar
> > to "back up source", "cd destination", "restore".
> > 
> > That it is implemented as "copy source destination", "delete source", is
> > just a detail of the real world. It is not even like this as long as
> > source *and* destination are on the same mount point.
> > 
> > If source and destination are on the same mount point, the move of a
> > directory works regardless on if there are other write-protected
> > directories *in* it or not.
> > 
> > Why the discrepancy?
> 
> Programming flaw? I think I get your point. If the write protected
> directory is part of the dnd selection, then do not erase, but if the
> write protected directory is *inside* the one of the dnd selected
> directories, then move it (preserving attributes). OK?

Yes :)

> 
> > 
> > > > 
> > > > > 
> > > [...]
> > > > Which leads me to a question before I even start: is it possible to add
> > > > some own programs to the xffm context menu of folder nodes ? ;)
> > > > 
> > > > (I could think of using it for "compression", "image viewer" and "size
> > > > statistics" right away)
> > > 
> > > If you want entries into the popup menu edit the libs/menu.c file and
> > > add the entries in the static autotype_t autotype[] structure. No
> > > problem if you add programs that do not exist. They will just not
> > > appear. Benny put in the __linux__ directives but they are not really
> > > required.
> > > [...]
> > > workdir by asking "Extract into" and making the command queued (no other
> > > "queued" autotype function will proceed until this one has finished).
> > 
> > Ahaaa ? Cool, queueing... muhahaha :)
> [...]
> No where. Move to is processed by window2. There is no dnd queue. You
> must wait till window 2 finishes. If you want to do another drop, do it
> to window3 (separate threads).

Hehe, too bad :) Well it was only a guess anyways :)

> 
> regards,
> 
> Edscott

cheers,
   Danny