------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=117513
------- Additional Comments From iwilcox iwilcox me uk 2006-01-29 18:33 -------
OK, here's a patch (below). It also hopefully fixes bug 92949 and bug 120989.
It correctly sets me away when I reach my autoaway timeout, when I lock the
screen manually and when I start the screensaver in non-locking mode, and in
all three cases I remain set away until I move the mouse or press a key. I
haven't tried it with a screensaver that kicks in by itself, but I'm sure
that'll work.
There's one small bit I'm not happy with, which is that if you unlock the
screen but do nothing else you don't get set active. I tried hooking the
KDE_stop_screensaver() signal up to call setActive() in kopete/kopeteiface.cpp
in just the same way as KDE_start_screensaver() calls setAutoAway(), but it
never seemed to trigger. Didn't look into why, but I left the DCOP connection
in there in case it's a bug somewhere else that gets fixed later.
Obviously most people unlocking their screen will proceed to do something and
thus get set active in the normal way so this won't be a problem, but it'd just
be that bit cleaner if the DCOP connection worked.
Seeing as some people seem able to reproduce this bug and some don't, it'd be
nice to get both someone else who can reproduce it to try this patch out and
confirm it works, and someone else who can't reproduce it eyeballing the code
and trying it to confirm that it at least doesn't make things any worse for
people without the bug.
Cheers,
Zak (Isaac Wilcox)
_______________________________________________
kopete-devel mailing list
[EMAIL PROTECTED]
https://mail.kde.org/mailman/listinfo/kopete-devel
