Le 18/06/2014 09:37, Jean-Samuel Reynaud a écrit :
> Hi,
>
> When not docked it's working for me:
>
> Ubuntu 12.04
> wx : 2.8.12.1
>
> Ok for this modification but I have a question:
> Why not remove this shortcut from the menu and put it only on the pcb
> edit frame (like T or M hotkey for exam
Hi,
When not docked it's working for me:
Ubuntu 12.04
wx : 2.8.12.1
Ok for this modification but I have a question:
Why not remove this shortcut from the menu and put it only on the pcb
edit frame (like T or M hotkey for example) ?
Is it because it remove the hotkey remind in the menu ?
Le 17/
Le 12/06/2014 17:14, Dick Hollenbeck a écrit :
> The keys I press when the focus is on the Python Scripting window seem to be
> filtered by
> some higher up handler in the pcbnew editor.
>
> For example, the 'o' key, and the 'x' key do not make it to the python
> console. They
> cause a tool ch
I have Ubuntu 14.04 with wx2.8.12 and the patch does not work.
On 06/13/2014 04:09 PM, Jean-Samuel Reynaud wrote:
>
> I had test this patch but unfortunately is not working for me:
> Ubuntu 12.04 (amd64)
> wx2.8.12 (default ubuntu version)
>
> I still have issue with x and o letter.
>
> Regards
I had test this patch but unfortunately is not working for me:
Ubuntu 12.04 (amd64)
wx2.8.12 (default ubuntu version)
I still have issue with x and o letter.
Regards
Le 13/06/2014 20:28, jp charras a écrit :
> Le 13/06/2014 15:39, Dick Hollenbeck a écrit :
>> The problem is made more difficult b
Le 13/06/2014 15:39, Dick Hollenbeck a écrit :
> The problem is made more difficult by the wxWindow hierarchy chosen. I don't
> know if it
> would be possible and easier if everything except the console wxWindow had a
> common
> wxPanel parent. That wxPanel injection might make the problem easi
The problem is made more difficult by the wxWindow hierarchy chosen. I don't
know if it
would be possible and easier if everything except the console wxWindow had a
common
wxPanel parent. That wxPanel injection might make the problem easier to solve,
but it
might not be possible with some chil
On 06/13/2014 08:15 AM, jp charras wrote:
> 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
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
FYI. The 'x' and 'o' could not be typed in Python Console Window under Windows.
But Alt codes Alt+0120 and Alt+0111 works.
Version: (2014-05-26 BZR 4890)-product Release buildwxWidgets: Version 3.0.0
(debug,wchar_t,compiler with C++ ABI 1002,GCC 4.8.1,wx containers,compatible
with 2.8)
Platform:
Hi,
As I understand 'x' and 'o' are global hotkeys (defined on menubar from
menubar_pcbframe.cpp:363) and
other keys (for example 'm') is defined only as hotkey in PCB_EDIT_FRAME
context).
Some solution can be:
- remove those global hotkey and define them only on PCB_EDIT_FRAME
context (but in thi
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.
___
Mailing list: https://la
I use the path to wx-config.
Its CMake variable name is wxWidgets_CONFIG_EXECUTABLE. This is typically
enough. But
with wxPython it gets harder.
On 06/12/2014 04:37 PM, Nick Østergaard wrote:
> Do you know is there is a cmake switch to use wx 2.8? I could not find
> a variable in CMakeCache.t
Do you know is there is a cmake switch to use wx 2.8? I could not find
a variable in CMakeCache.txt, only the include strings.
2014-06-12 23:27 GMT+02:00 Dick Hollenbeck :
> This fails. A difference is wx 2.8.12.
>
> Application: pcbnew
> Version: (2014-06-12 BZR 4942)-product Debug build
> wxWid
This fails. A difference is wx 2.8.12.
Application: pcbnew
Version: (2014-06-12 BZR 4942)-product Debug build
wxWidgets: Version 2.8.12 (release,Unicode,compiler with C++ ABI 1002,GCC
4.8.2,wx
containers,compatible with 2.6)
Platform: Linux 3.13.0-27-lowlatency x86_64, 64 bit, Little endian, wxG
I just compiled 4941 with all the scripting options enabled on my
Archlinux and I don't have that problem. I can type the whole
alphabet.
Version: (2014-06-12 BZR 4941)-kicad Release build
wxWidgets: Version 3.0.0 (debug,wchar_t,compiler with C++ ABI 1002,GCC
4.9.0,STL containers,compatible with 2
The keys I press when the focus is on the Python Scripting window seem to be
filtered by
some higher up handler in the pcbnew editor.
For example, the 'o' key, and the 'x' key do not make it to the python console.
They
cause a tool change in the pcbnew editor instead of allowing me add that
ch
17 matches
Mail list logo
