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

List:       kde-panel-devel
Subject:    Re: [PATCH] tooltip: add update parametr to updateToolTip function
From:       "Ismael Asensio" <caciquecola500 () gmail ! com>
Date:       2008-04-01 20:09:39
Message-ID: 80c786080804011309v50ac4ebap1c8fafb093d4e462 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


>
>
> > To make clear why I need this for digital clock:
> >
> > In digital clock we use Plasma::DataEngine and connectSource(...) with
> > interval 1sec or 60secs (depending on user's configuration).
> > DataEngine calls dataUpdated(...) every that interval and inside this
> > function we update displayed time in panel + displayed time in tooltip
> > - even if it's not displayed (tooltip). That causes a lot of unneeded
> > updates when tooltip is not visible.
> >
> > Problem will be even bigger when we introduce multizones support (I
> > have patch 90% ready). For each timezone we will use single query and
> > we will add response to tooltip. That will cause horribly big amount
> > on unneeded operations.
>

Sorry if I say something stupid here but to solve this issue couldn't the
tooltip just get updated before it is shown (updateToolTip), that is,
retrieving the time from all the required timezones and then, for the
seconds, get synced with the seconds info provided by the plasmoid itself
(If I understood it right, via data Updated).

That way the "expensive" retrieval of data would be the same either the
tooltip is shown or not.
Maybe is too hackish that way?

[Attachment #5 (text/html)]

<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br> &gt; To make clear why I \
need this for digital clock:<br> &gt;<br> &gt; In digital clock we use \
Plasma::DataEngine and connectSource(...) with<br>  &gt; interval 1sec or 60secs \
(depending on user&#39;s configuration).<br> &gt; DataEngine calls dataUpdated(...) \
every that interval and inside this<br> &gt; function we update displayed time in \
panel + displayed time in tooltip<br>  &gt; - even if it&#39;s not displayed \
(tooltip). That causes a lot of unneeded<br> &gt; updates when tooltip is not \
visible.<br> &gt;<br> &gt; Problem will be even bigger when we introduce multizones \
support (I<br> &gt; have patch 90% ready). For each timezone we will use single query \
and<br>  &gt; we will add response to tooltip. That will cause horribly big \
amount<br> &gt; on unneeded operations.<br> </blockquote></div><br>Sorry if I say \
something stupid here but to solve this issue couldn&#39;t the tooltip just get \
updated before it is shown (updateToolTip), that is, retrieving the time from all the \
required timezones and then, for the seconds, get synced with the seconds info \
provided by the plasmoid itself (If I understood it right, via data Updated).<br> \
<br>That way the &quot;expensive&quot; retrieval of data would be the same either the \
tooltip is shown or not. <br>Maybe is too hackish that way? <br>



_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel


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