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

[Bruce Steers <bsteers4@xxxxxxxxx>]

On Thu, 22 Jan 2026 at 02:55, Benoît Minisini <
benoit.minisini@xxxxxxxxxxxxxxxx> wrote:

> Le 22/01/2026 à 01:02, Benoît Minisini a écrit :
> >
> > It's more complex than that, because not everybody has the same keyboard
> > layout.
> >
> > It's what I said: "A" and "a" are two different keys in the toolkit
> > logic, whereas they are not on american and french keyboard (and
> > others), and so does the shortcut representation, which is then no
> > coherent anymore with 'Key.Code'.
> >
>
> The behaviour of 'Key.Send()' should have been fixed in the last commit.
> It should now understand the same shortcut syntax as the 'Key.Shortcut'
> property.
>
> Regards,
>
> --
> Benoît Minisini.


aaaah yes, perfect , much more compatible now.

I'm already finding it useful for other things :)

In my test program before using F3 to "search next" in a pre-loaded macro i
needed to first press Ctrl+F in the editor to open the search bar and then
enter a double quote and press return, then click back on the editor.
That puts the double quote in the search parameter for "find next" and puts
the cursor on the first quote.

That was as easy as this...

  TextEditor1.Goto(0, 0)
  TextEditor1.SetFocus

  ' open Find box and Wait for it to be active if not already done
  If Not Last.Tag Then
    Key.Send("Ctrl+f")
    Wait
    ' type '"' in the box and press return
    Key.Send("\"")
    Key.Send("Return")
    Last.Tag = True
    ' go back to editor
    TextEditor1.SetFocus
  Else
     Key.Send("F3")  ' search field is non-empty so just use F3
  Endif

I think this could be a very useful tool  :)
Thanks again , awesome stuff :)

Respects
BruceS