kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #13705
Re: Python Scripting Window event handling
-
To:
kicad-developers@xxxxxxxxxxxxxxxxxxx
-
From:
jp charras <jp.charras@xxxxxxxxxx>
-
Date:
Fri, 13 Jun 2014 15:15:57 +0200
-
In-reply-to:
<CAKLXgru=bmxSQrydd348ubhnPXNzxyDQNVtSqAqKMfcZUq4t5A@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
Le 13/06/2014 09:43, Brian Sidebotham a écrit :
> I know I had this same problem with the python console on Windows. I
> don't t think this is something that changed, I think it's always been
> there.
>
> I can test on Windows tonight for you and let you know.
>
> Best Regards, Brian.
This issue happens both on Windows and Linux (wxWidgets 3.0).
Perhaps a focus issue between the main frame and the python console,
related to hot-key accelerators in menu:
these 2 chars are the only 2 printable keys which are used as
accelerators in the main menu (see main menu/Place)
There are other accelerators but they are not printable (Ctrl Z, Ctrl Y
.. ), therefore you do not see they are not sent to the console (but you
can see they are "captured" by the main menu.
If in the hot-key editor, you change o or x to an other (printable) key,
the new key is no more usable in python console, but o or x become usable.
--
Jean-Pierre CHARRAS
Follow ups
References