Re: Property Inspector bug for keys with commas in the key name

2023-11-03 Thread Paul Dupuis via use-livecode

Hi Bernd,

You do make a good point about the documentation regarding custom 
properties. Assuming people read the documentation. At the same time, 
you used to be able to use commas in custom property names. As Curry 
noted, Livecode even used to use them in the standalone setting 
properties, so the mothership set a precedence.


My problem is that I have stacks where commas were used because they 
could be used and there was value to using them as evidenced by how 
Livecode used them in the standalone settings. Now I can only edit them 
via scripts rather than the current PI.


It's not really a problem since I can do updates by script. It is more 
of just an annoyance.


Knowing that the current issue if the hilitedElement of the tree view 
object, I won't bother trying to look for any quick fix I could make to 
the PI code in the IDE. Thanks for the information.



On 11/3/2023 2:29 PM, Niggemann, Bernd via use-livecode wrote:

Hi Paul,

The problem with the comma in a customproperty name in the Properties Inspector (PI) arises because 
the PI uses a treeview to display the customproperties. More specifically the 
"hilitedElement" to retrieve the current selection and "hilitedElement" has the 
form:
"A comma delimited list of array keys."

Now you have a comma in your customproperty name and at that point the PI is 
confused as to what is the key and what is the value and fails to display both.

However I wonder if treeview or PI is to blame:

Page 145 of "Livecode User Guide" 9.6.10
Custom Property Names
The name of a custom property must consist of a single word and may contain any 
combination of letters, digits, and underscores (_). The first character must 
be either a letter or an underscore.

Page 113 of "Revolution User Guide 2.0" printed edition from 2004
Custom Property Names
The name of a custom property must consist of a single word and may contain any 
combination of letters, digits, and underscores (_). The first character must 
be either a letter or an underscore.

So I am afraid that treeview could not expect a comma in a customproperty name.

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: Property Inspector bug for keys with commas in the key name

2023-11-03 Thread Curry Kenworthy via use-livecode



Bernd:

> "Livecode User Guide" 9.6.10 - Custom Property Names
> any combination of letters, digits, and underscores
> treeview could not expect a comma in a customproperty name.

Hi Y'all,

Anyone ever hear of the cRevStandaloneSettings?

Wonderful (official) prop set ... especially all the commas!

Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
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: Crashing on M2 Mac

2023-11-03 Thread Dan Friedman via use-livecode
Mark,

It is literally:convert dateSecs to date  //dateSecs is a epoch value (as 
in the seconds).  And yes, I am 100% positive dateSecs is a valid date


-Dan


From: use-livecode  on behalf of Mark 
Waddingham via use-livecode 
Date: Friday, November 3, 2023 at 11:16 AM
To: How to use LiveCode 
Cc: Mark Waddingham 
Subject: Re: Crashing on M2 Mac
Dan, could you file a bug with the offending line of code which crashed ios17 
with 9.6.10… Just so we can check it isn’t still there in 9.6.11 :)

Thanks!

Mark

Sent from my iPhone

