Re: LC Date Conversions post 2035

[Mark Clark via use-livecode]

Thanks for the quick responses. In this case I did indeed use a 4 digit year as 
initial input (always), but still managed to shoot myself with a second 
conversion step. 

Converted my nicely formed input text to dateitems -- all good. Did my addition 
for renewal days to item 3. Check. Then I converted that back to date. Uh oh, 
not check. Should have been long date.

If we had it to do all over again I'd say let's make the function date always 
be the full year and only using the form short date would get you the two digit 
year. Long date would remain unchanged.

Or, ya know, I could just pay better attention! ;)

Mark

 



On Nov 7, 2022, at 3:43 AM, J. Landman Gay via use-livecode 
mailto:use-livecode@lists.runrev.com>> wrote:

That's the centuryCutoff in action, but I think something is amiss since it's 
only supposed to apply to 2-digit years and you supply a 4-digit year.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: LC Date Conversions post 2035

[Martin Koob via use-livecode]

Hi

This thread reminded me of some sci-fi show show I was watching which 
referenced the collapse of society on earth caused by a bug around 2035 or 
something like that where the computers could not process dates beyond that.   
I thought this is just a off hand reference to something Y2K. 

But I did a quick search turned up this:

https://en.wikipedia.org/wiki/Year_2038_problem

So a signed 32 bit number counting the seconds since Jan 1, 1970 will overflow 
after 03:14:07 UTC  
on 19 January 2038.

So if it was in referencing  that date and time in 2038 that your problem 
showed up then maybe that was the cause.  But that would not explain it if the 
date things started going wrong was in 2035.

But it appears from the tests that Andreas did on Windows 10 and MacOS 12.6 
that they have already resolved the Year 2038 problem.

Maybe the MacOS is using a 64 bit number now for the Unix time.  According to 
wikipedia

"though many modern systems have been upgraded to measure Unix time with signed 
64-bit  integers which will not 
overflow for 292 billion years.”

Not sure what Window is doing that it is only going to work till 3000.  Maybe 
MicroSoft have decided to EOL Windows  then and have plans to release a totally 
rewritten operating system then.


Martin


> On Nov 7, 2022, at 2:49 AM, Andreas Bergendal via use-livecode 
>  wrote:
> 
> But how far does the 4-digit conversion work? Here’s what I’ve found:
> - On Windows 10, it works until year 3000, and stops working on year 3001 (it 
> just returns the input without converting).
> - On MacOS 12.6 it works at least until year 2.100.000.000 (which is a 
> Sunday… :). By that time we should be expecting LC v14 or something, or maybe 
> that LC rules the galaxy, so I hope that’s sorted by then… :D

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: LC Date Conversions post 2035

[Paul Dupuis via use-livecode]

The results on Windows may also depend upon whether you built a 32 bit 
standalone or a 64 bit standalone? Or using the 32 or 64 bit version of 
whatever release of Livecode is being used.


On 11/7/2022 9:55 AM, Martin Koob via use-livecode wrote:

Hi

This thread reminded me of some sci-fi show show I was watching which 
referenced the collapse of society on earth caused by a bug around 2035 or 
something like that where the computers could not process dates beyond that.   
I thought this is just a off hand reference to something Y2K.

But I did a quick search turned up this:

https://en.wikipedia.org/wiki/Year_2038_problem

So a signed 32 bit number counting the seconds since Jan 1, 1970 will overflow after 
03:14:07 UTC  on 19 
January 2038.

So if it was in referencing  that date and time in 2038 that your problem 
showed up then maybe that was the cause.  But that would not explain it if the 
date things started going wrong was in 2035.

But it appears from the tests that Andreas did on Windows 10 and MacOS 12.6 
that they have already resolved the Year 2038 problem.

Maybe the MacOS is using a 64 bit number now for the Unix time.  According to 
wikipedia

"though many modern systems have been upgraded to measure Unix time with signed 
64-bit  integers which will not 
overflow for 292 billion years.”

Not sure what Window is doing that it is only going to work till 3000.  Maybe 
MicroSoft have decided to EOL Windows  then and have plans to release a totally 
rewritten operating system then.


Martin



On Nov 7, 2022, at 2:49 AM, Andreas Bergendal via use-livecode 
 wrote:

But how far does the 4-digit conversion work? Here’s what I’ve found:
- On Windows 10, it works until year 3000, and stops working on year 3001 (it 
just returns the input without converting).
- On MacOS 12.6 it works at least until year 2.100.000.000 (which is a Sunday… 
:). By that time we should be expecting LC v14 or something, or maybe that LC 
rules the galaxy, so I hope that’s sorted by then… :D

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

