A screenshot of my primary display.
Wallpaper not included. Source: http://wallpoper.com/images/00/29/00/37/snow-forest_00290037.jpg
[ Direct Link ]
Synkro³ has been updated!
Well, thanks for the feedback. I'm glad you liked it :)Mordasius wrote:This is a neat looking set of skins and you might like to consider the following when finalising them:
Sure, I didn't really know you could do that. I'll edit it right awayMordasius wrote:1) AccurateText=1 and TransitionUpdate=10 both belong in the [Rainmeter] section rather than in the meters.
Not sure why I did that... lolMordasius wrote:2) Rather than putting Update=1000000000 in the [Rainmeter] section of the Synkro³ and background skins you can just put Update=-1 in the [Background] and [Synkro³] meters.
I found the time often desyncing with Update=1000. The music player update was probably by mistake. I'll test them out again at 1000 and see what happens.Mordasius wrote:3) I'm not sure why you need Update=100 in the [Rainmeter] sections of the Music Player and Time skins.
Mordasius wrote:4) I'd be tempted to have [Measure.Time.Hours.Main] reporting the users time wherever they are by not including the line TimeZone=0.
with update = 1000 the meter will be at most 999 ms out of sync, e.g. the player is at 2:00 and the meter updates to 2:00 and then right after the player updates to 2:01. with an update of 100 it'll be at most 99 ms out of sync, but at a cost of ~10x the computing timeosuka_ wrote: I found the time often desyncing with Update=1000. The music player update was probably by mistake. I'll test them out again at 1000 and see what happens.
moshi wrote:there are many Rainmeter skins that aren't really useful, so let's add another one.
jsmorley wrote:I have good news and bad news.
First the bad news. [...] We would be happy to have this happen and would love to work with anyone who is feeling ambitious.
Now the good news.
I lied, there isn't any good news...
Well, yeah. That was... quite obvious, but thanks for the helpful answer anyways!Bekarfel wrote:with update = 1000 the meter will be at most 999 ms out of sync, e.g. the player is at 2:00 and the meter updates to 2:00 and then right after the player updates to 2:01. with an update of 100 it'll be at most 99 ms out of sync, but at a cost of ~10x the computing time