> On 3 Nov 2023, at 16:48, Dan Friedman via use-livecode 
>  wrote:
>
> To all,
>
> Oops!  I am mistaken…. It wasn’t MacOS that had the issue, it was iOS 17 that 
> was problem.   iOS app built with 9.6.10 running on iOS 17 crashes when the 
> convert command is called.  I can (in my experience) absolutely confirm this. 
>  Debugged it down to the single line of code.  Rebuilt the app with 10.0.0 
> (dp 6) and the issue was solved.
>
> Apologies for posting the wrong platform.
>
> -Dan
>
>
> From: use-livecode  on behalf of 
> panagiotis merakos via use-livecode 
> Date: Friday, November 3, 2023 at 9:23 AM
> To: How to use LiveCode 
> Cc: panagiotis merakos 
> Subject: Re: Crashing on M2 Mac
> Hello all,
>
> We are not aware of any bug in the "convert" command, and I think it is
> highly unlikely such a bug to affect M2 machines but not M1 ones.
>
> We have a M2 machine running Sonoma which is used in the prerelease testing
> so my feeling is that if there was such a bug, we would have caught it in
> the prerelease testing of 9.6.11 rc1, which included a fix related to the
> system date on Sonoma. Also, a related report we got about the convert
> command - but turned out to be not a bug, is this one:
>
> https://quality.livecode.com/show_bug.cgi?id=24362
>
> BTW, the crash report that is attached in the first post indicates that the
> app was running under Rosetta (> Code Type:X86-64 (Translated))
>
> @Peter
> If you have a reproducible recipe please do file a bug report and include
> your app or a sample stack - I can give it a try in my Sonoma M2 mac mini.
>
> Kind regards,
> Panos
>
>
>> On Fri, 3 Nov 2023 at 14:05, Paul Dupuis via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>
>> Also, have you (or could you) try LC 9.6.11rc-1 and see if that has a
>> fix for the convert issue you found?
>>
>> We use convert a lot (currently under LC 9.6.10) and can't take out app
>> to LC 10, so a 9.6.11 that addresses this convert bug is needed.
>>
>>> On 11/2/2023 6:33 PM, Dan Friedman via use-livecode wrote:
>>> Peter,
>>>
>>> I recently discovered (from one of my own apps) that a Mac app built
>> with 9.6.10 running on Sonoma crashes when the convert command is called.
>> I rebuilt the app in 10.0.0 (dp 6) and the app no longer crashes.   Hope
>> that helps!
>>>
>>> - Dan
>>>
>>>
>>> From: use-livecode  on behalf of
>> Peter Bogdanoff via use-livecode 
>>> Date: Thursday, November 2, 2023 at 3:23 PM
>>> To: Paul Dupuis via use-livecode 
>>> Cc: Peter Bogdanoff 
>>> Subject: Crashing on M2 Mac
>>> A user is reporting crashing on his M2 Sonoma Mac.
>>>
>>> This was a build of LC 9.6.10, with both Intel and Apple chosen in the
>> Standalone settings.
>>>
>>> It did not crash with only Apple chosen, though there were script errors
>> that did not happen with non-M2 users (M1 is OK). I haven’t been able to
>> debug that since I don’t have an M2 Mac.
>>>
>>> Has anyone used LC with M2?
>>>
>>> Peter Bogdanoff
>>>
 Process:   MITA [10810]
 Path:  /Applications/MITA.app/Contents/MacOS/MITA
 Identifier:com.artsinteractiveinc.mita
 Version:   3.0 (3.0)
 Code Type: X86-64 (Translated)
 Parent Process:launchd [1]
 User ID:   501

 Date/Time: 2023-11-02 13:22:17.1555 -0400
 OS Version:macOS 14.1 (23B74)
 Report Version:12
 Anonymous UUID:982CECFD-B763-4068-2C69-6639836A03DF

 Sleep/Wake UUID:   DAD13568-D6D9-4419-BF53-FA013DE5385B

 Time Awake Since Boot: 11 seconds
 Time Since Wake:   1041 seconds

 System Integrity Protection: enabled

 Notes:
 PC register does not match crashing frame (0x0 vs 0x1026B9E58)

 Crashed Thread:0  Dispatch queue: com.apple.main-thread

 Exception Type:EXC_BAD_ACCESS (SIGSEGV)
 Exception Codes:   KERN_INVALID_ADDRESS at 0x0004
 Exception Codes:   0x0001, 0x0004

 VM Region Info: 0x4 is not in any region.  Bytes before following
>> region: 140722906071036
   REGION TYPESTART - END [ VSIZE]
>> PRT/MAX SHRMOD  REGION DETAIL
   UNUSED SPACE AT START
 --->
   mapped file  7ffc9ad4-7ffcc03e8000 [598.7M]
>> r-x/r-x SM=COW  ...t_id=60eeba9b

 Error Formulating Crash Report:

Property Inspector bug for keys with commas in the key name

