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

List:       kde-devel
Subject:    Re: Problems with Solid in kio-slave (Slots not called, properties not updated)
From:       David Narvaez <david.narvaez () computer ! org>
Date:       2013-02-12 18:41:23
Message-ID: CACFh1D4QyZULTcX-PAmyK5Fwe+gqhOJ3ZZrYfkFWEJbX_+jRyg () mail ! gmail ! com
[Download RAW message or body]

On Mon, Feb 11, 2013 at 12:45 PM, Philipp Schmidt <philschmidt@gmx.net> wro=
te:
> Hi Alex,
>
> that's exactly why I created a separate Thread and moved the Objects that
> need
> to have slots called there. I just altered my little example and if I set
> the
> timer to normal recurring (not single shot) the slot gets called as
> expected.
> So the problem is probably not in my code.
>
> Also: As noted in the last part, when called repeatedly from kio (not
> using
> signals/slots) Solid also does NOT update information about devices. It's
> like
> it is stuck with the information it got when it was first initialized.

I have been debugging exactly the same situation in the Activities KIO
Slave. I tried putting the affected parts in their own thread, and
that didn't work. Right now I have a processEvents() call before using
those objects which at least changes some values (it used to stay
stuck with the information it got when it was first initialized) but
those are stale.

The implementation that went into 4.10 depends on no signal/slots and
that works, but it is of course less efficient. I've given up for the
moment in trying to find a solution, but if you manage to solve your
situation please let me know.

David E. Narv=E1ez

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