Apparently the longest date & time this century in Roman numerals is 23:38 on August 28th 2088 which is what it reads on the screenshot. (You can see I plan for the app to be running well into the future). My inspiration for the app icon was the time of day I built the first version for the AppStore.
Roman desk clock app icon
RomanClock-Icon-144x144.png (4.25 KiB) Viewed 42282 times
Wait.. you bought it? You did! Thanks guys… I wasn’t trying for sales here. I just wanted to share that there’s another LiveCode iOS App out there and show some screenshots and images.
As for your suggestion.. I suppose I could add a help page to explain roman numerals… or link to Wikipedia?
There’s an update coming soon. As Roman numerals don’t have zero, midnight displays as just a colon. Technically this is correct, but I’m adding a little logic to show “MEDIA NOX” (Midnight) for the midnight minute instead. Hope you like it. I’ll probably add the Roman Numerals help link or info at the same time.
I contributed too. It has a nice clean interface and I like the settings panel. I'd like to hear how easy/hard it was to get this onto the App Store.
-Mike
Hi Mike, it’s not too difficult to get on the AppStore. There’s a process to follow as with most things. I found that following the Livecode lesson helped immensely as long as you can navigate any UI changes in the Apple apps and version of Livecode used in the lesson. https://lessons.livecode.com/m/4069/l/3 ... -app-store
Just curious, how did you implement successive values of the time display? A look-up table that was read second by second? Or perhaps some predefined sequences that can be called as needed?
Just curious, how did you implement successive values of the time display? A look-up table that was read second by second? Or perhaps some predefined sequences that can be called as needed?
Craig
Hi Craig,
I use the send command to update the clock every minute.
E.g. send “updateClock” to me in 60 seconds
My updateClock command calculates which roman numerals to use and updates the display.
My updateClock command calculates which roman numerals to use
That is what I was wondering about. You cannot really "calculate" the required new display, no? So I thought you either had a large look-up table (tedious to build) or some sort of rules-based gadget that determines the next reading based on the previous: (Pseudo)
if char - 3 to -1 of tDisplay = "III" then put "IV" into char -3 to -1 of tDisplay
if char -2 to -1 of tDisplay = "IX" then put "X" into char -2 to -1 of tDisplay
...
Still works perfectly on MacOS ("but not verified for MacOS").
I hope you may consider uploading this to the Mac App Store as well (easier to update my Mac lol)
Still works perfectly on MacOS ("but not verified for MacOS").
I hope you may consider uploading this to the Mac App Store as well (easier to update my Mac lol)