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

List:       kfm-devel
Subject:    Re: help!
From:       Simon Hausmann <shaus () uermel ! med ! Uni-Magdeburg ! DE>
Date:       1999-09-26 11:15:07
[Download RAW message or body]


This slot method is connected to the QListView signal. When the selection
changes (and therefore the corresponding Qt signal of the listview is
emitted), this slot gets called and emits the corresponding KOM signal.
The mainview connects to this KOM signal and upon invokation it updates
the copy/paste/delete entries in the menu/toolbar by doing invokations
through the EditExtension interface (which KonqKfmTreeView implements) .

Ciao,
 Simon

On Sun, 26 Sep 1999, Thomas Zander wrote:

> I am completely going mad!
> 
> OK, 
> 
> I am trying to find out the source of some bugs. This is always hard work, but
> with code like:
> void KonqKfmTreeView::slotSelectionChanged()
> {
>   kdebug(0, 1202, "slotSelectionChanged");
>   SIGNAL_CALL0( "selectionChanged" );
> } 
> 
> You don't even know what happens.
> 
> Can someone tell me the runtime tree of objects. So I know where a signal like
> selectionChanged comes from and in this case where it goes.
> 
> 
> Thanx.
> 
> 
> ps. I am trying to find out why a shift-arrow kind of selection does a select
> on the object where it is going to, not where it was.. Ooh never mind.
> 
> --
> Thomas Zander                                              zander@earthling.net
> Today, it's understood that of course you'll use a computer,
> because it makes other people's lives easier -- or, more         icq: 970 00 05
> accurately, it enables them to maintain their manic pace.      gpg-key:  0588D5
> 

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