TheShanMan wrote: > It's pretty hard to figure out the maximum shift, and if you pick too > large a value the display will "stick" to the left or right side for a > while before reversing direction. It makes it even harder if the time > format doesn't include seconds because it only moves once per minute > instead of once per second.
Yeah, I wish that were better, too. It likely won't improve because 1) I haven't found time to code Squeezebox stuff for years now and 2) I don't use FuzzyTime much myself for the FuzzyTime screensaver. Most of my devices are SB2/SB3 and I use a version of SuperDateTime that I've customized to use FuzzyTime APIs to move everything around (even less often -- only moves the bitmaps when it refreshes the weather data). SDT makes it even harder to figure out the max shift as it has separately positioned text and bitmapped icons -- so making FT's screensaver max shift logic better wouldn't help my usage, and might actually complicate the APIs used by my custom SDT. But FT is licensed under the GPL, so anyone who'd like to is welcome to take the code & tweak it. I hope that's not cold comfort. :-( ------------------------------------------------------------------------ peterw's Profile: http://forums.slimdevices.com/member.php?userid=2107 View this thread: http://forums.slimdevices.com/showthread.php?t=98470 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