2023-11-03 Thread Niggemann, Bernd via use-livecode
Hi Paul,

The problem with the comma in a customproperty name in the Properties Inspector 
(PI) arises because the PI uses a treeview to display the customproperties. 
More specifically the "hilitedElement" to retrieve the current selection and 
"hilitedElement" has the form:
"A comma delimited list of array keys."

Now you have a comma in your customproperty name and at that point the PI is 
confused as to what is the key and what is the value and fails to display both.

However I wonder if treeview or PI is to blame:

Page 145 of "Livecode User Guide" 9.6.10
Custom Property Names
The name of a custom property must consist of a single word and may contain any 
combination of letters, digits, and underscores (_). The first character must 
be either a letter or an underscore.

Page 113 of "Revolution User Guide 2.0" printed edition from 2004
Custom Property Names
The name of a custom property must consist of a single word and may contain any 
combination of letters, digits, and underscores (_). The first character must 
be either a letter or an underscore.

So I am afraid that treeview could not expect a comma in a customproperty name.

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: Crashing on M2 Mac

2023-11-03 Thread Mark Waddingham via use-livecode
Dan, could you file a bug with the offending line of code which crashed ios17 
with 9.6.10… Just so we can check it isn’t still there in 9.6.11 :)

Thanks!

Mark

Sent from my iPhone

> On 3 Nov 2023, at 16:48, Dan Friedman via use-livecode 
>  wrote:
> 
> To all,
> 
> Oops!  I am mistaken…. It wasn’t MacOS that had the issue, it was iOS 17 that 
> was problem.   iOS app built with 9.6.10 running on iOS 17 crashes when the 
> convert command is called.  I can (in my experience) absolutely confirm this. 
>  Debugged it down to the single line of code.  Rebuilt the app with 10.0.0 
> (dp 6) and the issue was solved.
> 
> Apologies for posting the wrong platform.
> 
> -Dan
> 
> 
> From: use-livecode  on behalf of 
> panagiotis merakos via use-livecode 
> Date: Friday, November 3, 2023 at 9:23 AM
> To: How to use LiveCode 
> Cc: panagiotis merakos 
> Subject: Re: Crashing on M2 Mac
> Hello all,
> 
> We are not aware of any bug in the "convert" command, and I think it is
> highly unlikely such a bug to affect M2 machines but not M1 ones.
> 
> We have a M2 machine running Sonoma which is used in the prerelease testing
> so my feeling is that if there was such a bug, we would have caught it in
> the prerelease testing of 9.6.11 rc1, which included a fix related to the
> system date on Sonoma. Also, a related report we got about the convert
> command - but turned out to be not a bug, is this one:
> 
> https://quality.livecode.com/show_bug.cgi?id=24362
> 
> BTW, the crash report that is attached in the first post indicates that the
> app was running under Rosetta (> Code Type:X86-64 (Translated))
> 
> @Peter
> If you have a reproducible recipe please do file a bug report and include
> your app or a sample stack - I can give it a try in my Sonoma M2 mac mini.
> 
> Kind regards,
> Panos
> 
> 
>> On Fri, 3 Nov 2023 at 14:05, Paul Dupuis via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>> Also, have you (or could you) try LC 9.6.11rc-1 and see if that has a
>> fix for the convert issue you found?
>> 
>> We use convert a lot (currently under LC 9.6.10) and can't take out app
>> to LC 10, so a 9.6.11 that addresses this convert bug is needed.
>> 
>>> On 11/2/2023 6:33 PM, Dan Friedman via use-livecode wrote:
>>> Peter,
>>> 
>>> I recently discovered (from one of my own apps) that a Mac app built
>> with 9.6.10 running on Sonoma crashes when the convert command is called.
>> I rebuilt the app in 10.0.0 (dp 6) and the app no longer crashes.   Hope
>> that helps!
>>> 
>>> - Dan
>>> 
>>> 
>>> From: use-livecode  on behalf of
>> Peter Bogdanoff via use-livecode 
>>> Date: Thursday, November 2, 2023 at 3:23 PM
>>> To: Paul Dupuis via use-livecode 
>>> Cc: Peter Bogdanoff 
>>> Subject: Crashing on M2 Mac
>>> A user is reporting crashing on his M2 Sonoma Mac.
>>> 
>>> This was a build of LC 9.6.10, with both Intel and Apple chosen in the
>> Standalone settings.
>>> 
>>> It did not crash with only Apple chosen, though there were script errors
>> that did not happen with non-M2 users (M1 is OK). I haven’t been able to
>> debug that since I don’t have an M2 Mac.
>>> 
>>> Has anyone used LC with M2?
>>> 
>>> Peter Bogdanoff
>>> 
 Process:   MITA [10810]
 Path:  /Applications/MITA.app/Contents/MacOS/MITA
 Identifier:com.artsinteractiveinc.mita
 Version:   3.0 (3.0)
 Code Type: X86-64 (Translated)
 Parent Process:launchd [1]
 User ID:   501
 
 Date/Time: 2023-11-02 13:22:17.1555 -0400
 OS Version:macOS 14.1 (23B74)
 Report Version:12
 Anonymous UUID:982CECFD-B763-4068-2C69-6639836A03DF
 
 Sleep/Wake UUID:   DAD13568-D6D9-4419-BF53-FA013DE5385B
 
 Time Awake Since Boot: 11 seconds
 Time Since Wake:   1041 seconds
 
 System Integrity Protection: enabled
 
 Notes:
 PC register does not match crashing frame (0x0 vs 0x1026B9E58)
 
 Crashed Thread:0  Dispatch queue: com.apple.main-thread
 
 Exception Type:EXC_BAD_ACCESS (SIGSEGV)
 Exception Codes:   KERN_INVALID_ADDRESS at 0x0004
 Exception Codes:   0x0001, 0x0004
 
 VM Region Info: 0x4 is not in any region.  Bytes before following
