|
|
|
[
Permlink
| « Hide
]
Harleen Gretzky added a comment - 19/Oct/07 02:21 PM
I've been able to read it.
it depends. Soemtimes you can, sometimes not.
Not sure why Resident Bonbon Flow closed this set of issues, so I'm reopening them.
The lag meter is not refreshing, it is giving real time readings. which is what is needed, i have no problems reading it.
@Rascal, I am not sure what you mean "The lag meter is not refreshing"?
It must be refreshing in order for new data to be shown on it. Sometimes the meter refreshes the data it is displaying quicker than the user can read it. I still find that the in certain situations the client meter changes to fast, especially when I move.
Jason, REAL Time meaning rather then refreshing every second, it is changing AS the lag conditions change, also IF you watch the the Lag meter you will see that it it not refreshing at a set rate such as every two seconds or some-such.
Refreshing MEANS it is taking a reading at a predetermined set rate such as every two seconds. The Lag meter gives real time data like the FPS meters. and im performance meters in the client menue. I don't know how better to explain this. Agreed to Jasons comment ... sometimes it really refreshes to fast to read. I had this on my list too. Hint text should not disappear the moment light turns green. It should fade within 3-5 seconds and then be replaced with 'Normal'. Maybe it shouldn't fade all the way as not to leave an empty space in the pane. If condition turns yellow to red, message should be replaced immediately. If a different message of the same (or lower) level would be in order during the fade, I think it could be simply dropped. It will probably get its chance to be displayed eventually. If the same condition recurs, the fade algorithm should simply reset.
A couple of other suggestions:
BTW, why is the lag meter always transparent? Should be solid at least when clicked.
BTW, I linked silently to VWR-3353 back then, but want to draw some attention to it now. There are some ideas there to also have a simple algorithm that would ignore short bursts/spikes. Basically something simple that would require a threshold exceeded condition to persist for say 3 seconds (or occur in more than 30% of samples during the last 10 seconds) before it is reported.
I think a simple answer for this would be a little text box attached to the lag meter, showing the last few messages it displayed aside from normal.
I disagree, WarKirby. A window with information that changes quickly and flashes is distracting. It should be smooth as not to cause strain to the brain
But that depends also on how it is intended to be used. If it is to be used only when troubleshooting, then your suggestion might work. But where would that box be? Even as it is, the window is too large for many people. OK, we assumed it's for troubleshooting only. But then even more the need to have a mini version. And the statistics window also gets absurdly large if you want to see the same information you get with the lag meter (feel free to vote on VWR-3364). |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Reopened
Low
Lag meter refreshes too quick to read
