Lagi Pittas wrote:
> 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 p
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
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 wrote:
>
> Hi monte
>
> I'm sure we would find a use case for it as we have/had that in
Agree. Data binding is a good use case for me as well.
Best, je...@botz.live
On Aug 19, 2016, 1:29 AM -0500, Iphonelagi , 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 allo
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 do
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