>> region: 140722906071036
   REGION TYPESTART - END [ VSIZE]
>> PRT/MAX SHRMOD  REGION DETAIL
   UNUSED SPACE AT START
 --->
   mapped file  7ffc9ad4-7ffcc03e8000 [598.7M]
>> r-x/r-x SM=COW  ...t_id=60eeba9b
 
 Error Formulating Crash Report:
 PC register does not match crashing frame (0x0 vs 0x1026B9E58)
>>> ___
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>>> 

Re: Crashing on M2 Mac

2023-11-03 Thread Dan Friedman via use-livecode
To all,

Oops!  I am mistaken…. It wasn’t MacOS that had the issue, it was iOS 17 that 
was problem.   iOS app built with 9.6.10 running on iOS 17 crashes when the 
convert command is called.  I can (in my experience) absolutely confirm this.  
Debugged it down to the single line of code.  Rebuilt the app with 10.0.0 (dp 
6) and the issue was solved.

Apologies for posting the wrong platform.

-Dan


From: use-livecode  on behalf of 
panagiotis merakos via use-livecode 
Date: Friday, November 3, 2023 at 9:23 AM
To: How to use LiveCode 
Cc: panagiotis merakos 
Subject: Re: Crashing on M2 Mac
Hello all,

We are not aware of any bug in the "convert" command, and I think it is
highly unlikely such a bug to affect M2 machines but not M1 ones.

We have a M2 machine running Sonoma which is used in the prerelease testing
so my feeling is that if there was such a bug, we would have caught it in
the prerelease testing of 9.6.11 rc1, which included a fix related to the
system date on Sonoma. Also, a related report we got about the convert
command - but turned out to be not a bug, is this one:

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

BTW, the crash report that is attached in the first post indicates that the
app was running under Rosetta (> Code Type:X86-64 (Translated))

@Peter
If you have a reproducible recipe please do file a bug report and include
your app or a sample stack - I can give it a try in my Sonoma M2 mac mini.

Kind regards,
Panos


