loadStack message use cases

Lagi Pittas iphonelagi at gmail.com
Fri Aug 19 11:16:01 EDT 2016


Well I'll go to the foot of our stairs! (said in a Graham Chapman Yorkshire
accent)

I never even thought to look if it was there,  otherwise I would have used
it. In the old days we would have an 800 page dead trees command / events
properties book which i would go through in a day or 2 just so I would know
what was available - just in case, I havent seen

Anyway does that mean if I put an an opencontrol method/command on a stack
or card or group  it will be fired by each control in succession if I don't
have an opencontrol within the control
and use "the target" as usual to see which one?

This opens up many possibilities if so ....

Thanks again.

Lagi

p.s.

I just did a test stack and it doesn't work the way I thought --- the event
only goes to a group, it  seems opencontrol and preopencontrol are not part
of the methods of controls but groups.
This means we  have to do a repeat loop of each control in the group to set
propertiesetc  if you need to so maybe this should be extended to objects.?


On 19 August 2016 at 07:34, Monte Goulding <monte at appisle.net> wrote:

> The solution for that would be extending preOpenControl, openControl and
> closeControl to all object types instead of just groups.
>
> Cheers
>
> Monte
>
> Sent from my iPhone
>
> > On 19 Aug 2016, at 4:28 PM, Iphonelagi <iphonelagi at gmail.com> wrote:
> >
> > Hi monte
> >
> > I'm sure we would find a use case for it as we have/had that in visual
> foxpro where each container form or control object had an init event which
> allowed setting Clours and code dynamically on creation ... Very powerful
> > If your in the system how about adding an. Init event as per the docs
> below from the vfp documentation
> > "
> > For form sets and other container objects, the Init events for all the
> contained objects are triggered before the container's Init event, so you
> can access the contained objects within the container's Init event. The
> Init event for each contained object occurs in the order it was added to
> the container object.
> > To prevent a control from being created, return false (.F.) from the
> Init event. The Destroy event will not be triggered. For example, the
> following code returns false (.F.) if the Invoice table is not available:"
> > I would be able to then be able to create  in effect a data binding
> system with much less code simulating the data environment of vfp on
> creation/init of the stack if it doesn't slow things down too much just put
> it in ... Simples! 😀
> > I have programmed round it so far but it would be a brilliant addition
> > Regards Lagi
> > Sent from my iPhone
> >
> >> On 18 Aug 2016, at 22:35, Monte Goulding <monte at appisle.net> wrote:
> >>
> >> Hi Folks
> >>
> >> I’m wondering if anyone with interest could post use cases they can
> think of for a loadStack message to the following bug report. This would be
> a message sent to a stack before preOpeStack when the stack is first loaded
> into memory. It’s possible that the only use cases are for the IDE.
> >>
> >> http://quality.livecode.com/show_bug.cgi?id=18223 <
> http://quality.livecode.com/show_bug.cgi?id=18223>
> >>
> >> Cheers
> >>
> >> Monte
> >> _______________________________________________
> >> use-livecode mailing list
> >> use-livecode at lists.runrev.com
> >> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> >> http://lists.runrev.com/mailman/listinfo/use-livecode
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode



More information about the Use-livecode mailing list