The encoding property

Peter Haworth pete at lcsql.com
Mon Aug 26 17:46:03 EDT 2013


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
_unplacedgroupids
_vscrollbarid
abbr
abbrev
abbreviated
breakpoints
columndel
compositorstatistics
controlids
controlnames
currentcard
debugcontext
deferscreenupdates
desktop
detailed
documents
effective
engine
english
fillback
flaggedranges
formattedstyledtext
home
iconmenu
internet
lockupdates
long
lzwkey
messagemessages
printrect
processtype
referringstack
revavailablehandlers
revavailablevariables
revcrashreportsettings
revlicenseinfo
revlicenselimits
revmessageboxlastobject
revmessageboxredirect
revobjectlisteners
revpropertylistenerthrottle
revruntimebehaviour
revunplacedgroupids
rowdel
savecompressed
screen
scriptexecutionerrors
scriptparsingerrors
securitycategories
securitypermissions
short
statusicon
statusiconmenu
statusicontooltip
system
tabalign
temporary
traceabort
traceuntil
unicodeacceleratortext
urlresponse
watchedvariables
working


Pete
lcSQL Software <http://www.lcsql.com>


On Mon, Aug 26, 2013 at 2:22 PM, Peter Haworth <pete at lcsql.com> wrote:

> 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 db of the dictionary to get a
> definitive list of properties which have no dictionary entries.
>
>
>
> Pete
> lcSQL Software <http://www.lcsql.com>
>
>
> On Mon, Aug 26, 2013 at 1:12 PM, J. Landman Gay <jacque at hyperactivesw.com>wrote:
>
>> 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 anyone else has come across this bug?
>>>
>>
>> Yeah. Write it up for us?
>>
>> --
>> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
>> HyperActive Software           |     http://www.hyperactivesw.com
>>
>>
>> ______________________________**_________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>
>>
>
>



More information about the use-livecode mailing list