On Fri, 3 Nov 2023 at 14:05, Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Also, have you (or could you) try LC 9.6.11rc-1 and see if that has a
> fix for the convert issue you found?
>
> We use convert a lot (currently under LC 9.6.10) and can't take out app
> to LC 10, so a 9.6.11 that addresses this convert bug is needed.
>
> On 11/2/2023 6:33 PM, Dan Friedman via use-livecode wrote:
> > Peter,
> >
> > I recently discovered (from one of my own apps) that a Mac app built
> with 9.6.10 running on Sonoma crashes when the convert command is called.
> I rebuilt the app in 10.0.0 (dp 6) and the app no longer crashes.   Hope
> that helps!
> >
> > - Dan
> >
> >
> > From: use-livecode  on behalf of
> Peter Bogdanoff via use-livecode 
> > Date: Thursday, November 2, 2023 at 3:23 PM
> > To: Paul Dupuis via use-livecode 
> > Cc: Peter Bogdanoff 
> > Subject: Crashing on M2 Mac
> > A user is reporting crashing on his M2 Sonoma Mac.
> >
> > This was a build of LC 9.6.10, with both Intel and Apple chosen in the
> Standalone settings.
> >
> > It did not crash with only Apple chosen, though there were script errors
> that did not happen with non-M2 users (M1 is OK). I haven’t been able to
> debug that since I don’t have an M2 Mac.
> >
> > Has anyone used LC with M2?
> >
> > Peter Bogdanoff
> >
> >> Process:   MITA [10810]
> >> Path:  /Applications/MITA.app/Contents/MacOS/MITA
> >> Identifier:com.artsinteractiveinc.mita
> >> Version:   3.0 (3.0)
> >> Code Type: X86-64 (Translated)
> >> Parent Process:launchd [1]
> >> User ID:   501
> >>
> >> Date/Time: 2023-11-02 13:22:17.1555 -0400
> >> OS Version:macOS 14.1 (23B74)
> >> Report Version:12
> >> Anonymous UUID:982CECFD-B763-4068-2C69-6639836A03DF
> >>
> >> Sleep/Wake UUID:   DAD13568-D6D9-4419-BF53-FA013DE5385B
> >>
> >> Time Awake Since Boot: 11 seconds
> >> Time Since Wake:   1041 seconds
> >>
> >> System Integrity Protection: enabled
> >>
> >> Notes:
> >> PC register does not match crashing frame (0x0 vs 0x1026B9E58)
> >>
> >> Crashed Thread:0  Dispatch queue: com.apple.main-thread
> >>
> >> Exception Type:EXC_BAD_ACCESS (SIGSEGV)
> >> Exception Codes:   KERN_INVALID_ADDRESS at 0x0004
> >> Exception Codes:   0x0001, 0x0004
> >>
> >> VM Region Info: 0x4 is not in any region.  Bytes before following
> region: 140722906071036
> >>REGION TYPESTART - END [ VSIZE]
> PRT/MAX SHRMOD  REGION DETAIL
> >>UNUSED SPACE AT START
> >> --->
> >>mapped file  7ffc9ad4-7ffcc03e8000 [598.7M]
> r-x/r-x SM=COW  ...t_id=60eeba9b
> >>
> >> Error Formulating Crash Report:
> >> PC register does not match crashing frame (0x0 vs 0x1026B9E58)
> > ___
> > 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
> 

Re: Crashing on M2 Mac

2023-11-03 Thread panagiotis merakos via use-livecode
Hello all,

We are not aware of any bug in the "convert" command, and I think it is
highly unlikely such a bug to affect M2 machines but not M1 ones.

We have a M2 machine running Sonoma which is used in the prerelease testing
so my feeling is that if there was such a bug, we would have caught it in
the prerelease testing of 9.6.11 rc1, which included a fix related to the
system date on Sonoma. Also, a related report we got about the convert
command - but turned out to be not a bug, is this one:

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

BTW, the crash report that is attached in the first post indicates that the
app was running under Rosetta (> Code Type:X86-64 (Translated))

