cisaak wrote: > Started using 5.9.16. Generally back to normal except for the much > noted switch from prediction to observed. In my case, the high/low > temperature (%f) switches from a prediction to observed and the > precipitation probability (%x) switches from a prediction to a blank. > Like all of us, I hope this can be fixed. > > Two other nits. In my script I use %y to state each period. %y > generates Tonight in upper and lower case and TOMORROW in caps. Any way > to make consistent? Also, %x generates "PRECIP 20%" or "RAIN 10%" (all > caps) while most of the rest of the criteria generate upper and lower > case results (e.g., High 77% or Partly Cloudy). Once again, any way to > make consistent? Of course I want to be consistent. In this case it sounds like you're using Custom Clock on a Touch as non-touch players automatically show in all caps when presenting. Custom Clock pulls raw data from SDT via API so it's grabbing inconsistently stored data. I can easily make them all consistent so that Custom Clock gets them that way. What is desired- "Rain" vs "RAIN" I assume?
Thanks -Greg ------------------------------------------------------------------------ GoCubs's Profile: http://forums.slimdevices.com/member.php?userid=312 View this thread: http://forums.slimdevices.com/showthread.php?t=14327 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
