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

List:       kde-devel
Subject:    PyKDE4: Solid.Networking
From:       Thomas Olsen <tanghus () gmail ! com>
Date:       2009-10-07 18:26:13
Message-ID: 200910072026.14081.tanghus () gmail ! com
[Download RAW message or body]

Hi

I first posted this in kde-bindings but I can see that it's a very low traffic 
list.

Just started figuring out how Solid works in a Python Plasmoid and I'm already 
stuck.

This small snippet returns 'True' when I'm connected and 'False' when
disconnected just as expected:
 
  self.is_connected = (Solid.Networking.status() == \
	Solid.Networking.Connected) == True
  print self.is_connected
 
But the following yields an exception:
 
  print str(Solid.Networking.notifier())
 
AttributeError: type object 'Networking' has no attribute 'notifier'
 
According to http://api.kde.org/pykde-4.3-api/solid/Solid.Networking.html
Solid.Networking has both a status and a notifier method.
 
  print dir(Solid.Networking)

Gives:

['Connected', 'Connecting', 'Disconnecting', 'Managed', 'ManagementPolicy', 
'Manual', 'OnNextStatusChange', 'Status', 'Unconnected', 'Unknown', 
'__class__', '__delattr__', '__dict__', '__doc__', '__format__', 
'__getattribute__', '__hash__', '__init__', '__module__', '__new__', 
'__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', 
'__str__', '__subclasshook__', '__weakref__', 'status']

So I guess it's not implemented in PyKDE4.3 yet? Is there any chance that it 
will be soonish or should I forget using Solid.Networking until I'm 
comfortable enough to code i C++ again?

Beware that the last time I coded for KDE/Qt nobody worried about namespaces 
so it might be that I'm just mixing things up.

-- 
Best Regards / Med venlig hilsen

  Thomas Olsen

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]