Bug 54635 - Redraw triggers graph scrolling
Summary: Redraw triggers graph scrolling
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xosview   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2001-10-14 20:48 UTC by Craig Lawson
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-10-14 20:48:07 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Craig Lawson 2001-10-14 20:48:03 UTC
Description of Problem:
  Forcing the xosview window to redraw triggers the scrolling graphs to
scroll. The extra scrolling makes the graphs inaccurate. For example, if
the CPU graph is configured to to scroll once every two seconds, then 60
redraw events can cause the graph to represent that 120 seconds have
passed, when in fact only one or two actual seconds may have elapsed.

Version-Release number of selected component (if applicable):
1.7.3, release 4

How Reproducible:

Steps to Reproduce:
1. Add the following to your .Xdefaults, or pass as -xrm arguments on the
command line:
    xosview*cpu: true
    xosview*cpuGraph: true
    xosview*cpuPriority: 20
2. Start xosview.
3. Open another window. A terminal window will do. Grab the terminal window
with your mouse, and move it around the screen. Pass it over the xosview
window to send redraw events to xosview. While it partially covers xosview,
wiggle it a lot to generate a lot of events.

Actual Results:
The CPU graph scrolls with haste while it processes the redraw events.

Expected Results:
The CPU graph should update only once every two seconds.

Comment 1 Ngo Than 2001-10-16 16:04:02 UTC
cannot reproduce it here. the CPU graph updates correct only once every two seconds.

Note You need to log in before you can comment on or make changes to this bug.