peterworks
Ye Olde Bowler
All fixed for me too - thanks
Schedule fixed, Thx
Not seeing any problems with formatting
humax# diff -u /mod/webif/lib/pretty_size~ /mod/webif/lib/pretty_size
--- /mod/webif/lib/pretty_size~
+++ /mod/webif/lib//pretty_size
@@ -3,7 +3,7 @@
proc pretty_size {size} {
set units {bytes KiB MiB GiB TiB}
- for {set i 0} {$size > 1023} {incr i} {
+ for {set i 0} {$size > 1023 && $i < [llength $units] - 1} {incr i} {
set size $($size / 1024.0)
}
I've uploaded version 1.0.17 of the web interface package. Here is a list of the changes since version 1.0.16. See http://wiki.hummy.tv/wiki/Webif_release_notes for the full change history.
1.0.17 (07/10/2014)
- Fix for scheduling series which span channels (based on work by, and patch from, prpr);
- Fix schedule backup and restore for series which span channels;
- Fix scheduling of events with % in their name;
- Fix folder creation from schedule list;
- Support changing folder for pending recording;
- Fix width of toggle switches on settings page;
- Add option to reset dedup in order to run it again on a folder;
- Check connectivity to repository using ping in order to provide better error messages;
- Fix display of certain network names on channel diagnostic page (patch from prpr).
Clearing cache worked!Now there is a big pie chart showing disc capacity in the the middle of the we if screen blocking access?
It was like that for me in Firefox till I cleared the browser cache.
humax /mnt/hd2/mod/webif/lib # diff plugin~ plugin
--- plugin~
+++ plugin
@@ -1,6 +1,6 @@
proc eval_plugins {hook} {
- foreach plugin [glob -nocomplain /mod/webif/plugin/*] {
+ foreach plugin [lsort [glob -nocomplain /mod/webif/plugin/*]] {
if {[file isfile "$plugin/$hook.hook"]} {
catch {uplevel source "$plugin/$hook.hook"}
}
Aye.( Don't you just hate it when someone writes "my bad").
That's an artefact of the capture. It was a hand when I captured it, but it turned into a pointer in the capture buffer. I agree it's potentially confusing but I don't know what to do about it.From your screenshot I 'd assumed that you had both status bars on all of the time (because your pointer was an arrow, not a hand, indicating mouse-over was not active).