Aha. My first thought was that it must be a Mac system “feature” since the
iconised version looked Mac-ish rather than LC-ish. But I hadn’t updated to
Mojave, and I had just updated to LC9.0.1 and it didn’t affect LC8, so I
deduced it was down to LC. Thanks Brian, you have given me a place to lo
, 2018, 8:06 PM -0500, Neville Smythe via use-livecode
, wrote:
> Thanks for the replies about may setProp question a little while back. But
> no-one game me any info about the annoying problem I raised concerning
> windows under LC9 and it’s driving me nuts.
>
> To recap: new stac
Thanks for the replies about may setProp question a little while back. But
no-one game me any info about the annoying problem I raised concerning windows
under LC9 and it’s driving me nuts.
To recap: new stacks (but not old stacks) and some engine windows such as for
scripts and the
I have a real job (I develop for the company but it isn't what they pay me to
do), but I will throw something together when I get a little time today.
Bob S
> On Oct 19, 2018, at 06:59 , Sannyasin Brahmanathaswami via use-livecode
> wrote:
>
> Wow! that very cool
>
> Can you post a sample
Wow! that very cool
Can you post a sample stack, or snippet of code for this
"Just by passing the long ID, instead of a string of parameters. It's like a
package of variables, AND the variables are persistent between sessions."
BR
On 10/16/18 5:13 AM, Bob Sneidar via use-livecode wrote:
> For
Not to mercilessly flog an expired Equine, but one of the great things about
custom properties, is that you can pass the long ID of an object to a command
or function (think behaviors), and so reference it's custom properties in said
command or function. Essentially this behaves as group of vari
"...Well, I just gave up on using custom properties completely. Probably not
the right thing to do, but it works for me. "
Alex.
Really? You abandoned custom properties? I cannot live without them, though
I rarely use the setProp and getProp control structures.
Craig Newman
--
Sent from:
ht
I don't know of a way to intercept them, and I did look, because I
have/had exactly the same problem.
I wrote a script (ExplicitProperties) which does a decent, but
imperfect, attempt to find places you have referenced a customprop, and
checks whether it is a "known" one. That was back in 2012
I don't know.
BUT, you can open up the properties palette and manually delete custom
props.
I'm sorry, I know that's a bit of a pain in the bum
Richmond.
On 16.10.18 г. 10:49 ч., Neville Smythe via use-livecode wrote:
Is there any way to intercept setProp messages for properties you *don’t*
Is there any way to intercept setProp messages for properties you *don’t* want
to set?
I find with my poor typing skills I keep typing
Set the of
where NonexistentProperty is a mistype of SomePropertyWhichHasASetPropHandler
and so I keep creating lots of superfluous properties for the object
Thanks. I knew I was missing something obvious!
Pete Haworth
On Jan 14, 2011, at 10:42 AM, dunb...@aol.com wrote:
> Ask for the target in your handler.
>
> on mouseUp
> set the superDuper of this card to ""
> end mouseUp
>
> on setProp superDuper
> put the target
> end setProp
> _
Ask for the target in your handler.
on mouseUp
set the superDuper of this card to ""
end mouseUp
on setProp superDuper
put the target
end setProp
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsub
I'm probably missing something obvious here but in a setprop or getprop
handler, how can I find out the object whose property is being set/get,
assuming the getprop/setprop is not in property owner's script?
For example, if I have the following line of code in a script:
put the xyz of field "a
13 matches
Mail list logo
