kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

I'm not super interested in adding patches to the nightlies that aren't
accepted in core.  Right now, the trackpad patches aren't ready to be put
in core because they break some things in other platforms.

Adam Wolf
Cofounder and Engineer
W&L
On Mar 17, 2015 10:50 AM, "Bob Gustafson" <bobgus@xxxxxxx> wrote:

>  Hi Adam
>
>  As written in the kicad build documentation, I patched the
> wxPython/wxWidgets code and built that (also added the doPatch for the
> patch files that were not included in the virgin osx_build_wx.sh file). All
> patch files were used successfully (including the added ones -
> macos_scrolledwindow and macos_yosemite).
>
>  I also turned on most of the scripting build switches (why not..)
>
>  I used a custom kicad-configure.sh script to turn on these switches (see
> attached). From there it was just ‘make’ and ‘sudo make install’. No
> compile errors, but as I have reported before, lots of warnings and notes
> (using clang - which is also available on Fedora21)
>
> I have the console output saved from all of these steps if that would be
> of interest.
>
>  As you point out, the gesture/trackpad patches are not in the patches/
> directory, so were not included. These patch files could perhaps be
> included or not by commenting out appropriate doPatch lines in
> osx_build_wx.sh
>
>
> I tried your nightlies before, but didn’t see any trackpad panning
> improvement - will try again.
>
>  I will also try the nightly with Python support you mentioned in a
> previous email. I thought about that last night after I sent the email
> report.
>
>  My motivation is to get a working KiCad that I can use to build a board
> for a legacy piece of gear. I see these beautiful youtube videos of paired
> board traces and wiggly matched delay traces - am disappointed that I can’t
> have the same action on my OSX platform. Perhaps I should concentrate on my
> Fedora21 box instead, although it seems that the build instructions for
> that platform are more or less identical to OSX.
>
> I'm guessing that some of the OSX problems may be caused by a mix of
> carbon and cocoa library calls. Many of the error reports have carbon
> references. Also, try out the KiCad->About menu item.
>
>  I will fish around in the DEBUG folder and look for the Python support
> build.
>
>  Because of the clumsiness of scrollbars, having two finger panning is
> more or less essential on the OSX platform. When are you planning to try
> out those patches in your nightly builds? The OpenGL option, without
> scrollbars, needs those patches.
>
>  Thanks very much for your efforts all
>
>  Bob G
>
> On Mar 16, 2015, at 23:59, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>
> <adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> Hi Bob,
>
> Did you add any patches?  If you didn't, there definitely won't be any
> gesture/trackpad support.  It isn't ready for merging yet due to behavior
> on other platforms.
>
> Are you looking for issues or trying to get a usable KiCad?  If the
> latter, I suggest the nightlies.  I, and quite a few other people, use them
> to make real boards!  (There are even nightlies with Python support in the
> DEBUG folder.)
>
> Adam Wolf
> Cofounder and Engineer
> W&L
>
>
> On Mon, Mar 16, 2015 at 11:46 PM, Bob Gustafson <bobgus@xxxxxxx>
> <bobgus@xxxxxxx> wrote:
> Application: kicad
> Version: (2015-03-16 BZR 5522)-product Debug build
> wxWidgets: Version 3.0.2 (debug,UTF-8,compiler with C++ ABI
> 1002,GCC 4.2.1,STL containers,compatible with 2.8)
> Platform: Mac OS X (Darwin 14.1.0 x86_64), 64 bit, Little endian, wxMac
> Boost version: 1.57.0
>          USE_WX_GRAPHICS_CONTEXT=OFF
>          USE_WX_OVERLAY=ON
>          KICAD_SCRIPTING=ON
>          KICAD_SCRIPTING_MODULES=ON
>          KICAD_SCRIPTING_WXPYTHON=ON
>          USE_FP_LIB_TABLE=HARD_CODED_ON
>          BUILD_GITHUB_PLUGIN=ON
>          KICAD_USE_WEBKIT=ON
>
>
> pcbnewinitPythonScripting() failed (error 0: Undefined error: 0)
>
> ***** Error importing the wxPython API! ****                20:43:52
> pcbnewinitPythonScripting() failed: (error 0: Undefined error: 0)
>    20:43:52
>
> ----
>
> There are a number of other error conditions - see attached screen dumps
> and logs
>
> -----
>
> I see that the Contents/Contents typo was removed somewhere in
> the 5513-5522 changes.
>
> -----
>
> I am not able to pan anywhere using two finger gestures. When I try, the
> newPCB zooms in and out.
>
> Hope this is helpful
>
> Bob G
>
> _______________________________________________
> 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
>
>
>
>