Re: use-livecode Digest, Vol 212, Issue 13

[Keith Clarke via use-livecode]

I will do when I attempt to climb that new learning curve!
Best,
Keith 

> On 12 May 2021, at 06:17, Brian K. Duck via use-livecode 
>  wrote:
> 
> Can you share more about your standalone settings to make this happen?
> 
> Sent from my iPad,
> Brian
> 
>> On May 11, 2021, at 12:03 PM, use-livecode-requ...@lists.runrev.com wrote:
>> 
>> I’ll be glad when I finish the project and can deploy it to a standalone 
>> that run on a dedicated Raspberry pi without all the ?helpful? 
>> infrastructure! 
>> 
>> Thanks all for the help.
>> Best,
>> Keith
> 
> ___
> 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: use-livecode Digest, Vol 212, Issue 13

[Brian K. Duck via use-livecode]

Can you share more about your standalone settings to make this happen?

Sent from my iPad,
Brian

> On May 11, 2021, at 12:03 PM, use-livecode-requ...@lists.runrev.com wrote:
> 
> I’ll be glad when I finish the project and can deploy it to a standalone that 
> run on a dedicated Raspberry pi without all the ?helpful? infrastructure! 
> 
> Thanks all for the help.
> Best,
> Keith

___
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

Bug, feature, or just something I need to program around?

[Alex Tweedly via use-livecode]

In a LC single line field (MacOS), the keys shift-cmd-rightarrow will 
select from the current position to the end of the line, and add that to 
the selection.


BUT if I TAB into the field the cursor is initially at the start of the 
field and the key sequence above will move the cursor to the end 
*without* selecting the characters.


At that point, shift-cmd-leftarrow will move it back to the start, still 
without selecting any characters. But if you do "something else" (e.g. 
left arrow, insert a char, delete a char, ...) then normal behaviour 
resumes. If you click into the field, everything behaves itself.


Feels to me like a bug, but I'd be happy to be corrected.

And, if I need to - any suggestions how I could script around it ?

Thanks,

Alex.


___
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: Finding invisible/non printable characters in a string

[Curry Kenworthy via use-livecode]

David:

> I set out to learn some Livecode, but instead learned about Zalgo.

Patience, dear chap! :)

Indeed you learned a relevant fact about Zalgo, and also Hindi, to 
demonstrate the answer to your first assumption and first question:


> Would I be right in thinking if codepoint count > the number of chars
> in a text string, then it probably contains invisible characters?

I'll try to remember that for you, answering simply "No" might be 
preferable to "No, and here's the reason why, along with some proof."


(But I may still need to mention the reason for the benefit of others.)

> and that invisible characters have to go in the ‘maybe when I have
> some time’ drawer, with datagrids, arrays and regex.

I would have the same response ("negative") for this new assumption.
And if I ended it there, just "no" with no reason, it might be strange!

So here's why: this list still exists, you and I are here. Many people.
Answering your first question did not preclude answering your second.
I don't see any reason why we might not be able to squeeze that in

Once again, I'm following in Paul's accurate footsteps:

> I think the best way is to scan the codepoints looking for
> codePointToNum values that are 0-31 (exclude tab and cr/lfs
> if you like) and 127 (DEL). There may be some others in the
> 128-255 range that are not printable.

