Hey,
When using a 1 second refresh rate and hovering over an entry in the history list 'the background lights up'.
Everytime the UI refreshes 'the background dims down' again AND does not respond to clicks for a small period of time.
This happens as well with higher refresh rates, just less frequent.
Please fix it
Greets,
n2k
History and refresh rate
Forum rules
Help us help you:
Help us help you:
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
History and refresh rate
Last edited by n2k on March 31st, 2011, 2:50 am, edited 1 time in total.
Re: History and refresh rate
Don't use 1 second, it's just too fast.
By the time this is the highest priority problem, we'll fix it
By the time this is the highest priority problem, we'll fix it
Re: History and refresh rate
I use 1 second to get the feel of working with 'a real program'. I'm used to seeing things happen on screen when things are being done.
Now I'm not saying SABnzbd+ is not a real program, but I hope you get what I mean.
This doesn't happen in the queue, because when you hover over an entry in the queue the refresh rate seems to be 'on hold' until you hover out again.
Thanks for the reply
Now I'm not saying SABnzbd+ is not a real program, but I hope you get what I mean.
This doesn't happen in the queue, because when you hover over an entry in the queue the refresh rate seems to be 'on hold' until you hover out again.
Thanks for the reply
Re: History and refresh rate
OK, it's not that we're unwilling to fix issues,
it's just a question of priorities.
It will be fixed eventually.
The difference between the queue and history does show that it's solvable.
About the 1 second remark.
The price to pay for a Web UI is that it's more expensive (in performance) to keep a tight sync with the app.
It's a compromise.
it's just a question of priorities.
It will be fixed eventually.
The difference between the queue and history does show that it's solvable.
About the 1 second remark.
The price to pay for a Web UI is that it's more expensive (in performance) to keep a tight sync with the app.
It's a compromise.
Re: History and refresh rate
Last edited by war59312 on April 4th, 2011, 11:26 pm, edited 1 time in total.