QueueMetrics forum
QueueMetrics => Running QueueMetrics => Topic started by: scooby2 on August 12, 2008, 21:30:26
-
Thanks for the excellent program! Besides the broken buttons on the Realtime page (javascript?), my team thinks the font color has changed and is wanting to have only active queues shown on the Realtime page as default.
I did not see anything to change colors or only show active queues on the Realtime page. Is there any way to change these? Are all the configuration options documented anywhere or is everything in the configuration.properties file?
Thank you,
Scooby2
-
Replying to myself...
I showed them how to change the yellow/red alerts in the queue configuration so that made them happy. Now if there was a way to default the Realtime page to just show active queues, I would be a happy camper.
Thanks!
-
and again..
In console when trying to click on buttons in the Realtime page I get the following two errors over and over:
Warning: Error in parsing value for property 'cursor'. Declaration dropped.
Source File: http://10.3.2.43:8080/queuemetrics/img/video.css
Line: 74
Warning: Error in parsing value for property 'cursor'. Declaration dropped.
Source File: http://10.3.2.43:8080/queuemetrics/img/video.css
Line: 259
-
Replying to myself...
I showed them how to change the yellow/red alerts in the queue configuration so that made them happy. Now if there was a way to default the Realtime page to just show active queues, I would be a happy camper.
Thanks!
This can be set from the property:
realtime.all_subqueues=false
-
and again..
In console when trying to click on buttons in the Realtime page I get the following two errors over and over:
Warning: Error in parsing value for property 'cursor'. Declaration dropped.
Source File: http://10.3.2.43:8080/queuemetrics/img/video.css
Line: 74
Warning: Error in parsing value for property 'cursor'. Declaration dropped.
Source File: http://10.3.2.43:8080/queuemetrics/img/video.css
Line: 259
Which browser are you using? we test on IE 6/7, Firefox, opera 8 and 9. And I've never seen that error. ;)
-
Which browser are you using? we test on IE 6/7, Firefox, opera 8 and 9. And I've never seen that error. ;)
This is from Firefox 3.0.1 on Mac.
-
I thought all Firefoxes would be alike but maybe I'm wrong. :'(
We filed this as bug #432 and we'll notify you here on the board when it's fixed.
-
I thought all Firefoxes would be alike but maybe I'm wrong. :'(
We filed this as bug #432 and we'll notify you here on the board when it's fixed.
I confirm the bug was fixed in the CSV and will be released with 1.5.0.