Re: The encoding property

On Tue, Aug 27, 2013 at 7:19 AM, Richard Gaskin wrote: > I wonder if perhaps you could split the difference, and have your > property-checking routine done during development to build a list that's > used at runtime. That would keep runtime lean and efficient, and unless > you plan on abandoning

Re: The encoding property

On Mon, Aug 26, 2013 at 2:22 PM, Peter Haworth wrote: > I've entered bug# 11129 at the QCC. The fix is already in "awaiting build" status Pete lcSQL Software ___ use-livecode mailing list use-livecode@lists.runrev.com Please vi

Re: The encoding property

Peter Haworth wrote: This is for the next release of my lcStackBrowser plugin. It will include the ability to display and edit properties within the main lcStackBrowser window. As part of that functionality, users can define property groups to include whatever properties they wish. In turn, th

Re: The encoding property

Thanks Monte. I noticed the IDE props (the ones beginning with "rev" I think). Will be interesting to see how things shape up after the parser rewrite. Pete lcSQL Software On Mon, Aug 26, 2013 at 3:06 PM, Monte Goulding wrote: > On 27/08/2013, at 7:46 AM, Peter Haworth

Re: The encoding property

On Mon, Aug 26, 2013 at 6:06 PM, Richard Gaskin wrote: > I don't mean to sound pedantic, but serious question: what is your goal > with that? This is for the next release of my lcStackBrowser plugin. It will include the ability to display and edit properties within the main lcStackBrowser wind

Re: The encoding property

Peter Haworth wrote: My goal is to get a list of the valid property names for each Livecode object (stack, card, field, etc) I don't mean to sound pedantic, but serious question: what is your goal with that? Sometimes in our imperfect world we find limitations in the engine, and a hard-wir

Re: The encoding property

Hi Jacque, Those are the only two my script crashed on. I was getting the of the templateField, where is a line from the propertynames, executed within a try/catch block in an attempt to get a full list of properties for a filed, button, stack, card, etc. Some got caught in the catch statement

Re: The encoding property

My goal is to get a list of the valid property names for each Livecode object (stack, card, field, etc) I'm not using "the properties" because it does not return a complete list of property names. So my solution, in pseudo code is: for each propertyname in the propertynames Get the propertyna

Re: The encoding property

On 27/08/2013, at 7:46 AM, Peter Haworth wrote: > Here's the list of entries in propertynames that have no matching entry in > the dictionary. There's quite a few understandable omissions such as > "abbrev", "english","system"(why are they in the propertynames?). Maybe I > should put this into

Re: The encoding property

Peter - Not all properties are available for all object types; indeed, many are global properties. What is your goal, and is "the properties" the best way to reach it? -- Richard Gaskin Fourth World LiveCode training and consulting: http://www.fourthworld.com Webzine for LiveCode develope

Re: The encoding property

On Mon, Aug 26, 2013 at 3:06 PM, Björnke von Gierke wrote: > i think your list is overzealous. For example considering "abbr", > "abbrev", "abbreviated" (from teh abbreviated docu entry): > > Note: The abbreviated keyword is implemented internally as a property, and > appears in the propertyNames

Re: The encoding property

i think your list is overzealous. For example considering "abbr", "abbrev", "abbreviated" (from teh abbreviated docu entry): Note: The abbreviated keyword is implemented internally as a property, and appears in the propertyNames. However, it cannot be used as a property in an expression, nor wi

Re: The encoding property

Here's the list of entries in propertynames that have no matching entry in the dictionary. There's quite a few understandable omissions such as "abbrev", "english","system"(why are they in the propertynames?). Maybe I should put this into a QCC report? _hscrollbarid _ideoverride _unplacedgroupid

Re: The encoding property

On 8/26/13 4:22 PM, Peter Haworth wrote: I've entered bug# 11129 at the QCC. Came across another property that causes the same problem - flaggedRanges. It may crash on other unicode-related functions too. I was crashing all over the place trying to use the template field to parse and revise

Re: The encoding property

I've entered bug# 11129 at the QCC. Came across another property that causes the same problem - flaggedRanges. That's also interesting because flaggedRanges is not in the dictionary. I think I'm going to make a simple stack that checks the output of the propertynames against the Bjornke's SQLite

Re: The encoding property

On 8/26/13 2:14 PM, Peter Haworth wrote: If you try to get the encoding of the templatefield, LC aborts with no error message. Getting the encoding of a real field works OK. Happens in 5.5.0, thru 6.1.1(rc3). I realize this is pretty obscure but I do have a need to do this and wondering if any

Re: The encoding property

Pete- Monday, August 26, 2013, 12:14:39 PM, you wrote: > If you try to get the encoding of the templatefield, LC aborts with no > error message. Getting the encoding of a real field works OK. Happens in > 5.5.0, thru 6.1.1(rc3). > I realize this is pretty obscure but I do have a need to do thi

The encoding property

If you try to get the encoding of the templatefield, LC aborts with no error message. Getting the encoding of a real field works OK. Happens in 5.5.0, thru 6.1.1(rc3). I realize this is pretty obscure but I do have a need to do this and wondering if anyone else has come across this bug? Pete lc