Data for rocket launches gives bad times in Eastern Hemisphere (positive UTC time zones)

[shaktishekhar]

Data for next 5 rocket launch seems to giving error regex needs to update with latest json response "https://fdo.rocketlaunch.live/json/launches/next/5" as its showing error Webparser Overloaded restart rain meter also it seems that there is time issue as its not picking up any launch time also count down seems not working

[mpurses]

Sorry for the late reply.

Usually I show the "Restart Rainmeter" error based on getting a bad time (that's not null) for the next upcoming launch. Which I usually get when Rainmeter's webparser is overloaded and no data is downloaded. It can happen often since the World Map has a lot of webparsing things. I've put in various delays to try to minimize this from happening.

Anyways... It is weird that is shows up even though there is a date for the next launch.

I've made a bunch of changes in the mean time to correct errors/issues with getting Rocket Launch data. Could you download this updated version to see if this fixes any issues you have? (I had to put the rmskin file inside a zip file for github)

Sonder_21.X.0_Test.zip

• World Map: Night Shadow Color option
• World Map: Fix Rocket Launches not updating automatically and add estimated dates instead of TBD if available.
• Date: StringStyle Setting, Seperate Font Setting from Time skin.
• Weather: Remove unnessesary refresh at sunrise/set, auto-location bug fixes, slightly faster animations.
• Add Taiwanese language; Fix German, Slovak, Portuguese.
• Update default layout to have more consistent theme with 'small' system variations.
• Other bug fixes and log error cleanup.

[shaktishekhar]

both the information is still wrong kindly have a look

[mpurses]

Could you take some screenshots of the measures in the Rainmeter Log > Skins Tab > under "Sonder/Space". As well as make sure there are no errors showing up in the log as well. I feel like something is happening when trying to convert/subtract your time zone or system time possibly.

[shaktishekhar]

https://drive.google.com/file/d/11re-MqjREEzTJJeI0BG21KDLv8bt2qj7/view

check this video

[mpurses]

Alright, I think I found the problem, Windows doesn't like the Eastern Hemisphere for whatever reason.. Changed from reading the registry to comparing the Local/UTC Times:

Could you download/replace this file: https://raw.githubusercontent.com/mpurses/Sonder/master/Skins/Sonder/Space/WorldMapMeasures.inc

[shaktishekhar]

i think readings are fine now iss also

but I have a question when I place widget to taskbar the context menu doesn't detect taskbar edge and content goes behind taskbar unlike windows content menu it detects edge and inverts the menu when there is no space at the bottom kindly check screenshot like this looks fine it goes on top issue is here rocket launches list goes behind taskbar can it be fixed

[shaktishekhar]

[mpurses]

Thanks for testing that out.

I don't use the windows context menu for the Rocket Launches, so it's in a fixed location. I'll try to add an option to move it's location up (or something) in the next version. In the mean time you can shift it up a little by changing the Y under [RocketLaunchBackground] in the skin ini file to something like this:

Also try out TaskbarX if you want a transparent taskbar: https://chrisandriessen.nl/taskbarx

One last question for you, are there any translation errors in the skin/settings when using the Hindi language in the settings (assuming you speak it..)? It's kind of halfway translated right now.

[shaktishekhar]

"[RocketLaunchBackground] " is helpful I'll adjust it accordingly and about translation in Hindi it seems all good no spelling error am not so good in Hindi as I speak Hindi but in theory am not so good but I asked my mom she said its all good I think u used google translation one suggestion some words in India is adapted in Hinglish for example now days no one even knows what is even villagers knows calender so you better use like this https://indiatyping.com/index.php/translations/english-to-hindi-translation

[shaktishekhar]

as you can see on the top side its going offset and getting cropped as going off frame how to increase frame size @ top as it float @ bottom

[mpurses]

Gotcha, thanks for your help.

And for moving the rocket launches higher, there really isnt a good way around it right now with how Rainmeter works, you will have to shift every Meter down to compensate for it, and with how many meters/calculations there are it will be a mess getting it to go higher. I'll try to think through a new layout/option for the next version in the mean time.

[shaktishekhar]

found new issue today, i think we need text wrapping its gng off body @mpurses

[mpurses]

Ya that's an issue I wasn't sure if I wanted to fix yet, I can't wrap as that throws off my formatting. So I have to just cut of excess. I might fix (cut) in the next version.

[shaktishekhar]

Ya that's an issue I wasn't sure if I wanted to fix yet, I can't wrap as that throws off my formatting. So I have to just cut of excess. I might fix (cut) in the next version.

ok am trying to find my self how to trim json response or how to use trim function of native rainmeter anyways thnx :-)

[mpurses]

You can add a regex substitute like: "^(.{32}).+$":"\1..." this trims the string if over 32 characters...

[shaktishekhar]

Worked like charm thank you soo much buddy :-)

[mpurses]

@shaktishekhar Could you test out this Pre-release, it should have everything fixed. (Found another bug where the times didn't update properly) And I want to make sure the upgrade goes well, it should preserve all your existing Variables (custom changes).

https://github.com/mpurses/Sonder/releases/tag/v21.6.0

[shaktishekhar]

it is going little bit out of frame

when i did its showing correct

i tested in vmware so that i can compare 1 to 1 i upgraded my current settings are intact everything seems fine when i upgrade except that rocket make background little wider or trim more char i think

Before update

After update

[mpurses]

Thanks for testing, The font I'm using isn't monospaced so 32 characters with a different location (string of characters) will have different lengths, so I'm just going to stick with 32 for now until I see more locations come through. I may adjust in a future update.