XWidgetSoft Forum

Just as per the Network core, the CPU core does not seem to want accept an interval of greater than 1000ms. If you change it to 3000ms it seems to 'take' for the lifetime of the current running widget but if you open the IDE and check you will find the value has reverted to 1000ms.

1000ms is too frequent for an animated gauge and causes an unnecessary CPU overhead when the pointer is attached to a switch animation. A CPU gauge that uses too much cpu usage is rather pointless.

WORKAROUND:NONE

SEVERITY: MEDIUM

Yes, I agree. I have already mention it that XWidget should be optimised there to make the animations more usable.. Many times I want to use them but the increased cpu ruins the idea. XWidget in general uses minimal resources, and this is great, but in that part loses points.
Keep in mind though Dean that the design affects a LOT this part. I mean the general size/space of the widget. Also I have noticed using XWidget on two different laptops, complicated widgets use more resources on slow, old systems.. General rule: Big size widgets with animation = more cpu.

_________________
...and remember: don't take life too seriously...
My profile on Deviantart: http://jimking.deviantart.com/

I don't really care about the animation myself. It is just a fact that it affects a user's widgets in this manner. That is the impact of the bug.

I expect that others depend upon the animations as it is one of the main features Xwidget provides. Animations that are resource-hungry are largely counter-productive when used in the way I described.

What I really care about is the fact that the IDE gives you control of the interval but the core takes it away. This is the bug. Please add it to the list. Thanks in advance.