On Wed, 27 Apr 2016, Richard Gaskin wrote:
I think Kevin said best back in August in a discussion of when to choose
LCS and LCB:
(snip)
Previously our primary choices were between LiveCode Script
and a lower level language such as C. Now we have a third
choice, an intermedi
Ali wrote...
>> put the keys of (the properties of the templatefield)
That works…tks
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.
Ali Lloyd wrote:
> On Thu, Apr 28, 2016 at 4:21 PM Richard Gaskin wrote:
>
>> Sannyasin Brahmanathaswami wrote:
>> > Hmmm I could have sworn this worked years ago:
>> >
>> > put the keys of templatefield
>> >
>> > But it doesn’t today… how to you see all the props for the
>> > template?
>>
>> Plea
I suspect
put the keys of (the properties of the templatefield)
is what you want.
On Thu, Apr 28, 2016 at 4:21 PM Richard Gaskin
wrote:
> Sannyasin Brahmanathaswami wrote:
> > Hmmm I could have sworn this worked years ago:
> >
> > put the keys of templatefield
> >
> > But it doesn’t today…
Sannyasin Brahmanathaswami wrote:
> Hmmm I could have sworn this worked years ago:
>
> put the keys of templatefield
>
> But it doesn’t today… how to you see all the props for the template?
Please try it in v8.0rc1 and if it fails submit your recipe in a bug
report.
--
Richard Gaskin
Fourth
Kevin: “Use them [widgets] only when really needed”
Ok that makes good sense that as a strategy
On 4/27/16, 10:41 AM, "use-livecode on behalf of Richard Gaskin"
wrote:
>They're
>easy enough to make in LC Script that the benefit of doing so is a
>non-brainer. For ad hoc gadgets, like an
Sannyasin Brahmanathaswami wrote:
> I’m still trying to wrap my head around the use cases where a widget
> will be clearly superior architecture.
Widgets are a great choice when you're making a GUI element you expect
to share with other developers for use across a wide range of
applications.
On 4/27/16, 5:38 AM, "use-livecode on behalf of Richard Gaskin"
wrote:
>A custom control is just a group of other controls put together to
>provide something, well, custom.
I would like to take this one step further if that does not overstep the scope
of this thread:
How easy or hard, is
Todd Fabacher wrote:
> I have a simple question. Sorry for my ignorance, but how does one
> create a Custom Control from a group? It seems to be just a group,
> but somehome there is a way to set the group to be a Custom Control.
> Is a "Custom Control" a defined stack in the Plugins folder?
A c
I have a simple question. Sorry for my ignorance, but how does one create
a Custom Control from a group? It seems to be just a group, but somehome
there is a way to set the group to be a Custom Control. Is a "Custom
Control" a defined stack in the Plugins folder?
Thanks for the help.
--Todd
_
10 matches
Mail list logo
