Re: Bug in Properties command in 6.1?
Hi Monte, I see the error with padding here too (can't set this property). To clarify, I see it on Community 6.1; in 5.5.4, it lists htmlText and listBehavior and no error. This is on Windows, haven't tried it on Mac. In case it helps, here's the contents of tList as of the point the padding error occurs: traversalOn ink firstIndent dontSearch toggleHilites threeD scrollbarWidth blendLevel rect multipleHilites shadow hScroll textAlign vScrollbar hScrollbar id altId autoTab hGrid Pete lcSQL Software http://www.lcsql.com On Thu, Jul 18, 2013 at 6:03 PM, Monte Goulding mo...@sweattechnologies.com wrote: Not in my version ;-) I've fixed that. Padding was incorrectly documented as a field property when it's only a line property. Cheers Monte On 19/07/2013, at 10:18 AM, Paul Hibbert wrote: Don't know if this is any help to you but, this script errors on the line... set the tKey of field 1 to tProps[tKey] ...when tKey = padding This happens in LC6.1 Commercial but not in LC5.5.4 or LC5.5.5 for my tests. If I add the trap... if tKey = padding then next repeat ...it runs fine in LC6.1. I don't see how padding is related to hilitedLines, but could it cause a command to fail silently? -- M E R Goulding Software development services Bespoke application development for vertical markets mergExt - There's an external for that! ___ 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: Bug in Properties command in 6.1?
On 20/07/2013, at 3:56 AM, Peter Haworth p...@lcsql.com wrote: I see the error with padding here too (can't set this property). To clarify, I see it on Community 6.1; in 5.5.4, it lists htmlText and listBehavior and no error. This is on Windows, haven't tried it on Mac. Yes, I have fixed it along with another bug but my fix hasn't been integrated yet. padding slipped by unnoticed because there's an error lock on when you set the properties and it is documented as a field property. Unfortunately there's a far more sinister issue with label, tooltip, stack title and button text. These are the properties that will return unicode variants if their value is non-ascii. Unfortunately there was an error with the code and even when ascii they are returning unicode.. Because null is not represented as a square box or anything in livecode fields it looks right when you put the value into a field and the only way you can work out there is an issue is with the length function. Both of these are fixed and should I hope be soon seen in a 6.1.1 release. In case it helps, here's the contents of tList as of the point the padding error occurs: I've fixed the issue in this pull request https://github.com/runrev/livecode/pull/82 thanks. Cheers -- Monte Goulding M E R Goulding - software development services mergExt - There's an external for that! ___ 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: Bug in Properties command in 6.1?
Great, thanks Monte. Pete lcSQL Software http://www.lcsql.com On Fri, Jul 19, 2013 at 3:35 PM, Monte Goulding mo...@sweattechnologies.com wrote: On 20/07/2013, at 3:56 AM, Peter Haworth p...@lcsql.com wrote: I see the error with padding here too (can't set this property). To clarify, I see it on Community 6.1; in 5.5.4, it lists htmlText and listBehavior and no error. This is on Windows, haven't tried it on Mac. Yes, I have fixed it along with another bug but my fix hasn't been integrated yet. padding slipped by unnoticed because there's an error lock on when you set the properties and it is documented as a field property. Unfortunately there's a far more sinister issue with label, tooltip, stack title and button text. These are the properties that will return unicode variants if their value is non-ascii. Unfortunately there was an error with the code and even when ascii they are returning unicode.. Because null is not represented as a square box or anything in livecode fields it looks right when you put the value into a field and the only way you can work out there is an issue is with the length function. Both of these are fixed and should I hope be soon seen in a 6.1.1 release. In case it helps, here's the contents of tList as of the point the padding error occurs: I've fixed the issue in this pull request https://github.com/runrev/livecode/pull/82 thanks. Cheers -- Monte Goulding M E R Goulding - software development services mergExt - There's an external for that! ___ 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
Bug in Properties command in 6.1?
This looks like a bug to me. Create a new stack add a button and a list field Set the button script to on mouseUp Get the properties of fld 1 Put 2 into it [ HilitedLines ] Set the properties of fld 1 to it end mouse up Works in 5.5.4. In 6.1, the hilitedLines is empty after the properties of field 1 are set. Only tested on a Mac. Anyone else seeing this? Tim Bleiler, Ph.D. Instructional Designer, HSIT University at Buffalo ___ 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: Bug in Properties command in 6.1?
On Thu, Jul 18, 2013 at 10:15 AM, Timothy Bleiler blei...@buffalo.eduwrote: on mouseUp Get the properties of fld 1 Put 2 into it [ HilitedLines ] Set the properties of fld 1 to it end mouse up I see the same thing here on my Mac. In fact if you simply get the properties and immediately set them again without changing anything, hilitedlines ends up empty. Pete lcSQL Software http://www.lcsql.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: Bug in Properties command in 6.1?
I submitted a bug report 11060. Tim On Jul 18, 2013, at 1:31 PM, Peter Haworth wrote: On Thu, Jul 18, 2013 at 10:15 AM, Timothy Bleiler blei...@buffalo.eduwrote: on mouseUp Get the properties of fld 1 Put 2 into it [ HilitedLines ] Set the properties of fld 1 to it end mouse up I see the same thing here on my Mac. In fact if you simply get the properties and immediately set them again without changing anything, hilitedlines ends up empty. Pete lcSQL Software http://www.lcsql.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 ___ 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: Bug in Properties command in 6.1?
On 19/07/2013, at 4:00 AM, Timothy Bleiler blei...@buffalo.edu wrote: I submitted a bug report 11060. Thanks Timothy None of my changes touched hilitedLines however we did introduce some precedence ordering of setting properties that have side effects to try and ensure that setting actually did set things correctly and I suspect this side effect slipped by unnoticed. Basically the fact that it worked in 5.5.4 is a fluke of luck based on the ordering of the keys of the array when processed. I have a suspicion that ensuring text is set first will resolve it. Cheers -- Monte Goulding M E R Goulding - software development services mergExt - There's an external for that! ___ 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: Bug in Properties command in 6.1?
Thanks Monte, Is this something you can fix at the engine level or is it something we should work around when using the properties? Tim On Jul 18, 2013, at 5:16 PM, Monte Goulding wrote: On 19/07/2013, at 4:00 AM, Timothy Bleiler blei...@buffalo.edu wrote: I submitted a bug report 11060. Thanks Timothy None of my changes touched hilitedLines however we did introduce some precedence ordering of setting properties that have side effects to try and ensure that setting actually did set things correctly and I suspect this side effect slipped by unnoticed. Basically the fact that it worked in 5.5.4 is a fluke of luck based on the ordering of the keys of the array when processed. I have a suspicion that ensuring text is set first will resolve it. Cheers -- Monte Goulding M E R Goulding - software development services mergExt - There's an external for that! ___ 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: Bug in Properties command in 6.1?
Monte- Thursday, July 18, 2013, 4:20:43 PM, you wrote: Can anyone think of any other properties that either must be set before hilitedLines is set or when setting them the hilitedLines are lost? Do a binary search. Set the hilitedLines last, if that works then start bisecting the list until you find the one that munges the setting. -- -Mark Wieder mwie...@ahsoftware.net ___ 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: Bug in Properties command in 6.1?
On 7/18/13 4:51 PM, Monte Goulding wrote: On 19/07/2013, at 7:41 AM, Richard Gaskin ambassa...@fourthworld.com wrote: If the script isn't included in the properties, why does setting the properties alter it? It doesn't... perhaps that statement was poorly worded... setting the properties of field 1 to the properties of field 2 doesn't set the script. Back when rewriting the properties first started, I wondered why the script wasn't included. Why's that? -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.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: Bug in Properties command in 6.1?
On 19/07/2013, at 9:29 AM, Mark Wieder mwie...@ahsoftware.net wrote: Can anyone think of any other properties that either must be set before hilitedLines is set or when setting them the hilitedLines are lost? Do a binary search. Set the hilitedLines last, if that works then start bisecting the list until you find the one that munges the setting. I ran this and it only came up with listBehavior and htmlText... so I'm a bit stumped. on mouseUp put the properties of field 1 into tProps repeat for each key tKey in tProps if the hilitedLines of field 1 is empty then put tOldKeycr after tList set the hilitedLines of field 1 to tProps[hilitedLines] end if set the tKey of field 1 to tProps[tKey] put tKey into tOldKey end repeat put tList end mouseUp -- Monte Goulding M E R Goulding - software development services mergExt - There's an external for that! ___ 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: Bug in Properties command in 6.1?
Monte- Thursday, July 18, 2013, 4:39:51 PM, you wrote: I ran this and it only came up with listBehavior and htmlText... so I'm a bit stumped. Hmmm... does the properties give you an ordered list? -- -Mark Wieder mwie...@ahsoftware.net ___ 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: Bug in Properties command in 6.1?
Don't know if this is any help to you but, this script errors on the line... set the tKey of field 1 to tProps[tKey] ...when tKey = padding This happens in LC6.1 Commercial but not in LC5.5.4 or LC5.5.5 for my tests. If I add the trap... if tKey = padding then next repeat ...it runs fine in LC6.1. I don't see how padding is related to hilitedLines, but could it cause a command to fail silently? Paul On 2013-07-18, at 4:39 PM, Monte Goulding wrote: On 19/07/2013, at 9:29 AM, Mark Wieder mwie...@ahsoftware.net wrote: Can anyone think of any other properties that either must be set before hilitedLines is set or when setting them the hilitedLines are lost? Do a binary search. Set the hilitedLines last, if that works then start bisecting the list until you find the one that munges the setting. I ran this and it only came up with listBehavior and htmlText... so I'm a bit stumped. on mouseUp put the properties of field 1 into tProps repeat for each key tKey in tProps if the hilitedLines of field 1 is empty then put tOldKeycr after tList set the hilitedLines of field 1 to tProps[hilitedLines] end if set the tKey of field 1 to tProps[tKey] put tKey into tOldKey end repeat put tList end mouseUp -- Monte Goulding M E R Goulding - software development services mergExt - There's an external for that! ___ 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: Bug in Properties command in 6.1?
Not in my version ;-) I've fixed that. Padding was incorrectly documented as a field property when it's only a line property. Cheers Monte On 19/07/2013, at 10:18 AM, Paul Hibbert wrote: Don't know if this is any help to you but, this script errors on the line... set the tKey of field 1 to tProps[tKey] ...when tKey = padding This happens in LC6.1 Commercial but not in LC5.5.4 or LC5.5.5 for my tests. If I add the trap... if tKey = padding then next repeat ...it runs fine in LC6.1. I don't see how padding is related to hilitedLines, but could it cause a command to fail silently? -- M E R Goulding Software development services Bespoke application development for vertical markets mergExt - There's an external for that! ___ 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
