Re: Drag and drop creates some kind of self referential loop

On Mon, 19 Sep 2005 18:35:55 +1000
TomPh <tpgww@xxxxxxxxxxx> wrote:

> On Sun, 18 Sep 2005 13:29:03 -0400
> alaterale@xxxxxxxxxxxxx wrote:
> 
> > I know now emelfm2 conforms to the dnd standard, but as recent as
> > 0.0.9-r1 if you dragged the mouse downward you would select files
> > (this is the only e2 build currently available in portage).  Now,
> > with 0.1.2, you pick up the first file you start clicking on.  So
> > for me and a few people I know, its a change in how to use
> > emelfm2.  I personally enjoy the former behavior better, and I was
> > just suggesting having a configuration option about this, where the
> > default was to allow drag and drop, but the user could deselect it
> > if it suited them.  Or, even better probably, let the user select
> > which mouse button activated the pick-up-item action (I think it
> > was the middle click previously).  So letting people swap which
> > mouse press did what (activating dnd or just plain selecting files)
> > would be something I'd like to see.  I don't want to remove dnd
> > from the app, I just want to have more options to use it :P
> Ah, that's a BIG deal (and slow).
> Would need to go back to replicating gtk selection, i.e managing
> [un]selection process and range-[un]selection process, as well as
> double-clicks, background-color, hinted-background [etc?]
> 
> Not something I'm wild about ...
I found a way to make "drag-selection" co-exist with current dnd
arrangements, provided:
- a control key is involved in the process (i.e. press it after
the left-mouse-button but before dragging - or else the selection-state
of the clicked item toggles as it should)
- we don't mind the dnd cursor being displayed when we're not dragging,
really
- we can live with a hard-coded interval between clicks, to decide
what is a double-click (I picked 330 msec)

Code ends up like spaghetti, but who needs maintenance, anyhow ...

Regards
Tom


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: