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

List:       kde-core-devel
Subject:    Re: klistview problems
From:       Peter Putzer <pputzer () edu ! uni-klu ! ac ! at>
Date:       2000-10-27 0:08:21
[Download RAW message or body]

On Thu, 26 Oct 2000, David Faure wrote:

> On Thursday 26 October 2000 21:48, Peter Putzer wrote:
> > Why do it using "moveItems"? Just handle the drop yourself.
> I am handling the drop myself now, for other reasons, but note that to
> implement dropping on a group, one also needs to improve the
> "drop visualiser"......

which is overridable, IIRC.

> > > This is all internal in klistview, except that we need to tell the application
> > > about it, the way we do with moved().
> > > The problem is that if the application doesn't know about this signal, it might
> > > not update its internal stuff appropriately. This means that dropping on groups
> > > should probably be off by default, and activated by the app.
> > > Well, I'm assuming there are apps that rely on the "moveable items" feature
> > > of klistview, but given how much it was broken, I'm not sure that's the case :-)
> > 
> > As far as I know no app uses it (besides "klistviewtest" in kdenonbeta ;)
> > 
> > > My point was that I don't see how to use the current signals for it, so we'll
> > > need a new one. But it looks bad as an API, having different signals emitted
> > > depending on whether the dropped item is first child or not. But well, trees
> > > don't turn out to be easy to handle, that's for sure :-)
> > 
> > But if you want to handle DND yourself, you don't need the "moved" stuff
> > at all, indeed you should disable "autoMoving" and handle the drop (and
> > subsequently the move) yourself, I really don't see the problem here.
> 
> Well, sure, but why would I implement this in the application instead of klistview,
> when the same amount of code is needed in both cases, and klistview's implementation
> is _obviously_ not complete. Are you implying that some application might be happy
> with being able to move items but never as the first child of a group ?
> Well, I guess a listview without group would, but that's quite limited IMHO.
> 
> I don't see why you would prefer me to improve my own listview instead
> of KListView :-)

OK *g*

It's just that I don't like the moveChildren code in KListView at
all... IMHO it shouldn't be there... um. If you've got an idea how to make
it usable for applications (you're right, currently it isn't), then my
dislike for that code would probably disappear...

bye,
Peter

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