On Mar 30, 2016, at 9:53 AM, Richard Gaskin wrote:
> In all cases, once set a behavior is resolved to a "rugged long ID", a long
> ID where the stack portion is changed from the full file path as we normally
> find it to just the stack name, allowing portability.
>
> For example:
>
> button
Thank Mark... I had a chat with jacqueline... yes need to understand how these
behaviors are triggered.
meanwhile, in lc8 dp 15 I can't get a scriptonly stack behavior to work at all.
Still missing something mission critical here...
see other threadon "script only stack architecture"
On March
On 03/30/2016 01:07 PM, Sannyasin Brahmanathaswami wrote:
I tested this:
1) create script only stack with this script (this works if run from a button
on the card and a direct reference to the field name)
command centerTextVertically
put the formattedheight of me into tTotalTextHeight
@ Richard: doc on Git still leaves this use of stacks as behaviors quite opaque
for someone coming to it with no background. I suspect we only need about 5
more key sentences to get us to "aha! so that's how it works!"
Ditto Bill's question.
I tested this:
1) create script only stack with th
I’m wondering, does a script only behavior stack have to be loaded first with
“Start Using stack xyz” or once the behavior is set, LC automatically loads and
connects it to the control. What I’m thinking is that if a lot of behaviors are
used, and the appear in the project browser as stacks, the
NB the behavior entry in the dictionary has been rewritten and will be
correct in the next release of 8.0. You can check out the raw text of it
here if you want:
https://github.com/livecode/livecode/blob/develop/docs/dictionary/property/behavior.lcdoc
On Wed, Mar 30, 2016 at 2:53 PM Richard Gaskin
Sannyasin Brahmanathaswami wrote:
> Let's say we have a series of fields that have just a few words of
> text in them we want to center vertically. Text varies. Our designers
> may want to change the words over time. I don't want to have to go
> in and manually adjust the top and bottom margins t
This goes to the architecture discussion, but more to implemetation best
practices/methods, and not organization.
Let's say we have a series of fields that have just a few words of text in them
we want to center vertically. Text varies. Our designers may want to change the
words over time. I
