PopupFlags in konq_listviewwidget.cc

[Julian Rockey]

David, OK thanks, I've done that, works fine on 3.2 now.
Actually now I reflect I don't think BC is kept between releases for konqueror 
parts anyway - in my experience I always have to rebuild my app, otherwise I 
get undefined symbol errors in konq_listview.so anyway, i.e.

kdecore (KLibLoader): WARNING: library=konq_listview: file=/opt/non-portage/
kde/HEAD/lib/kde3/konq_listview.la: /opt/non-portage/kde/HEAD/lib/kde3/
konq_listview.so: undefined symbol: _ZN9KListView8takeItemEP13QListViewIte

which is application built against 3.1 trying to run against 3.2.

cheers
Julian

On Friday 02 Jan 2004 23:52, you wrote:
> On Friday 02 January 2004 12:24, Julian Rockey wrote:
> > ...
> > My question is: is this intentional - i.e. apps cannot rely on the
> > browserextension API to remain stable? And the only way to make the code
> > work with 3.1 and 3.2 is to #ifdef? So I can't make a binary that works
> > on both?
>
> ...
> You could connect to a signal even if it's not defined anywhere - but your
> slot using PopupFlags would not compile on KDE-3.1. However since you don't
> need the actual flags, you could simply remove that argument from the slot
> - it's allowed to connect a signal with 5 args to a slot with 4 args,
> dropping the last one.