That make good sense
I may use it some day. It would allow more handlers in a common back
script/library that did the same thing (anything) when called from
different modules (stacks)
On 11/1/18 10:02 AM, Bob Sneidar via use-livecode wrote:
> Well the big thing it deals with is ambiguity. I have
That should have been the full path to the stack.
Bob S
> On Nov 1, 2018, at 13:02 , Bob Sneidar via use-livecode
> wrote:
>
> put getParentStack(tParentCard) into tParentStack -- returns the long id of
> the parent stack
___
use-livecode mailing
Well the big thing it deals with is ambiguity. I have a number of substacks
which are similar, like data entry forms for different tables in the database,
and these have many controls, properties and scripts in common, but also some
that are unique to that particular form. If only one of these "
Bob, that make sense. But why do need those handlers?
What not just use "of this stack"?
Obviously, I am oblivious to the number contexts where you require:
"...created handlers that return the parent card or stack of an object."
I am curious what they are?
BR
Bob Sneidar via use-livecode w
Me is resolving correctly for me in stack, card and behavior scripts attached
to them. The issue I think was that you cannot seem to reference card of me
in a stack script handler. So I created handlers that return the parent card or
stack of an object. The object can be the long id of a card e
A guess: "me" resolves correctly for controls only. Stacks and cards are
not controls, so behaviors attached to those resolve to the behavior script
itself. Since there are no cards in a behavior script, it fails. Maybe.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software |
It's not a bug, it's a limitation (probably the wrong word) of the parser. As
has been talked about in the past, messing with the parser is one of the least
desirable things the devs have to do, and from what I have gleaned, they avoid
it if at all possible. The parser is really where all the LC
Hmm, is that a bug? Should we report it? I think so.
On 10/30/18 5:54 AM, Bob Sneidar via use-livecode wrote:
> Ah yes I've encountered this. What I do is I have 2 functions:
> getParentCard() and getParentStack(). pass the long id of any object on a
> card and they return the long id of the
Ah yes I've encountered this. What I do is I have 2 functions: getParentCard()
and getParentStack(). pass the long id of any object on a card and they return
the long id of the card, or the long filename of the stack respectively. Then
you can use go tParentCard and that will compile. Your issue
On 10/29/18 7:42 PM, Tom Glod via use-livecode wrote:
> oh...didn't know that syntax would work first thing that jumped out at
> me thought maybe it was as simple as that. :)
You learn as you go, with the plug in TinyDictionary.
I refer to it all the time...
Best way to access the dic
oh...didn't know that syntax would work first thing that jumped out at
me thought maybe it was as simple as that. :)
On Mon, Oct 29, 2018 at 8:15 PM, Sannyasin Brahmanathaswami via
use-livecode wrote:
> @tom go card and go to card same thing.
>
> @ bob
>
> That's what I understand (as
@tom go card and go to card same thing.
@ bob
That's what I understand (as you have described it)
-- The behavior is set in the properties of a stack.
-- the SE suggestions "knows" this and on typing
go card...[List of cards in current stack appears... choose one)
# you get:
go card "my
Me always refers to the object the script belongs to. It doesn't matter which
handler it is. A script running in a behavior is like running an instance of
the target object (the object with the behavior set). This allows for multiple
objects with the same behavior (think datagrids calling get th
the first version said "go card" not "go to card" :)
On Mon, Oct 29, 2018 at 11:14 AM, Sannyasin Brahmanathaswami via
use-livecode wrote:
> I thought I had a grip on "me"
>
> But in a script that is assigned to a stack, one assumes that "me"
> refers to stack itself.
> But the auto-suggestion on
I thought I had a grip on "me"
But in a script that is assigned to a stack, one assumes that "me"
refers to stack itself.
But the auto-suggestion on the SE popup menu generates an error on the
following line:
*
on openstack
put url ("binfile:" & path_Modules()& "listen/collection.json") into
tC
15 matches
Mail list logo
