(Slightly out of line, I'm just trying to tie the above two responses
together)
On Wed, 2012-07-11 at 15:39 +0200, Benoît Minisini wrote:
>
> The "group" name is the event name as specified at object creation.
>
> In other words, the compiler transforms
>
> { mnuGroup Menu
>...
>{ mnuGr
(Slightly out of line, I'm just trying to tie the above two responses
together)
On Wed, 2012-07-11 at 15:39 +0200, Benoît Minisini wrote:
>
> The "group" name is the event name as specified at object creation.
>
> In other words, the compiler transforms
>
> { mnuGroup Menu
>...
>{ mnuGr
Problem fixed in revision #4943.
2012/7/11 Antonio Carlos Siqueira
> sory, this is the sources.
>
> # Gambas Form File 3.0
>
> { Form Form
>MoveScaled(0,0,33,46)
>{ save Button
> MoveScaled(4,39,10,4)
> Text = ("Save")
>}
>{ TextArea1 TextArea
> MoveScaled(3,3,27,3
>
> Aha! Solved it by using an observer in the class that manages my
> dynamic menus.
>
> Gambas is such a thing of beauty. :-)
>
You can do it without an Observer, too. Observers duplicate events to there
could be some overhead
with this solution (unless that behaviour is desired) - besides
Le 11/07/2012 05:12, Bruce a écrit :
> On Tue, 2012-07-10 at 18:57 +0200, Tobias Boege wrote:
>> On Tue, 10 Jul 2012, Bruce wrote:
>>> The menu editor exposes (what looks like) a property called "Group" and
>>> if it is set I can use that name instead of the actual menu name in the
>>> event handle
sory, this is the sources.
# Gambas Form File 3.0
{ Form Form
MoveScaled(0,0,33,46)
{ save Button
MoveScaled(4,39,10,4)
Text = ("Save")
}
{ TextArea1 TextArea
MoveScaled(3,3,27,34)
}
{ open Button
MoveScaled(16,39,14,4)
Text = ("Re Open")
}
}
' Gamba
