[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: kdebase/konqueror/iconview
From:       Simon Hausmann <shaus () helios ! med ! Uni-Magdeburg ! DE>
Date:       1999-11-05 19:38:36
[Download RAW message or body]



On Fri, 5 Nov 1999, Dawit Alemayehu wrote:

> On Fri, 05 Nov 1999, Waldo Bastian wrote:
> > On Fri, 05 Nov 1999, Stefan Taferner wrote:
> > > On Fri, 05 Nov 1999, Waldo Bastian wrote:
> > > > On Fri, 05 Nov 1999, Simon Hausmann wrote:
> > > > 
> > > > > Hmmmmmm
> > > > > Well, perhaps we should skip the the-source-can-decide-about-the-action
> > > > > way completely and fully go for your popup menu approach :)
> > > > > This kills all doubts (from the user's POV) about which action is going to
> > > > > be taken :)
> > > > 
> > > > Form a UI point of view I think this is preferred. When you drag and
> > > > drop you probably have some behaviour in your mind. The popup menu
> > > > reminds you that there are several actions possible. This might not
> > > > have occured to you. E.g. you might think that drag and drop always
> > > > copies and only after dropping you discover that it was moved. With a
> > > > popup menu this can't happen.
> > > > 
> > > > I will add the "destination decides about action" rule in the new style
> > > > guide if no-one objects too heavily :-)
> > > 
> > > Does this read that the destination selects if things are moved/copied/whatever?
> > 
> > Yes, by means of a popup menu. (Or do I miss something here?)
> >  
> > > Mind you, there is a good reason why we have the popup menu now.
> > > Use Winblows for a while and you know why the destination-selects-mode
> > > approach sucks: you can never be sure what the apps do as default.
> > > This often leads to the wrong behaviour.
> > 
> > Windows has source-decides-mode doesn't it?
> > 
> > With "destination decieds about action" I mean that a popup window
> > should come up if there are multiple actions possibile. (This popup
> > window is provided by the destination isn't it?)
> > 
> > I do agree with you on this issue. It seems I may have the wording
> > wrong. :-]
> 
> Quick question here guys.  How is it possible to make a decision of based on
> the destination when it is unknown ?  I mean when I right click on an item, you
> have no way of knowing the destination so you cannot decide which actions the
> popup menu should have.  In both the drag and drop case and the Copy/Cut/Paste
> case what destination supports only comes into question when the drop or Paste
> action occurs right ?  and then we have to check if that action could be
> supported by the destination.  If not you get an error from kio or the app. 
> Am I totally off the wall here ?

Why not simply let the destination create the popup menu and ignore the
QDropEvent::action() value? :-)

At least that's what I had in my mind.

Ciao,
 Simon

[prev in list] [next in list] [prev in thread] [next in thread]