On Jul 30, 2015, at 4:34 PM, Mark Wieder wrote:
> Paul Dupuis writes:
>
>>
>> The LC 6.7.5 dictionary entry for setProp has the following:
>>
>> If the custom property you want to control is in a custom property set,
>> use array notation in the first line of the setProp handler, as in the
>>
Paul Dupuis writes:
> The recursion issue is of you have a pair (or more) or setProp handlers
> that call back to one another: ie.
Right. There's a special-case trap for that. From the docs:
If you use the set command within a setProp control structure to set the same
custom prope
Paul Dupuis writes:
> Am I missing something else Mark? How do you put a setProp handler in a
> customPropertySet? The handlers have to be in scripts. Do you use
> behaviors to switch between setprop handlers?
Nope - I'm getting distracted by too many things at once.
You're
a warning in the docs about recursion. So does the following
> work only in LC 7 and later?
>
Scott,
The recursion issue is of you have a pair (or more) or setProp handlers
that call back to one another: ie.
setprop propA pValue
set the propA of me to pValue
set the propB of me to pValue
ng of it.
>
Am I missing something else Mark? How do you put a setProp handler in a
customPropertySet? The handlers have to be in scripts. Do you use
behaviors to switch between setprop handlers?
___
use-livecode mailing list
use-livecode@lists.r
Maybe I'm missing something, but I originally thought the following would
cause a recursion error, because the property being set appears within a
setProp handler of the same name. Trying this in LC 7.0.5 works, but I
still see a warning in the docs about recursion. So does the following
work onl
Paul Dupuis writes:
> it does correctly execute the setProp handler. Much to my surprise. This
> implies that you can NOT have two custom property sets that have the
> same property name IF you want to use setprop or getProp handlers with them.
No, that's the point of the custom property sets.
T
I wonder if the mouseUp script is - set the mySet["myNumber"] of me to 90 -
whether the setProp handler for myNumber still is executed.
On Thu, Jul 30, 2015 at 3:22 PM Paul Dupuis wrote:
> On 7/30/2015 5:31 PM, Mark Wieder wrote:
> > Within the customPropertySet you just have:
> >
> > setProp
On 7/30/2015 5:31 PM, Mark Wieder wrote:
> Within the customPropertySet you just have:
>
> setProp property1 pValue
> set the property1 of me to pValue
> end property1
>
> setProp property2 pValue
> set the property2 of me to pValue
> end property2
Thanks Mark. I am interested in avoiding the
Paul Dupuis writes:
>
> On 7/30/2015 4:34 PM, Mark Wieder wrote:
> > Paul Dupuis ...> writes:
> >
> >> The LC 6.7.5 dictionary entry for setProp has the following:
> >>
> >> If the custom property you want to control is in a custom property set,
> >> use array notation in the first line of the
On 7/30/2015 4:34 PM, Mark Wieder wrote:
> Paul Dupuis writes:
>
>> The LC 6.7.5 dictionary entry for setProp has the following:
>>
>> If the custom property you want to control is in a custom property set,
>> use array notation in the first line of the setProp handler, as in the
>> following exam
Paul Dupuis writes:
>
> The LC 6.7.5 dictionary entry for setProp has the following:
>
> If the custom property you want to control is in a custom property set,
> use array notation in the first line of the setProp handler, as in the
> following example:
Interesting. I do see that in the docum
should be "end mySet" vs "end setProp".
Second, it appears you can NOT have individual setProp handlers for
custom properties in custom property sets. I.e. if mySet contain the
customer properties "that" and "this" and "those", I can not have:
On May 20, 2014, at 3:56 AM, Mark Schonewille
wrote:
> Hi Devin,
>
> The properties inspector seems to lock messages before setting properties.
> This also applies to e.g. setting the width and height of a control. If it
> didn't do this, the properties inspector would probably become unusab
Hi Devin,
The properties inspector seems to lock messages before setting
properties. This also applies to e.g. setting the width and height of a
control. If it didn't do this, the properties inspector would probably
become unusable because we'd have to switch message on and off all the
time a
The User Guide says:
--
7.10.1 Responding to changing a custom property
When you use the set command to change a custom property, LiveCode
sends a setProp trigger to the object whose property is being changed.
--
This implies that it works w
Shouldn't a setProp handler be triggered if you set the custom property in the
property inspector rather than in a script? It doesn't seem to be doing that
for me. LC 6.6.2 RC 3.
The dictionary doesn't have anything to say about this issue.
Devin
Devin Asay
Learn to code with LiveCode Univers
17 matches
Mail list logo