RE: LC Date Conversions post 2035 [OT ish]

[Ralph DiMola via use-livecode]

Interesting... On my Outlook the received date is used to sort emails but on
my phone the "date" field in the header is used for both sorting and
displaying in the list. So on my phone this email will be at the top until
31 Dec 2034.

This just reinforces that the interpretation of internet mail headers is
still not consistent. (and maybe should have had a little more thought
before the barn doors were opened)
 
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Mark Clark via use-livecode
Sent: Sunday, December 31, 2034 9:25 PM
To: How to use LiveCode
Cc: Mark Clark
Subject: LC Date Conversions post 2035

I was testing one of the tools I use to handle licensing today and decided
to run the series through a few iterations adding 2 years at a time. I
noticed that my dates were reverting to the 20th c. Hmm, whoops.

After a bit of head scratching I decided it wasn't just my doing.

Date conversion sort of works but the output can lead to trouble in the
future. I've done a few tests and some lengthy, but if anyone cares to
perform the "short test," please do.

Change your date to 12/31/2034; then change to 2035. 



run this:  

put the date into test
convert test to dateitems

answer item 1 of test --works in 2034; broken in 2035


Mark



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

ENTER in scripts

[Klaus major-k via use-livecode]

Hi friends,

is it only me or does the ENTER key nothing after hitting while in script 
editor?
Means precompile script resp. compile and close script editor window.

Works fine in LC 10 dp 4 but not in LC 9.6.9 RC 2!?


Best

Klaus
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ENTER in scripts

[Niggemann, Bernd via use-livecode]

Klaus wrote


is it only me or does the ENTER key nothing after hitting while in script
editor?



https://quality.livecode.com/show_bug.cgi?id=23999

Please note: in 9.6.9 rc 2 there is some more scriptifying of IDE stacks. Some 
of them have some quirks.
It is well worth to test 9.6.2 rc 2 to catch as many as possible and report 
them.

Kind regards
Bernd
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ENTER in scripts

[Klaus major-k via use-livecode]

Hi Bernd,

> Am 07.11.2022 um 18:45 schrieb Niggemann, Bernd via use-livecode 
> :
> 
> Klaus wrote
> is it only me or does the ENTER key nothing after hitting while in script
> editor?
> https://quality.livecode.com/show_bug.cgi?id=23999
> Please note: in 9.6.9 rc 2 there is some more scriptifying of IDE stacks. 
> Some of them have some quirks.
> It is well worth to test 9.6.2 rc 2 to catch as many as possible and report 
> them.

OK, thank you for confirming and reporting this issue!

> Kind regards
> Bernd

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ENTER in scripts

[Martin Koob via use-livecode]

Do you mean does pressing the ENTER key does the same thing as clicking the 
‘Apply’ button at the top left of the script editor?

The tool tip for the ‘APPLY’ button says.

‘compile and apply the current script (Enter, cmd+Return)’

I actually did not know there was a keyboard shortcut for the ‘Apply’ button.  
That is a handy tip.

I tried it out and at first it did not work.  That time the focus was on the 
script field and the text cursor was there. 

If I clicked on part of the card outside of the script field then the 
cmd+Return key combination worked.

If I clicked in another object like the ‘find’ text field or a handler in the 
list to the left of the text field or on the ‘MatchCase’ checkbox CMD+Return 
would not work.

So it looks like it only works when there is no focus on a field or other 
object.


In any case it sounds like a bug.   The key combination should work whether the 
script field has focus or not.


Since I have never used that key combo before I am not sure whether that 
behaviour has changed or not.


Martin Koob


> On Nov 7, 2022, at 12:45 PM, Niggemann, Bernd via use-livecode 
>  wrote:
> 
> Klaus wrote
> 
> 
> is it only me or does the ENTER key nothing after hitting while in script
> editor?
> 
> 
> 
> https://quality.livecode.com/show_bug.cgi?id=23999
> 
> Please note: in 9.6.9 rc 2 there is some more scriptifying of IDE stacks. 
> Some of them have some quirks.
> It is well worth to test 9.6.2 rc 2 to catch as many as possible and report 
> them.
> 
> Kind regards
> Bernd
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ENTER in scripts

[Craig Newman via use-livecode]

All.

"Enter" has always worked for me. And focus has always been required to be in 
the SE for it to do so.

This seems logical to me. It would not do for actions specific to certain 
spaces to be affected, or effected, when not in that space.

Craig

