Problems with the KTabWidget

[Jens Dagerbo]

Are you running up-to-date CVS? 

If I set the close-on-hover button to appear (User Interface settings) I can 
close tabs using it fine.

jd

On Tuesday 04 May 2004 17:08, Andras Mantia wrote:
> Hi,
>
>  Since some days (I believe since the editorProxy changes, but I'm not
> sure), the advanced behavior of KTabWidget is lost in KDevelop (closing
> with the close button on the tabs - there isn't any close button - or
> from the RMB menu). On startup the following warning appear:
>
> QObject::connect: No such signal KTabBar::contextMenu(int,const QPoint&)
> QObject::connect:  (sender name:   'tabbar')
> QObject::connect:  (receiver name: 'unnamed')
> QObject::connect: No such signal KTabBar::mouseDoubleClick(int)
> QObject::connect:  (sender name:   'tabbar')
> QObject::connect:  (receiver name: 'unnamed')
> QObject::connect: No such signal KTabBar::mouseMiddleClick(int)
> QObject::connect:  (sender name:   'tabbar')
> QObject::connect:  (receiver name: 'unnamed')
> QObject::connect: No such signal KTabBar::initiateDrag(int)
> QObject::connect:  (sender name:   'tabbar')
> QObject::connect:  (receiver name: 'unnamed')
> QObject::connect: No such signal KTabBar::testCanDecode(const
> QDragMoveEvent*,bool&)
> QObject::connect:  (sender name:   'tabbar')
> QObject::connect:  (receiver name: 'unnamed')
> QObject::connect: No such signal
> KTabBar::receivedDropEvent(int,QDropEvent*)
> QObject::connect:  (sender name:   'tabbar')
> QObject::connect:  (receiver name: 'unnamed')
> QObject::connect: No such signal KTabBar::moveTab(int,int)
> QObject::connect:  (sender name:   'tabbar')
> QObject::connect:  (receiver name: 'unnamed')
> QObject::connect: No such signal KTabBar::closeRequest(int)
> QObject::connect:  (sender name:   'tabbar')
> QObject::connect:  (receiver name: 'unnamed')
>
>
> This is printed out in KTabWidget::KTabWidget called from KMDI's
> KMdiDocumentViewTabWidget::KMdiDocumentViewTabWidget. Strange is that I
> don't see the same warning from Quanta (which uses KMDI as well), so
> something happened inside KDevelop, and I suspect some wrong
> Makefile.am. But I couldn't figure out what happened.
>
> Andras