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

List:       kde-devel
Subject:    Re: Plasma::DataEngine not automatically updating
From:       Shantanu Jha <jhahoneyk () gmail ! com>
Date:       2009-02-18 19:13:26
Message-ID: ec556b640902181101y2e2cf9d4h6ca369815a632a1b () mail ! gmail ! com
[Download RAW message or body]

So, Is there any workaround till the bug is fixed, I mean is it
somehow possible to destroy the object and recreate it? (Apologies if
didn't make sense, i'm kinda newbie ).

On Thu, Feb 19, 2009 at 12:25 AM, Trever Fischer <wm161@wm161.net> wrote:
> On Wednesday 18 February 2009 01:16:53 pm Shantanu Jha wrote:
>> I noticed that The System Monitor - Network applet did not
>> automatically updated its network interface list, i.e. if I connect a
>> dial-up modem, the interface ppp0 is not shown in the applet's
>> settings. However, if the applet is restarted, the list is updated.
>> I've examined the source (
>> kdebase/workspace/plasma/applets/system-monitor/net.cpp ) and found
>> that it uses "systemmonitor" as the data engine, and whenever a call
>> to engine()->sources() is made ( in the function
>> SM::Net::parseSources() ), the list returned back doesn't contain
>> "ppp0", if the interface was connected after the applet was started.
>> This means that the data engine is not getting properly updated.
>> Further, there are no public member functions of Plasma::DataEngine
>> which can force a update/refresh.
>> So, is this a bug in the DataEngine or am I missing something?
>> I am using Kubuntu 8.10 with latest kde svn trunk build. Thanks in advance,
>
> This is a bug with the DataEngine. Currently, it does not issue periodic
> updates for the list of all sources. When the engine object is first created,
> it requests the list, then forgets about it for eternity.
>
>
>>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>
>



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