Coming in late on this (at a conference for 3 days) but I have a couple of
virtual property handlers that address some of these issues. The robustID
getProp returns the kind of string that behavior references need.
getProp robustID
a virtual property
-- getting the lo
Doesn't address your issue, but I do have a free stack that is useful if
you need to make wholesale changes to a behavior id. You can search for
all objects with a string in the behavior and replace it with another.
If interested, its available at http://www.lcsql.com/free-stuff.html
Pete
lcSQL
Are you logged in? There's no downloads page until you login.
--
M E R Goulding
Software development services
mergExt - There's an external for that!
> On 25 Oct 2014, at 7:20 am, Bob Sneidar wrote:
>
> I do not see it there.
>
> Bob S
>
>
>> On Oct 23, 2014, at 21:50 , Monte Goulding
>>
I do not see it there.
Bob S
> On Oct 23, 2014, at 21:50 , Monte Goulding
> wrote:
>
>
> On this topic I just uploaded lcVCS 1.0.0 RC 1 to mergExt.com
>
> I will need to do a bit of work to make lcVCS fully LiveCode 7 compatible. My
> understanding is that for a time RunRev were using lcVC
On this topic I just uploaded lcVCS 1.0.0 RC 1 to mergExt.com
I will need to do a bit of work to make lcVCS fully LiveCode 7 compatible. My
understanding is that for a time RunRev were using lcVCS to help find bugs in 7
(it's really good at finding engine bugs) so hopefully it will work reasona
On 24 Oct 2014, at 11:58 am, Richard Gaskin wrote:
> Thanks for the info, Monte:
> > Behaviors are saved as an id and a stack name and no matter how
> > you set them that's what the internal reference is. lcVCS handles
> > behaviors fine (and image ids etc) as long as the stackFile
> > import/ex
Thanks for the info, Monte:
> Behaviors are saved as an id and a stack name and no matter how
> you set them that's what the internal reference is. lcVCS handles
> behaviors fine (and image ids etc) as long as the stackFile
> import/export order is right. It also has a plugin system to
> support l
On 24 Oct 2014, at 10:34 am, Richard Gaskin wrote:
> I wasn't aware that Monte had released a final version of that.
It's been in beta since January but with very few reports. Probably because
nobody is using it... Trevor, Martin, Myself and Todd could be it... I made a
couple of tweaks the
Todd Geist wrote:
> On Thu, Oct 23, 2014 at 11:45 AM, Richard Gaskin wrote:
>
>> If you're seeing ID numbers change when a stack is reconstructed
>> in lcVCS it's either a bug in LiveCode or lcVCS and should be
>> reported so it can be addressed.
>
> Monte's lcVCS still recommends using Name base
Monte's lcVCS still recommends using Name based references.
https://github.com/montegoulding/lcVCS
Todd
On Thu, Oct 23, 2014 at 11:45 AM, Richard Gaskin wrote:
> Todd Geist wrote:
> > Now why do I avoid IDs? The answer is version control. If you
> > use lcCVS that ID is probably not going to
Todd Geist wrote:
> Now why do I avoid IDs? The answer is version control. If you
> use lcCVS that ID is probably not going to be the same when you
> reconstitute the file.
The LiveCode engine was enhanced several versions ago to allow IDs to be
set, specifically to support the creation of suc
Hi Richard,
I can and do use dynamic assignments. But it's more boiler plate then I
would like. An object, once configured should just work. "Setup" steps
are too easy to forget in another context.
Now why do I avoid IDs? The answer is version control. If you use lcCVS
that ID is probably not
The dictionary gives no clue. Try the long name instead and see if it works.
Then you can tell us. :-)
Bob S
> On Oct 22, 2014, at 19:31 , Todd Geist wrote:
>
> Hello,
>
> I don’t like to use IDs to reference Objects. But it seems that the only way
> you can reference a Behavior is with it
Good to see you here, Todd -
> I don’t like to use IDs to reference Objects. But it seems that
> the only way you can reference a Behavior is with it’s ID. Is
> that true? Is there another way?
While long IDs are normally problematic since they include the file path
to the object (which will
was a more logical place.
Of course, the message hierarchy contains much of that functionality already.
Craig Newman
-Original Message-
From: Todd Geist
To: How to use LiveCode
Sent: Wed, Oct 22, 2014 10:32 pm
Subject: setting a behavior with out using an ID
Hello,
I don’t like to
Hello,
I don’t like to use IDs to reference Objects. But it seems that the only way
you can reference a Behavior is with it’s ID. Is that true? Is there another
way?
Thanks
Todd
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please vis
16 matches
Mail list logo