Bug 75 - Define good monitoring presets
Status:
RESOLVED FIXED
Component:
GUI :: gtkmm
Version:
unspecified
Hardware:
PC Linux
Importance:
P3 normal
Target Milestone:
---
Assignee:
Rob Caelers
URL:
Depends on:
Blocks:
74
Reported:
Sep 14 2002 20:27:21 UTC
by:
Raymond Penners
Modified:
Oct 22 2002 01:54:46 UTC
WhoWhenWhatRemovedAdded
Raymond PennersSep 14 2002 20:27:29 UTCblocks4545,
Raymond PennersSep 14 2002 20:34:29 UTCblocks74
Raymond PennersOct 17 2002 11:56:43 UTCsummaryDefine good monitoring presetsDefine good monitoring presets
Raymond PennersOct 17 2002 13:09:37 UTCstatusNEWRESOLVED
resolutionFIXED
Description
Raymond Penners  Sep 14 2002 20:27:21 UTC
We need some good values for activity/idle/noise for each of these settings.

  // name, activity, idle, noise
  { "Trigger-happy", 1000, 1000, 0 },
  { "Nervous", 1000, 1000, 500 },
  { "Alert", 2000, 5000, 1000 },   
  { "Normal", 1000, 5000, 9000 },  // Preferable KJ's settings
  { "Sluggish", 1000, 10000, 9000 }, // Rob's settings
  { "Numb", 1000, 10000, 9000 },
Comment 1
Raymond Penners  Oct 17 2002 11:56:43 UTC
I've checked the current settings, and all look fine to me, except for "Quick"
and "Normal". Two problems here:
a) Normal uses settings where noise time > activity time.
b) Quick is slower than normal.

a) needs to be fixed first, and then we can come up with a decent "Quick" that
fits in between "Trigger happy" and "Normal".

But, I am going nuts here... I've been trying to find some settings where noise
time < activity time that behave +/- similarly to the current "Normal".

HELP!
Comment 2
Raymond Penners  Oct 17 2002 13:09:37 UTC
Do not DARE reopen this bug.