http://redmine.emweb.be/http://redmine.emweb.be/favicon.ico?16934085252014-07-29T17:19:12ZRedmineWt - Bug #3504: WCartesianChart Firefox V29/V30 CPU usage problem when using PointSeries with more than 500 entrieshttp://redmine.emweb.be/issues/3504?journal_id=98202014-07-29T17:19:12ZKoen Deforchekoen@emweb.be
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>Koen Deforche</i></li></ul><p>Hey,</p>
<p>I believe it is a bug specific for Firefox/Linux. Firefox/Windows and Firefox/Mac (same versions) do not suffer from this problem. The only workaround I could find is to remove shadow.</p>
<p>Regards,<br><br>
koen</p>
Wt - Bug #3504: WCartesianChart Firefox V29/V30 CPU usage problem when using PointSeries with more than 500 entrieshttp://redmine.emweb.be/issues/3504?journal_id=98232014-07-30T13:07:18ZStefan Ruppert
<ul></ul><p>Hi Koen,</p>
<p>thanks for investigating this problem. For now I'll disable the shadow effect for point series.</p>
<p>What about a general zoom functionality as implemented in the TestGraph? The only thing which is missing from my point of view is calculating automatically new Y-Axis range based on the new X-Axis range. I didn't find/understand the auto range calculation in the current implementation...</p>
<p>Regards,<br><br>
Stefan</p>
Wt - Bug #3504: WCartesianChart Firefox V29/V30 CPU usage problem when using PointSeries with more than 500 entrieshttp://redmine.emweb.be/issues/3504?journal_id=98472014-08-05T10:22:16ZKoen Deforchekoen@emweb.be
<ul></ul><p>Hey,</p>
<p>By default the Y axis range will be automatically adjusted to the data that is available. So if you adjust the X axis range, the Y axis range will be recomputed.</p>
<p>I suppose then that's not what you're seeing or want?</p>
<p>Regards,<br><br>
koen</p>
Wt - Bug #3504: WCartesianChart Firefox V29/V30 CPU usage problem when using PointSeries with more than 500 entrieshttp://redmine.emweb.be/issues/3504?journal_id=98512014-08-05T11:30:14ZStefan Ruppert
<ul></ul><p>Hi,</p>
<p>ok, then its a bug ;-/ If I set a new X range using WCartesianChart::axis(XAxis).setRange(min, max), the Y axis min/max is not changed. You can verify this, be zooming into the green values on the right side using the mouse wheel of the test app!</p>
<p>Regards,<br><br>
Stefan</p>
Wt - Bug #3504: WCartesianChart Firefox V29/V30 CPU usage problem when using PointSeries with more than 500 entrieshttp://redmine.emweb.be/issues/3504?journal_id=98522014-08-05T11:33:07ZStefan Ruppert
<ul></ul><p>Hi,</p>
<p>Stefan Ruppert wrote: </p>
<blockquote>
<p>Hi Koen, </p>
<p>thanks for investigating this problem. For now I'll disable the shadow effect for point series.</p>
</blockquote>
<p>yesterday I played a little bit more with this problem and it is not so easy. Even if I disable the shadow firefox slows down dramatically. Also BarSeries seems to have this issue... Do you have a channel to mozilla to address such problems?</p>
<p>Regards,<br><br>
Stefan</p>
Wt - Bug #3504: WCartesianChart Firefox V29/V30 CPU usage problem when using PointSeries with more than 500 entrieshttp://redmine.emweb.be/issues/3504?journal_id=98542014-08-05T11:48:59ZKoen Deforchekoen@emweb.be
<ul></ul><p>Hey,</p>
<p>I did make some changes, which I still need to push.</p>
<p>Regards,<br><br>
koen</p>
Wt - Bug #3504: WCartesianChart Firefox V29/V30 CPU usage problem when using PointSeries with more than 500 entrieshttp://redmine.emweb.be/issues/3504?journal_id=100912014-10-14T13:18:50ZKoen Deforchekoen@emweb.be
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>Target version</strong> set to <i>3.3.4</i></li></ul> Wt - Bug #3504: WCartesianChart Firefox V29/V30 CPU usage problem when using PointSeries with more than 500 entrieshttp://redmine.emweb.be/issues/3504?journal_id=102172014-10-22T00:27:58ZKoen Deforchekoen@emweb.be
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>