> On Nov 7, 2022, at 1:07 PM, Martin Koob via use-livecode 
>  wrote:
> 
> Do you mean does pressing the ENTER key does the same thing as clicking the 
> ‘Apply’ button at the top left of the script editor?
> 
> The tool tip for the ‘APPLY’ button says.
> 
>   ‘compile and apply the current script (Enter, cmd+Return)’
> 
> I actually did not know there was a keyboard shortcut for the ‘Apply’ button. 
>  That is a handy tip.
> 
> I tried it out and at first it did not work.  That time the focus was on the 
> script field and the text cursor was there. 
> 
> If I clicked on part of the card outside of the script field then the 
> cmd+Return key combination worked.
> 
> If I clicked in another object like the ‘find’ text field or a handler in the 
> list to the left of the text field or on the ‘MatchCase’ checkbox   
> CMD+Return would not work.
> 
> So it looks like it only works when there is no focus on a field or other 
> object.
> 
> 
> In any case it sounds like a bug.   The key combination should work whether 
> the script field has focus or not.
> 
> 
> Since I have never used that key combo before I am not sure whether that 
> behaviour has changed or not.
> 
> 
> Martin Koob
> 
> 
>> On Nov 7, 2022, at 12:45 PM, Niggemann, Bernd via use-livecode 
>>  wrote:
>> 
>> Klaus wrote
>> 
>> 
>> is it only me or does the ENTER key nothing after hitting while in script
>> editor?
>> 
>> 
>> 
>> https://quality.livecode.com/show_bug.cgi?id=23999
>> 
>> Please note: in 9.6.9 rc 2 there is some more scriptifying of IDE stacks. 
>> Some of them have some quirks.
>> It is well worth to test 9.6.2 rc 2 to catch as many as possible and report 
>> them.
>> 
>> Kind regards
>> Bernd
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

RE: ENTER in scripts

[Ralph DiMola via use-livecode]

Well, you learn something exceedingly simple every day. OK I get it. Enter is 
the same as clicking "Apply". Very convenient! Saves time typing in the SE.

THANKS!


Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of 
Craig Newman via use-livecode
Sent: Monday, November 07, 2022 2:08 PM
To: How to use LiveCode
Cc: Craig Newman
Subject: Re: ENTER in scripts

All.

"Enter" has always worked for me. And focus has always been required to be in 
the SE for it to do so.

This seems logical to me. It would not do for actions specific to certain 
spaces to be affected, or effected, when not in that space.

Craig

> On Nov 7, 2022, at 1:07 PM, Martin Koob via use-livecode 
>  wrote:
> 
> Do you mean does pressing the ENTER key does the same thing as clicking the 
> ‘Apply’ button at the top left of the script editor?
> 
> The tool tip for the ‘APPLY’ button says.
> 
>   ‘compile and apply the current script (Enter, cmd+Return)’
> 
> I actually did not know there was a keyboard shortcut for the ‘Apply’ button. 
>  That is a handy tip.
> 
> I tried it out and at first it did not work.  That time the focus was on the 
> script field and the text cursor was there. 
> 
> If I clicked on part of the card outside of the script field then the 
> cmd+Return key combination worked.
> 
> If I clicked in another object like the ‘find’ text field or a handler in the 
> list to the left of the text field or on the ‘MatchCase’ checkbox   
> CMD+Return would not work.
> 
> So it looks like it only works when there is no focus on a field or other 
> object.
> 
> 
> In any case it sounds like a bug.   The key combination should work whether 
> the script field has focus or not.
> 
> 
> Since I have never used that key combo before I am not sure whether that 
> behaviour has changed or not.
> 
> 
> Martin Koob
> 
> 
>> On Nov 7, 2022, at 12:45 PM, Niggemann, Bernd via use-livecode 
>>  wrote:
>> 
>> Klaus wrote
>> 
>> 
>> is it only me or does the ENTER key nothing after hitting while in 
>> script editor?
>> 
>> 
>> 
>> https://quality.livecode.com/show_bug.cgi?id=23999
>> 
>> Please note: in 9.6.9 rc 2 there is some more scriptifying of IDE stacks. 
>> Some of them have some quirks.
>> It is well worth to test 9.6.2 rc 2 to catch as many as possible and report 
>> them.
>> 
>> Kind regards
>> Bernd
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Not LC-related, but this will give old-timers a blast of nostalgia

[Geoff Canyon via use-livecode]

https://beyondloom.com/decker/tour.html

Interestingly, it works almost identically native and on web. You literally
save with an .html extension and it's web-able.

The language is *not* HyperTalk.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode