kicad-developers team mailing list archive

[Miguel Angel <miguelangel@xxxxxx>]

I'm still trying to assimilate what just happened.

It seems that, after several debugging sessions that took me nowhere, I *
rebooted* the
damn MacOSX,  and ...

mba:KiCad ajo$ ./eeschema.app/Contents/MacOS/eeschema
open HID: Apple Internal Keyboard / Trackpad
open HID: Apple Keyboard
snapToGrid: 1 , aHotkey:0 WXKSHIFT: 0, WXKCONTROL: 0
snapToGrid: 1 , aHotkey:0 WXKSHIFT: 0, WXKCONTROL: 0
snapToGrid: 1 , aHotkey:0 WXKSHIFT: 0, WXKCONTROL: 0
snapToGrid: 1 , aHotkey:0 WXKSHIFT: 0, WXKCONTROL: 0
snapToGrid: 1 , aHotkey:0 WXKSHIFT: 0, WXKCONTROL: 0

Now WXK_SHIFT and control are reported as "non pushed", so grid snap works
again...

so I will blame Darwin...

and bug is fixed with 0 patches.

Miguel Angel Ajo Pelayo
http://www.nbee.es
+34 636 52 25 69
skype: ajoajoajo


2013/9/16 Dick Hollenbeck <dick@xxxxxxxxxxx>

> On 09/16/2013 09:01 AM, Tomasz Wlostowski wrote:
> > On 09/16/2013 03:54 PM, Miguel Angel wrote:
> >> It really seems like a wx/MACOSX related bug to me,
> >>
> > Miguel,
> >
> > Welcome to the wonderful world of cross-platform compatibility of
> > wxWidgets. This is exactly why we (me & Orson) don't want to use any
> > sort of wx events in new tools.
> >
> > Cheers,
> > Tom
>
>
> I suspect that the wxWidgets team will continue to accept patches, given
> that they have
> more than 80,000 commits already into the project and it is still active.
>
>
> My guess is that KiCad will continue to use wxWidgets for some time, and
> that wxWidgets
> will continue to use wxEvents for some time.  Therefore, this has KiCad
> using wxEvents for
> some time.
>
>
> Regards,
>
> Dick
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>