Bug 924725 - New graphs: refresh by clicking on "set interval" redraws the whole screen
Summary: New graphs: refresh by clicking on "set interval" redraws the whole screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.10
Assignee: Mike Thompson
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On: 1000175
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-22 11:33 UTC by Heiko W. Rupp
Modified: 2014-04-23 12:30 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-23 12:30:02 UTC
Embargoed:

Attachments (Terms of Use)
Screen capture (724.70 KB, video/x-m4v)
2013-03-22 11:35 UTC, Heiko W. Rupp 		no flags Details
View All

Description Heiko W. Rupp 2013-03-22 11:33:22 UTC 
When I want to refresh the graphs I have to either reload the whole page or click on the "set interval" button.

This does not only redraw the graphs, but the whole screen which results in some flickering and also in an increased load on the server.

We should perhaps introduce a dedicated refresh button next to "set interval".
And perhaps also implement some auto-refresh.

See attached video
Comment 1 Heiko W. Rupp 2013-03-22 11:35:12 UTC 
Created attachment 714495 [details]
Screen capture
Comment 2 Mike Thompson 2013-07-10 03:25:19 UTC 
Auto refresh is implemented. I just fixed this for the multi-resource graphs.

Committed to master: 746007a
Comment 3 Mike Thompson 2013-07-10 03:26:51 UTC 
Opps. Wrong commit above: fd4316e
Comment 4 Mike Thompson 2013-09-18 21:03:09 UTC 
Most of this work was actually done as part of https://bugzilla.redhat.com/show_bug.cgi?id=1000175. This was complicated.

See comment2 and 3 https://bugzilla.redhat.com/show_bug.cgi?id=1000175#c2

This is committed to master: 3507a4d

The excess screen refreshing is now resolved (and the screen paints faster).
Comment 5 Heiko W. Rupp 2014-04-23 12:30:02 UTC 
Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.
Note You need to log in before you can comment on or make changes to this bug.