@Peter
If you have a reproducible recipe please do file a bug report and include
your app or a sample stack - I can give it a try in my Sonoma M2 mac mini.

Kind regards,
Panos


On Fri, 3 Nov 2023 at 14:05, Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Also, have you (or could you) try LC 9.6.11rc-1 and see if that has a
> fix for the convert issue you found?
>
> We use convert a lot (currently under LC 9.6.10) and can't take out app
> to LC 10, so a 9.6.11 that addresses this convert bug is needed.
>
> On 11/2/2023 6:33 PM, Dan Friedman via use-livecode wrote:
> > Peter,
> >
> > I recently discovered (from one of my own apps) that a Mac app built
> with 9.6.10 running on Sonoma crashes when the convert command is called.
> I rebuilt the app in 10.0.0 (dp 6) and the app no longer crashes.   Hope
> that helps!
> >
> > - Dan
> >
> >
> > From: use-livecode  on behalf of
> Peter Bogdanoff via use-livecode 
> > Date: Thursday, November 2, 2023 at 3:23 PM
> > To: Paul Dupuis via use-livecode 
> > Cc: Peter Bogdanoff 
> > Subject: Crashing on M2 Mac
> > A user is reporting crashing on his M2 Sonoma Mac.
> >
> > This was a build of LC 9.6.10, with both Intel and Apple chosen in the
> Standalone settings.
> >
> > It did not crash with only Apple chosen, though there were script errors
> that did not happen with non-M2 users (M1 is OK). I haven’t been able to
> debug that since I don’t have an M2 Mac.
> >
> > Has anyone used LC with M2?
> >
> > Peter Bogdanoff
> >
> >> Process:   MITA [10810]
> >> Path:  /Applications/MITA.app/Contents/MacOS/MITA
> >> Identifier:com.artsinteractiveinc.mita
> >> Version:   3.0 (3.0)
> >> Code Type: X86-64 (Translated)
> >> Parent Process:launchd [1]
> >> User ID:   501
> >>
> >> Date/Time: 2023-11-02 13:22:17.1555 -0400
> >> OS Version:macOS 14.1 (23B74)
> >> Report Version:12
> >> Anonymous UUID:982CECFD-B763-4068-2C69-6639836A03DF
> >>
> >> Sleep/Wake UUID:   DAD13568-D6D9-4419-BF53-FA013DE5385B
> >>
> >> Time Awake Since Boot: 11 seconds
> >> Time Since Wake:   1041 seconds
> >>
> >> System Integrity Protection: enabled
> >>
> >> Notes:
> >> PC register does not match crashing frame (0x0 vs 0x1026B9E58)
> >>
> >> Crashed Thread:0  Dispatch queue: com.apple.main-thread
> >>
> >> Exception Type:EXC_BAD_ACCESS (SIGSEGV)
> >> Exception Codes:   KERN_INVALID_ADDRESS at 0x0004
> >> Exception Codes:   0x0001, 0x0004
> >>
> >> VM Region Info: 0x4 is not in any region.  Bytes before following
> region: 140722906071036
> >>REGION TYPESTART - END [ VSIZE]
> PRT/MAX SHRMOD  REGION DETAIL
> >>UNUSED SPACE AT START
> >> --->
> >>mapped file  7ffc9ad4-7ffcc03e8000 [598.7M]
> r-x/r-x SM=COW  ...t_id=60eeba9b
> >>
> >> Error Formulating Crash Report:
> >> PC register does not match crashing frame (0x0 vs 0x1026B9E58)
> > ___
> > 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: Property Inspector bug for keys with commas in the key name

2023-11-03 Thread Mike Kerner via use-livecode
ok, let's see. you got me distracted from real work:
if you're following along at home, in real time, look in
toolset->palettes->inspector->editors->com.livecode.pi.customprops.behavior.livecodescript