To build on that answer, usually I would aim to use regex. (Unless you 
know what type of text and which potential invisible chars you are 
expecting in your particular app; for 1 or 2 I'd use normal replace.)


More specifically, there are named Unicode categories implemented in 
regex. I would use those whenever possible. That way most of the hard 
work is already done for you, rather than painstakingly building up a 
list of possible chars and ranges from scratch for both ANSI and 
Unicode. But you should expect to tweak an expression for your purposes!


I'll stop there for now. Too much info, or not enough?

I have to admit that I love languages, scripts, formats, Unicode, and 
working with LC texts and fields! Always a fascinating subject. Thanks 
for bringing it up.


Back to work, take care everyone

Best wishes,

Curry Kenworthy

Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.com/

___
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: AppStore rejections

[J. Landman Gay via use-livecode]

And then they light them.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 11, 2021 9:55:09 AM Andrew at MidWest Coast Media via use-livecode 
 wrote:


This is a reminder that I need to bill clients more for each build 
submission as there are SO many hoops to jump through, and those hoops 
change shape and location at least once or twice a 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: LiveCode convert seconds to dateItems - year is out by 19?

[Keith Clarke via use-livecode]

According to the Dictionary "LiveCode uses midnight, January 1, 1970 as the 
start of the eon. Date and time functions are computed from that date.” This is 
the same as MacOs, according to fandom "The epoch of Mac OS X 
, macOS 
, and most Unix 
-based systems begins at midnight on 
January 1, 1970 ."

This got me thinking - that this project's files may be on my Mac but courtesy 
of our work Google Drive via Google FileStream. And according to the wires, 
FileStream does strange things with creation date on hosting systems. So, I 
moved the project folder structure from to my Mac’s Documents folder area 
(ironically, also backed up - this time to iCloud) and everything is working!

I’ll be glad when I finish the project and can deploy it to a standalone that 
run on a dedicated Raspberry pi without all the ‘helpful’ infrastructure! 

Thanks all for the help.
Best,
Keith 

> On 11 May 2021, at 14:58, Terence Heaford via use-livecode 
>  wrote:
> 
> Could it be something to do with the base date on the mac vs the base date of 
> live code?
> 
> I believe the base date on a mac is 1970, not sure what it is in live code?
> 
> Terry
> 
>> On 11 May 2021, at 13:59, Keith Clarke via use-livecode 
>>  wrote:
>> 
>> Thanks Martin & Alex,
>> 
>> I wasn’t aware of ‘the seconds’ - thanks that’s behaving correctly here. 
>> 
>> Tracing back from this date conversion being OK to the tCreateDate variable. 
>> This is item 4 of the long files, which according to the docs, should be 
>> Creation date, in seconds. 
>> 
>> Bypassing the conversion, this item is the same for all the files in my 
>> target folder (some created yesterday & some weeks ago). It has the value 
>> 2212122496, which LiveCode converts (reliably!) to 2040,2,6,6,28,16,2.
>> 
>> Printing out the long files for one of the files in the target folder shows… 
>> 
>> filename,2055,0,2212122496,1620675773,2212122496,0,501,20,600,ttxtTEXT
>> 
>> This same weird value is being returned for the Creation Date (item 4) & 
>> Last Access date (item 6), though the Last Modified Date (item 5) looks 
>> correct.
>> 
>> Any clues?   
>> Best,
>> Keith
>> 
>>> On 11 May 2021, at 13:09, Martin Koob via use-livecode 
>>>  wrote:
>>> 
>>> Hi Keith
>>> 
>>> I just tried the following
>>> 
>>> on mouseup
>>> 
>>> convert the seconds to dateitems
>>> 
>>> put it
>>> 
>>> end mouseup
>>> 
>>> The result is 2021,5,11,7,52,5,3  So that is correct.
>>> 
>>> Where is the value in your tCreateDate variable from.  Maybe there was a 
>>> miscalculation there.
>>> 
>>> Martin
>>> 
 On May 11, 2021, at 6:44 AM, Keith Clarke via use-livecode 
  wrote:
 
 Hi folks,
 What am I doing wrong with convert tCreateDate from seconds to dateItems… 
 
 I’m pulling the long files of files I created yesterday on a Mac and 
 attempting to convert the creation date. 
 
 Whatever date type I choose, LiveCode reckons yesterday was in the year 
 2040. Did I oversleep?
 Thanks
 Keith
 ___
 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

___
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

AppStore rejections

[Andrew at MidWest Coast Media via use-livecode]

My latest update to an on-going app (5 year old project) got rejected 6 times 
by Apple reviewers before lucky #7 satisfied their demands. I haven’t been 
rejected this much since high school! Lol
https://www.dropbox.com/s/en7xjkm354zv3pp/lukcy7.png?dl=1 


I’m excited that LC 9.6.3rc1 should be bringing us support for App Tracking 
Transparency as incorrect settings there were cited as part of my first 2 
rejections. I was never able to reproduce the other problem they were 
experiencing (which looked like network issues out of my control during their 
testing window) in either simulator or IRL devices. Also could never get a good 
response to my questions as to the events that led up to their issue (they are 
professional beta testers after all, seems like you could document a bug 
better) but eventually got approved. Finally just “got lucky” with a 
sympathizing reviewer I guess?

This is a reminder that I need to bill clients more for each build submission 
as there are SO many hoops to jump through, and those hoops change shape and 
location at least once or twice a year. 

-Andrew Bell
___
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: LiveCode convert seconds to dateItems - year is out by 19?

[Terence Heaford via use-livecode]

Could it be something to do with the base date on the mac vs the base date of 
live code?

I believe the base date on a mac is 1970, not sure what it is in live code?

Terry

> On 11 May 2021, at 13:59, Keith Clarke via use-livecode 
>  wrote:
> 
> Thanks Martin & Alex,
> 
> I wasn’t aware of ‘the seconds’ - thanks that’s behaving correctly here. 
> 
> Tracing back from this date conversion being OK to the tCreateDate variable. 
> This is item 4 of the long files, which according to the docs, should be 
> Creation date, in seconds. 
> 
> Bypassing the conversion, this item is the same for all the files in my 
> target folder (some created yesterday & some weeks ago). It has the value 
> 2212122496, which LiveCode converts (reliably!) to 2040,2,6,6,28,16,2.
> 
> Printing out the long files for one of the files in the target folder shows… 
> 
> filename,2055,0,2212122496,1620675773,2212122496,0,501,20,600,ttxtTEXT
> 
> This same weird value is being returned for the Creation Date (item 4) & Last 
> Access date (item 6), though the Last Modified Date (item 5) looks correct.
> 
> Any clues?   
> Best,
> Keith
> 
>> On 11 May 2021, at 13:09, Martin Koob via use-livecode 
>>  wrote:
>> 
>> Hi Keith
>> 
>> I just tried the following
>> 
>> on mouseup
>> 
>>  convert the seconds to dateitems
>> 
>>  put it
>> 
>> end mouseup
>> 
>> The result is 2021,5,11,7,52,5,3  So that is correct.
>> 
>> Where is the value in your tCreateDate variable from.  Maybe there was a 
>> miscalculation there.
>> 
>> Martin
>> 
>>> On May 11, 2021, at 6:44 AM, Keith Clarke via use-livecode 
>>>  wrote:
>>> 
>>> Hi folks,
>>> What am I doing wrong with convert tCreateDate from seconds to dateItems… 
>>> 
>>> I’m pulling the long files of files I created yesterday on a Mac and 
>>> attempting to convert the creation date. 
>>> 
>>> Whatever date type I choose, LiveCode reckons yesterday was in the year 
>>> 2040. Did I oversleep?
>>> Thanks
>>> Keith
>>> ___
>>> 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

Re: LiveCode convert seconds to dateItems - year is out by 19?

[Keith Clarke via use-livecode]

Thanks Martin & Alex,

I wasn’t aware of ‘the seconds’ - thanks that’s behaving correctly here. 

Tracing back from this date conversion being OK to the tCreateDate variable. 
This is item 4 of the long files, which according to the docs, should be 
Creation date, in seconds. 

Bypassing the conversion, this item is the same for all the files in my target 
folder (some created yesterday & some weeks ago). It has the value 2212122496, 
which LiveCode converts (reliably!) to 2040,2,6,6,28,16,2.

Printing out the long files for one of the files in the target folder shows… 

filename,2055,0,2212122496,1620675773,2212122496,0,501,20,600,ttxtTEXT

This same weird value is being returned for the Creation Date (item 4) & Last 
Access date (item 6), though the Last Modified Date (item 5) looks correct.
 
Any clues?   
Best,
Keith

> On 11 May 2021, at 13:09, Martin Koob via use-livecode 
>  wrote:
> 
> Hi Keith
> 
> I just tried the following
> 
> on mouseup
> 
>   convert the seconds to dateitems
> 
>   put it
> 
> end mouseup
> 
> The result is 2021,5,11,7,52,5,3  So that is correct.
> 
> Where is the value in your tCreateDate variable from.  Maybe there was a 
> miscalculation there.
> 
> Martin
> 
>> On May 11, 2021, at 6:44 AM, Keith Clarke via use-livecode 
>>  wrote:
>> 
>> Hi folks,
>> What am I doing wrong with convert tCreateDate from seconds to dateItems… 
>> 
>> I’m pulling the long files of files I created yesterday on a Mac and 
>> attempting to convert the creation date. 
>> 
>> Whatever date type I choose, LiveCode reckons yesterday was in the year 
>> 2040. Did I oversleep?
>> Thanks
>> Keith
>> ___
>> 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: LiveCode convert seconds to dateItems - year is out by 19?

[Martin Koob via use-livecode]

Hi Keith

I just tried the following

on mouseup

   convert the seconds to dateitems

   put it

end mouseup

The result is 2021,5,11,7,52,5,3  So that is correct.

Where is the value in your tCreateDate variable from.  Maybe there was a 
miscalculation there.

Martin

> On May 11, 2021, at 6:44 AM, Keith Clarke via use-livecode 
>  wrote:
> 
> Hi folks,
> What am I doing wrong with convert tCreateDate from seconds to dateItems… 
> 
> I’m pulling the long files of files I created yesterday on a Mac and 
> attempting to convert the creation date. 
> 
> Whatever date type I choose, LiveCode reckons yesterday was in the year 2040. 
> Did I oversleep?
> Thanks
> Keith
> ___
> 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: LiveCode convert seconds to dateItems - year is out by 19?

[Alex Tweedly via use-livecode]

I doubt it :-)  As a useless piece of info, it works OK for me.

