[Kde-hardware-devel] Solid::Control not finding local loopback
David Hubner
hubnerd at ntlworld.com
Tue Jan 12 03:07:03 CET 2010
On Monday 11 Jan 2010 10:33:26 Will Stephenson wrote:
> On Monday 11 January 2010 02:40:41 David Hubner wrote:
> > On Friday 08 Jan 2010 12:53:28 Will Stephenson wrote:
> > > On Sunday 27 December 2009 21:05:25 David Hubner wrote:
> > > > On 27/12/2009 10:19, Will Stephenson wrote:
> > > > > On Tuesday 22 December 2009 20:29:08 David Hubner wrote:
> > > > >>> What are you using it for? (That might be the use case you were
> > > > >>> looking for ...)
> > > > >>
> > > > >> Solid Device Viewer, its in playground, its for KInfoCenter. I am
> > > > >> redoing most of its KCM's over Christmas as it looks like it needs
> > > > >> work. I shall be moving it into kdereview after 4.4 is released. If
> > > > >> you look at SolDeviceTypes.cpp under the SolNetworkDevice::* you
> > > > >> should see what I am looking at doing :)
> > > > >
> > > > > Nice project :)
> > > > >
> > > > > Will
> > > > > _______________________________________________
> > > > > Kde-hardware-devel mailing list
> > > > > Kde-hardware-devel at kde.org
> > > > > https://mail.kde.org/mailman/listinfo/kde-hardware-devel
> > > >
> > > > Thanks, it would be nothing if it was not for Solid :)
> > > >
> > > > I am also just wondering about Solid::Networking::Notifier, does it
> > > > send a signal when a single network card changes state (eg, loses
> > > > connection) or only if all network cards loose access to a network?
> > >
> > > Sorry for the delay, hopefully you'll have figured it out already,
> > > otherwise:
> > >
> > > Solid::Networking::Notifier signals system-wide 'online status'.
> > >
> > > Solid::Control::NetworkInterface (and subclasses) signal individual
> > > network cards state.
> > >
> > > Will
> > > _______________________________________________
> > > Kde-hardware-devel mailing list
> > > Kde-hardware-devel at kde.org
> > > https://mail.kde.org/mailman/listinfo/kde-hardware-devel
> >
> > Thanks, i have been playing around with it. I have been trying to connect
> > to every networkinterfaces ipDetailsChanged() signal by doing
> >
> > QList<Solid::Control::NetworkInterface *> nicList =
> > Solid::Control::NetworkManager::networkInterfaces();
> >
> > foreach(Solid::Control::NetworkInterface *nic, nicList) {
> > kDebug() << "Connecting " << nic->uni() << endl;
> > connect(nic,SIGNAL(ipDetailsChanged()),this,SLOT(nicChangedSignal()));
> > }
> >
> > For some reason it does not complain about the slot or signal not being
> > there ( because they are ) but it does not work. Its probably something
> > stupid i am doing :)
>
> Or a bug in the code emitting the signal - why don't you put a breakpoint in
> Solid::Control::NetworkInterface::ipDetailsChanged() and see if it is ever
> called?
>
> Will
> _______________________________________________
> Kde-hardware-devel mailing list
> Kde-hardware-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-hardware-devel
>
Yer, i had a look. Looks like the IpDetailsChanged() signal is not being emitted. The only signal that seems to be implemented is
stateChanged(uint new_state, uint old_state, uint reason).
I shall use that for the moment.
Thanks
--
David Hubner
IRC: hubnerd
MSN: hubnerd at hubnerd.org
ICQ: 24308559
More information about the Kde-hardware-devel
mailing list