>> When I feel the urge to put an integer as a property into a prop list (you
>> know, I've never really found a problem with integers as properties, but
>> it's considered bad form - maybe you just found out why?)
>
> Meow, you just stepped on the cats tale!
> Considered bad form by who???
> Tell that to the MACR engineers.
> Yeah, I know some of us have discussed this here before, and I have
> just found some pretty fine ammunition.
>
> - -- Welcome to Director --
> put the markerList
> - -- [5: "a", 10: "b"]
>
> There you go!
> Bad form... nah nah nah ;P
As far as the MACR engineers go... I don't think I need to say it.
But, as I said, I never found a problem with integers as properties (it's
floats that don't work) - I guess I was asking in a roundabout way if the
reason it's (by some) considered bad form is because of the problem Grimm
discovered when trying to access his list through list[1]. I guess changing
an integer to a descriptive string for a property could be considered
"mucking it up", to use Roy's term, but at that point it's more a matter of
preference than anything else. It's fun getting you guys all riled up,
though.
> Go press your button! <http://home.worldonline.dk/~hede/misc/kurt/>
Pressing away. I think I'll have to steal that sample.
-Kurt
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