I'd suggest printing out the tCreateDate and "the seconds" so you can 
compare.


Or, put the seconds into tCreateDate and convert it, just to see.

Alex.

On 11/05/2021 11:44, Keith Clarke via use-livecode wrote:

Hi folks,
What am I doing wrong with convert tCreateDate from seconds to dateItems…

I’m pulling the long files of files I created yesterday on a Mac and attempting 
to convert the creation date.

Whatever date type I choose, LiveCode reckons yesterday was in the year 2040. 
Did I oversleep?
Thanks
Keith
___
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

LiveCode convert seconds to dateItems - year is out by 19?

[Keith Clarke via use-livecode]

Hi folks,
What am I doing wrong with convert tCreateDate from seconds to dateItems… 

I’m pulling the long files of files I created yesterday on a Mac and attempting 
to convert the creation date. 

Whatever date type I choose, LiveCode reckons yesterday was in the year 2040. 
Did I oversleep?
Thanks
Keith
___
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: Finding invisible/non printable characters in a string

[David V Glasgow via use-livecode]

> On 10 May 2021, at 6:23 pm, Curry Kenworthy via use-livecode 
>  wrote:
> 
> 
> Another fun accent example is using a "Zalgo" generator:


I set out to learn some Livecode, but instead learned about Zalgo.

… and that invisible characters have to go in the ‘maybe when I have some time’ 
drawer, with datagrids, arrays and regex.

Cheers

David G

___
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