AOS & LOS proper usage question

[rbureau85]

Hello again,
The documentation for AOS and LOS says you can use the military time designations. I have tried using "D", "d", "Delta" etc but none of those work. They don't appear to work in the storybook either. Can you assist on what I am missing?

Thanks
Renee, SSC

[markacianfrani]

Hey Renee,

The timezone property doesn't currently affect the AOS/LOS timestamps. I think our (wrong) assumption was that these would already be formatted to your particular timezone, either from your data source or in your client code since you're passing them in directly.

We'll go ahead and add this as a new feature now though. I'll follow up here as soon as that's released.

[markacianfrani]

Sorry, I was totally wrong here. Timezone does affect timestamps, but it looks like there's a bug when you dynamically change the timezone. https://codesandbox.io/s/infallible-cache-igvsx?file=/src/App.js

Hotfix incoming! Are you changing the timezone after render?

[rbureau85]

That might be a setting options we incorporate later on but right now we are just looking to track a few time zones in the header. I tried using 2 RuxClocks but that looks like a mess and does not fit in the header without css :root adjustments

[rbureau85]

Mark, So I am trying to get AOS and LOS to be 2 different timestamps based on the timezone of the RuxClock. Like behind 4 hours or ahead 6 hours to track different time zones. I have not been able to get the AOS or LOS to display anything useful. Even the canvas doesn't seem to be working based on the documentation. Example: Clock is on MST (mountain time) AOS = Dubi time LOS = Hawaii time Based on the documentation I thought passing in the military time letter would adjust the aos/los but it shows nothing or 00:00:00. Thanks! Renee

…

On Mon, Nov 29, 2021 at 12:44 PM Mark Anthony Cianfrani < ***@***.***> wrote: Sorry, I was totally wrong here. Timezone does affect timestamps, but it looks like there's a bug when you dynamically change the timezone. https://codesandbox.io/s/infallible-cache-igvsx?file=/src/App.js Hotfix incoming! Are you changing the timezone after render? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#131 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFUROBALOLXW4ZFI5JTRYXDUOPJZDANCNFSM5I3IZZKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[markacianfrani]

Gotcha! Are you able to share a snippet of your Clock implementation? Or just the values you're passing in?

[rbureau85]

Looks like the AOS is stuck on the top of the hour too. It did not include the minutes passed in to move ahead 4 hrs. I think there are more bugs in here than I originally thought :-(

[markacianfrani]

Ahh okay, so the AOS/LOS properties are meant to be static timestamps. It sounds like what you want are actually three separate Clocks. Something like https://codesandbox.io/s/agitated-panka-9nu07?file=/src/App.js ?

[rbureau85]

The "D" is still throwing and error so the military string props

Why are they static? What was the original purpose?

Yes, I was going to use 3 different clocks but they take up a lot of space and having the AOS/LOS as other time zones shows connection between that main clock and the other needed zones. I would recommend that be a feature. As you know tracking of multiple time zones is a big thing in mission.

thanks for your time in explaining.

[markacianfrani]

AOS (Acquisition of Signal) and LOS (Loss of Signal) are usage specific and represent the specific times a signal was received and lost from a satellite.

As for the spacing issue, you can control the margin of each clock (I updated the example above to show that) so essentially it can take up the same amount of space as using AOS/LOS would. We're currently working on design tokens that would give you consistent spacing variables for scenarios like this, but we will definitely bring this up internally and iterate on it.

That invalid time error will be fixed shortly in a patch

[rbureau85]

Excellent, Thank you for the clarification. I definitely had it wrong in my
head.

[rbureau85]

Ahh okay, so the AOS/LOS properties are meant to be static timestamps. It sounds like what you want are actually three separate Clocks. Something like https://codesandbox.io/s/agitated-panka-9nu07?file=/src/App.js ?

Current answer to this question is use 3 different clocks and know that AOS/LOS are static and after some digging in the source code require a string of something like 1995-12-17T03:24:00. The date part needs to be there but is irreverent to what is displayed. Your hour and mins will be displayed as what you pass in not difference from timezone selected.

[markacianfrani]

Just to close the loop here, we just released 6.0.4 which should fix that console error you were getting