安裝 Steam
登入
|
語言
簡體中文
日本語（日文）
한국어（韓文）
ไทย（泰文）
Български（保加利亞文）
Čeština（捷克文）
Dansk（丹麥文）
Deutsch（德文）
English（英文）
Español - España（西班牙文 - 西班牙）
Español - Latinoamérica（西班牙文 - 拉丁美洲）
Ελληνικά（希臘文）
Français（法文）
Italiano（義大利文）
Bahasa Indonesia（印尼語）
Magyar（匈牙利文）
Nederlands（荷蘭文）
Norsk（挪威文）
Polski（波蘭文）
Português（葡萄牙文 - 葡萄牙）
Português - Brasil（葡萄牙文 - 巴西）
Română（羅馬尼亞文）
Русский（俄文）
Suomi（芬蘭文）
Svenska（瑞典文）
Türkçe（土耳其文）
tiếng Việt（越南文）
Українська（烏克蘭文）
回報翻譯問題
3 
檢舉此篇文章
Another possibility is that I have some bug processing the settings causing the code to stop starting. I have had that one before in another wallpaper.
Will be asking Bio this week to be sure of how it should be because if true that would mean I would have to update a lot more than just this wallpaper. Will also update this wallpaper in the coming days.
the issue with window.onload is true, but I don't think it's currently the prevalent cause. While I'm actually waiting for a 'load ended' event in C++ before sending any properties too, it is different from window.onload, so the order of things still isn't guaranteed. So it's best to just set up the listener object right away. (My understanding is that window.onload will also wait for all dependencies while the C++ callback won't.)
Since the last time I updated Chromium I noticed this happening even more often than before when switching between two web wallpapers quickly. It seems the callbacks I'm waiting for don't allow me to check whether they belong to the last page I loaded, so the properties never reach the most recently selected web wallpaper. I think I already have a work around for that issue though.
Thanks for the feedback .. will update all my wallpapers to start different and not wait for window.onload.
That's because ultio is a friend of mine
Thanks, I'll check it out when it's updated. Perhaps the issue is fully gone then. The changes I have on my end seem to almost fix the problem so far.
If there are any other issues, just let me know ..