Re: Allow missing components (or detect them in project)

[Bruce Steers <bsteers4@xxxxxxxxx>]

Omg omg omg , Fantastic 😁

I'll start testing it as soon as I finish work 😎

Thank you so very much Benoit.

A superb addition to the gui suite 😎

Much respect
BruceS

On Wed, 21 Jan 2026, 08:20 Benoît Minisini, <
benoit.minisini@xxxxxxxxxxxxxxxx> wrote:

> Le 17/01/2026 à 17:48, Benoît Minisini a écrit :
> > Le 17/01/2026 à 16:59, Bruce Steers a écrit :
> >>
> >>     Why don't you just use an event observer to catch the keyboard
> >>     events on
> >>     the editor?
> >>
> >>     And in that cas which private variable would you need?
> >>
> >>     --     Benoît Minisini.
> >>
> >>
> >> It's not the getting of the event it's the giving.
> >>
> >
> > Ah, now I remember, we already talk about that. If I remember correctly,
> > I said that I should add a way inside the GUI component to inject a fake
> > keyboard event, so that you don't have to do any trick to make macros.
> >
> > Is there an issue tracker for that request? I don't think it's very
> > difficult to implement that. But of course the fake key event may be
> > available only locally, and for controls written in Gambas. I will see...
> >
> > Regards,
> >
>
> Hi,
>
> I have added 'Key.Send()' in the last commits, that send a fake keyboard
> event to the current active control (two actually, one 'KeyPress', and
> one 'KeyRelease').
>
> It takes a string shortcut as argument, something like that:
>
> Key.Send("A")
> Key.Send("é")
> Key.Send("CTRL+C")
> Key.Send("CTRL+ALT+DEL")
>
> You should pass it directly what you get from 'Key.Shortcut'.
>
> Normally, you should be able to get rid of a lot of hacks with that!
>
> Regards,
>
> --
> Benoît Minisini.
>
>
>