There is one more benefit of asynchronous update.<br>
Suppose one sensor supplies some datasets (e.g. sensorsensor) . You
want one meter to show one data from those datasets, other meter to
show otherdata from that datasets. So those meters may want to have
different update intervals.<br>
This is perfectly possibly with current dotted notion.<br>
So if sensor is not multiply instantiated, you can have different
update interval for meters for same sensors within same karambawidget.<br>
<br><br><div><span class="gmail_quote">On 19/09/05, <b class="gmail_sendername">Vinay Khaitan</b> <<a href="mailto:vkhaitan@gmail.com">vkhaitan@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
First thing, the problem is about synchronisation of meters, which uses
same sensor. It is not possible when using asynchronous update of
meters data by sensors. And we need asynchronous updates for singleton
pattern. So that we can support different refresh rate for meters.<br>
<br>
We need singleton pattern, because we want to minimise resource uses.<br>
Imagine a scenario, where there are 4 karambas lying with 4
cpusensors(cpusensor is just an example). All of them updates at 2000
ms interval. so within 2 second there would be 4 updates, whereas we
could do with single update. That's why we need asynchronous update of
meter data.<br>
this scenario is possible in cases , where suppose a karamba is lying
with graph-cpu at bottom of desktop, the other karamba is at the top of
desktop with bar meter-cpu sensor. and so on.and we want in the future
to make karambas split by dragging. So singleton patter and
asynchronous update is inevitable for scaling in future. <br>
<br>
I find meter connection the best thing. If we think from OO viewpoint,
you want that you require synchro between two meters, which implies
that there should be made a connection between meters. <br><br>
<br>
<div><span class="q"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Don't you think, that if you need to workaround a problem with your design,
<br>it's better changing your design and not introducing strange things?
</blockquote></span><div><br>
All the designs has some plus and minus points. We should take that design, which is the most suitable.<br>
I differ from the word "strange". in qt world, where signal-signal connection is possible, this is normal.<br>
<br>
</div><span class="q"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">You say it's an easy solution, but I think it's bad since it's a solution
<br>ad-hoc for a problem you have with your design.
</blockquote></span><div>it's not ad-hoc. I find it nicer even in the case, when you dont need them.<br>
</div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> If I wouldn't know anything<br>about that, I couldn't understand why is needed interconnecting meters.
</blockquote><br></span><div>That's why I would like to know the viewpoint of other developers.<br>
Please, from next mail onwards, be kinder to me :))<br>
<br>
cheers, <br>
Vinay Khaitan<br>
</div></div><br>
</blockquote></div><br>