On Thu, Nov 2, 2023 at 6:02 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> This bug (https://quality.livecode.com/show_bug.cgi?id=23512) where a
> comma in the key name of an array prevents the Proerty Inspector from
> being able to edit the property just bit me again.
>
> I have a stack (for help) that extensively uses keys with commas (create
> prior to the Project Browser and new PI) that I can not edit except by
> script - which is a pain in the (you know what).
>
> Does anyone have an edit to the PI code for this OR an alternative PI
> that does not have this bug?
>
> ___
> 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
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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: Property Inspector bug for keys with commas in the key name

2023-11-03 Thread Mike Kerner via use-livecode
no, but, i started to write a wiki on the PI/PE, which might help you to
get started in your search:
https://github.com/macMikey/LC-HACK/wiki/Property-Inspector

On Thu, Nov 2, 2023 at 6:02 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> This bug (https://quality.livecode.com/show_bug.cgi?id=23512) where a
> comma in the key name of an array prevents the Proerty Inspector from
> being able to edit the property just bit me again.
>
> I have a stack (for help) that extensively uses keys with commas (create
> prior to the Project Browser and new PI) that I can not edit except by
> script - which is a pain in the (you know what).
>
> Does anyone have an edit to the PI code for this OR an alternative PI
> that does not have this bug?
>
> ___
> 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
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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: Crashing on M2 Mac

2023-11-03 Thread Paul Dupuis via use-livecode
Also, have you (or could you) try LC 9.6.11rc-1 and see if that has a 
fix for the convert issue you found?


We use convert a lot (currently under LC 9.6.10) and can't take out app 
to LC 10, so a 9.6.11 that addresses this convert bug is needed.


On 11/2/2023 6:33 PM, Dan Friedman via use-livecode wrote:

Peter,

I recently discovered (from one of my own apps) that a Mac app built with 
9.6.10 running on Sonoma crashes when the convert command is called.  I rebuilt 
the app in 10.0.0 (dp 6) and the app no longer crashes.   Hope that helps!

- Dan


From: use-livecode  on behalf of Peter 
Bogdanoff via use-livecode 
Date: Thursday, November 2, 2023 at 3:23 PM
To: Paul Dupuis via use-livecode 
Cc: Peter Bogdanoff 
Subject: Crashing on M2 Mac
A user is reporting crashing on his M2 Sonoma Mac.

This was a build of LC 9.6.10, with both Intel and Apple chosen in the  
Standalone settings.

It did not crash with only Apple chosen, though there were script errors that 
did not happen with non-M2 users (M1 is OK). I haven’t been able to debug that 
since I don’t have an M2 Mac.

Has anyone used LC with M2?

Peter Bogdanoff


Process:   MITA [10810]
Path:  /Applications/MITA.app/Contents/MacOS/MITA
Identifier:com.artsinteractiveinc.mita
Version:   3.0 (3.0)
Code Type: X86-64 (Translated)
Parent Process:launchd [1]
User ID:   501

Date/Time: 2023-11-02 13:22:17.1555 -0400
OS Version:macOS 14.1 (23B74)
Report Version:12
Anonymous UUID:982CECFD-B763-4068-2C69-6639836A03DF

Sleep/Wake UUID:   DAD13568-D6D9-4419-BF53-FA013DE5385B

Time Awake Since Boot: 11 seconds
Time Since Wake:   1041 seconds

System Integrity Protection: enabled

Notes:
PC register does not match crashing frame (0x0 vs 0x1026B9E58)

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x0004
Exception Codes:   0x0001, 0x0004

VM Region Info: 0x4 is not in any region.  Bytes before following region: 
140722906071036
   REGION TYPESTART - END [ VSIZE] PRT/MAX 
SHRMOD  REGION DETAIL
   UNUSED SPACE AT START
--->
   mapped file  7ffc9ad4-7ffcc03e8000 [598.7M] r-x/r-x 
SM=COW  ...t_id=60eeba9b

Error Formulating Crash Report:
PC register does not match crashing frame (0x0 vs 0x1026B9E58)

___
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