Wallpaper Engine:壁纸引擎

Wallpaper Engine:壁纸引擎

1,131 个评价
Circular Calendar 2.0
   
奖励
收藏
已收藏
取消收藏
Type: Web
Age Rating: Everyone
Genre: Technology
Resolution: Dynamic resolution
Category: Wallpaper
文件大小
发表于
4.324 MB
2017 年 6 月 1 日 上午 3:04
1 项改动说明 ( 查看 )

订阅以下载
Circular Calendar 2.0

描述
A simplistic clock-calendar combo inspired by ToshimonsterRealm, based on Matt Juggins' clock-calendar combo over at codepen.io/mattjuggins/pen/WGRRYx.

I just made the full port to WE, added a couple of customisation presets and a customisable background. Go to your steam directory/steamapps/workshop/431960/937252521 to find the full instructions in the README file.

An updated version is at psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=956565408
26 条留言
今晚CT不在家 2022 年 2 月 6 日 上午 5:21 
Sorry, emm, but I would say that now I wonder why the Wallpaper platform scales up by 75% when applying the wallpaper now to make it look bigger

emm,抱歉,但我想说现在不知道为什么Wallpaper平台现在应用该壁纸的时候会缩放75%的样子,让它看起来更大了
Babel  [作者] 2018 年 1 月 12 日 上午 6:19 
@Mister Roboto Currently it's set up in pixels, so it won't scale to 4k. If I make a v3 one of the things I've got planned is dynamic resizing and positioning anyway!
Babel  [作者] 2018 年 1 月 12 日 上午 6:17 
@冷若冰霜 that's a little beyond what I know how to do with electron (the webpage framework WE uses). Just use something other than WE to display a widget over the top...
Mister Roboto 2018 年 1 月 6 日 上午 11:28 
Would be great to change the size, I've got a 4k screen and it looks tiny
Shirft 2017 年 8 月 24 日 下午 8:28 
Wish could add NET SPEED display:steamsalty:
Rikachyan 2017 年 8 月 17 日 下午 7:03 
Other than "clock", nothings can be refreshed normally. sad :steambored:
绝不吃螺蛳粉 2017 年 7 月 30 日 下午 6:55 
“Hey, buddy, is my screen dirty?”
“Fool, that's wallpaper”
云海星 2017 年 7 月 29 日 上午 1:25 
@StoryStratos oh i see, thanks for your anwser, i was so busy that i cant see your message
sorry , now ,i need enjoy this!
Ricochet 2017 年 7 月 22 日 上午 8:25 
Many thanks,man. This is what i need.
Babel  [作者] 2017 年 7 月 16 日 上午 1:59 
@Flabbergaster That's the intention, though that'll probably be a 3.0 update, since I'll have to redo the port backend