RIght, I saw that when looking at some Livecode Preference settings. I
assume that was done in the days before arrays were possible in custom
properties and they never changed it when arrays became possible.
I guess a lot of this stuff doesn't cause any grief to people who are
developing "normal"
Peter Haworth writes:
> Pretty inconsistent, wouldn't you say?
Oh, it gets worse. You can also insert commas into the property name, and
this isn't likely to change because the IDE uses this "feature".
--
Mark Wieder
mwie...@ahsoftware.net
___
I think "undesirable" is a good way to put it.
I am working round it but, as usual, it's not quite as simple as it might
seem :-(
Here's another little oddity.
The Inspector palette for an object happily lets me add a property to
customkeys with spaces in its name, or any other special character
Peter Haworth writes:
> Bug?
Well, I think it's undesirable and there are several "fixed" bugs in the
database (8186, 8501, etc.) dealing with this situation. It's not quite a
bug because it's documented behavior.
There are reserved keywords for built-in things that you can't override
(groups d
prefix to prevent name clashes (for example
> "uName" instead of "name").
>
>
> Is this a possible collision?
>
>
> Craig Newman
>
>
>
>
> -Original Message-
> From: Peter Haworth
> To: How to use LiveCode
> Sent: Fri, May
ix to prevent name clashes (for example "uName" instead of "name").
Is this a possible collision?
Craig Newman
-Original Message-
From: Peter Haworth
To: How to use LiveCode
Sent: Fri, May 10, 2013 1:06 pm
Subject: customPropertySets
I'm seeing an unex
I'm seeing an unexpected behavior when using the customProperty set of an
object.
Here's the recipe.
1.Create a new stack and put a datagrid on it
2. Make a button with the following code:
on mouseUp
set the customPropertyset of group "Datagrid 1" to "dgProps"
get the style of gro
