[Kicad-developers] EESchema: regression in object moving?

2017-12-17 Thread Jeff Young
Has anyone noticed that dragging an object in EESchema doesn’t erase the old 
images (it just smears the canvas each time its redrawn during the drag 
operation)?
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] macOS 3d-viewer improvements

2017-12-17 Thread Bernhard Stegmaier
Hi Wayne,

sorry, I obviously have copied a wx-3.1 only constructor.
Please try attached patches.


Thanks,
Bernhard



0001-Create-HIDPI_GL_CANVAS-wrapper-for-transparent-wxGLC.patch
Description: Binary data


0002-Merge-HIDPI_GL_CANVAS-wrapper-with-OPENGL_GAL-implem.patch
Description: Binary data


0003-Fix-macOS-pinch-to-zoom-for-3d-viewer.patch
Description: Binary data


0004-Remove-wx-3.1-only-constructor-from-HIDPI_GL_CANVAS-.patch
Description: Binary data



> On 15. Dec 2017, at 23:08, Wayne Stambaugh  wrote:
> 
> Bernhard,
> 
> Your patch set fails to build on Linux (Debian testing) with the
> following build errors:
> 
> In file included from
> /home/wayne/src/kicad/kicad-trunk/common/gal/hidpi_gl_canvas.cpp:27:0:
> /home/wayne/src/kicad/kicad-trunk/include/gal/hidpi_gl_canvas.h:45:22:
> error: ‘wxGLAttributes’ does not name a type; did you mean
> ‘wxVisualAttributes’?
>const wxGLAttributes& dispAttrs,
>  ^~
>  wxVisualAttributes
> /home/wayne/src/kicad/kicad-trunk/common/gal/hidpi_gl_canvas.cpp:31:18:
> error: ‘wxGLAttributes’ does not name a type; did you mean
> ‘wxVisualAttributes’?
>const wxGLAttributes& dispAttrs,
>  ^~
>  wxVisualAttributes
> /home/wayne/src/kicad/kicad-trunk/common/gal/hidpi_gl_canvas.cpp: In
> constructor ‘HIDPI_GL_CANVAS::HIDPI_GL_CANVAS(wxWindow*, const int&,
> wxWindowID, const wxPoint&, const wxSize&, long int, const wxString&,
> const wxPalette&)’:
> /home/wayne/src/kicad/kicad-trunk/common/gal/hidpi_gl_canvas.cpp:38:72:
> error: invalid conversion from ‘wxWindowID {aka int}’ to ‘const int*’
> [-fpermissive]
> wxGLCanvas( parent, dispAttrs, id, pos, size, style, name, palette )
>^
> In file included from /usr/include/wx-3.0/wx/glcanvas.h:195:0,
> from
> /home/wayne/src/kicad/kicad-trunk/include/gal/hidpi_gl_canvas.h:30,
> from
> /home/wayne/src/kicad/kicad-trunk/common/gal/hidpi_gl_canvas.cpp:27:
> /usr/include/wx-3.0/wx/gtk/glcanvas.h:23:5: note:   initializing
> argument 3 of ‘wxGLCanvas::wxGLCanvas(wxWindow*, wxWindowID, const int*,
> const wxPoint&, const wxSize&, long int, const wxString&, const wxPalette&)’
> wxGLCanvas(wxWindow *parent,
> ^~
> common/CMakeFiles/gal.dir/build.make:422: recipe for target
> 'common/CMakeFiles/gal.dir/gal/hidpi_gl_canvas.cpp.o' failed
> make[2]: *** [common/CMakeFiles/gal.dir/gal/hidpi_gl_canvas.cpp.o] Error 1
> make[2]: *** Waiting for unfinished jobs
> In file included from
> /home/wayne/src/kicad/kicad-trunk/include/gal/opengl/opengl_gal.h:41:0,
> from
> /home/wayne/src/kicad/kicad-trunk/common/gal/opengl/opengl_gal.cpp:29:
> /home/wayne/src/kicad/kicad-trunk/include/gal/hidpi_gl_canvas.h:45:22:
> error: ‘wxGLAttributes’ does not name a type; did you mean
> ‘wxVisualAttributes’?
>const wxGLAttributes& dispAttrs,
>  ^~
>  wxVisualAttributes
> In file included from
> /home/wayne/src/kicad/kicad-trunk/include/gal/opengl/opengl_gal.h:41:0,
> from
> /home/wayne/src/kicad/kicad-trunk/common/draw_panel_gal.cpp:37:
> /home/wayne/src/kicad/kicad-trunk/include/gal/hidpi_gl_canvas.h:45:22:
> error: ‘wxGLAttributes’ does not name a type; did you mean
> ‘wxVisualAttributes’?
>const wxGLAttributes& dispAttrs,
>  ^~
>  wxVisualAttributes
> common/CMakeFiles/gal.dir/build.make:446: recipe for target
> 'common/CMakeFiles/gal.dir/gal/opengl/opengl_gal.cpp.o' failed
> make[2]: *** [common/CMakeFiles/gal.dir/gal/opengl/opengl_gal.cpp.o] Error 1
> common/CMakeFiles/gal.dir/build.make:86: recipe for target
> 'common/CMakeFiles/gal.dir/draw_panel_gal.cpp.o' failed
> make[2]: *** [common/CMakeFiles/gal.dir/draw_panel_gal.cpp.o] Error 1
> CMakeFiles/Makefile2:360: recipe for target
> 'common/CMakeFiles/gal.dir/all' failed
> make[1]: *** [common/CMakeFiles/gal.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs
> In file included from
> /home/wayne/src/kicad/kicad-trunk/common/../3d-viewer/3d_viewer/../3d_canvas/eda_3d_canvas.h:39:0,
> from
> /home/wayne/src/kicad/kicad-trunk/common/../3d-viewer/3d_viewer/eda_3d_viewer.h:37,
> from
> /home/wayne/src/kicad/kicad-trunk/pcbnew/basepcbframe.cpp:42:
> /home/wayne/src/kicad/kicad-trunk/include/gal/hidpi_gl_canvas.h:45:22:
> error: ‘wxGLAttributes’ does not name a type; did you mean
> ‘wxVisualAttributes’?
>const wxGLAttributes& dispAttrs,
>  ^~
>  wxVisualAttributes
> common/CMakeFiles/pcbcommon.dir/build.make:180: recipe for target
> 'common/CMakeFiles/pcbcommon.dir/__/pcbnew/basepcbframe.cpp.o' failed
> make[2]: ***
> 

[Kicad-developers] Jenkins build is back to normal : kicad-qa #3181

2017-12-17 Thread Miguel Angel Ajo
See 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] eeschema regression

2017-12-17 Thread Nick Østergaard
I am not sure why, but I see the progress dialog opened for an equal amount
of time every time in my case. Testing on windows 10.

The path Seth proposed seem to work sort of. But it does not show the
loading dialog on init and I get an error dialog shortly after I open
eeschema that it fails to load a dcm file. This error does not occur
without Seths patch.

But on subsequent additions of a symbol the dialog is not shown and with no
delay as expected.

2017-12-16 23:52 GMT+01:00 Oliver Walters :

> Wayne,
>
> I believe you are correct, they are cached and the progress dialog is the
> actual source of the perceived delay. If this dialog is only shown on first
> library load that would be sufficient.
>
> On Sun, Dec 17, 2017 at 12:40 AM, Wayne Stambaugh 
> wrote:
>
>> Are you sure the libraries are actually being reloaded?  The behavior I
>> observe is the first time I open the symbol chooser, the progress dialog
>> is open for a significant amount of time while the libraries are being
>> loaded.  On all subsequent openings of the symbol chooser, the progress
>> dialog is dismissed very quickly indicating that the libraries have
>> already been cached.  I agree that the progress dialog being displayed
>> every time the symbol chooser is opened is annoying.  I probably merged
>> this patch too quickly.  After the initial loading of all of the symbol
>> libraries, the progress dialog doesn't need to be shown.
>>
>> On 12/15/2017 09:10 PM, Oliver Walters wrote:
>> > I think that there has been a functional regression in a recent build,
>> > relating to placing symbols in eeschema.
>> >
>> > Previously, the libraries were loaded once when the schematic was
>> opened.
>> >
>> > now, the entire symbol library set is re-loaded every time you select
>> > "Place Symbol". This brings up the "loading symbol libraries" progress
>> > dialog before opening the component selector window.
>> >
>> > This is very tedious - especially on Windows where loading symbols can
>> > be an order of magnitude slower than linux. It really interrupts work
>> flow.
>> >
>> > I do not imagine this is intended behaviour? Can anyone comment on this?
>> >
>> > Oliver
>> >
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


[Kicad-developers] Build failed in Jenkins: kicad-qa #3180

2017-12-17 Thread Miguel Angel Ajo
See 

Changes:

[Maciej Suminski] Eagle Schematic Import: try harder to generate a meaningful 
library name

[Maciej Suminski] Eagle Schematic Import: fixed imported libraries location

[Maciej Suminski] Implemented std::hash specialization

[Maciej Suminski] Eagle Schematics Importer: support for UTF-8

--
[...truncated 2.09 KB...]
-- Python module install path: lib/python2.7/dist-packages
-- wxPython version 3.0 found.
-- S3DSG version: 2.0.0
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Configuring done
-- Generating done
-- Build files have been written to: 

+ echo CMAKE exit code is 0
CMAKE exit code is 0
+ rm -f pcbnew/pcbnewPYTHON_wrap.cxx
+ env
+ grep -q ^MAKEJOBS=
+ echo The MAKEJOBS variable is empty
The MAKEJOBS variable is empty
+ JOBS=4
+ make -j4 pcbnew_python_module
[  1%] Built target netlist_lexer_source_files
[  1%] [  1%] Built target page_layout_lexer_source_files
Generating version string header
[  1%] Built target idf3
-- Using Git to determine build version string.
-- Found Git: /usr/bin/git (found version "2.1.4") 
-- Git hash: 3f68af177ad649fcd7479b3888a0a12e22c65720
-- Git branch: HEAD
-- Writing 
 file with 
version: (2017-12-17 revision 3f68af1)-HEAD
[  1%] [  1%] Built target lib_table_lexer_source_files
Built target version_header
[  1%] Built target pcb_lexer_source_files
[ 44%] Built target bitmaps
[ 44%] Built target pcb_plot_lexer_source_files
[ 46%] Built target kicad_3dsg
[ 46%] Built target lib_dxf
[ 46%] Built target specctra_lexer_source_files
Scanning dependencies of target polygon
[ 46%] [ 46%] Building CXX object 
polygon/CMakeFiles/polygon.dir/math_for_graphics.cpp.o
Building CXX object polygon/CMakeFiles/polygon.dir/PolyLine.cpp.o
Scanning dependencies of target gal
[ 46%] Building CXX object common/CMakeFiles/gal.dir/basic_gal.cpp.o
Scanning dependencies of target pcbcommon
[ 46%] Building CXX object common/CMakeFiles/pcbcommon.dir/base_screen.cpp.o
[ 46%] Building CXX object common/CMakeFiles/pcbcommon.dir/eda_text.cpp.o
[ 46%] Building CXX object common/CMakeFiles/gal.dir/draw_panel_gal.cpp.o
[ 46%] Building CXX object common/CMakeFiles/pcbcommon.dir/class_page_info.cpp.o
Linking CXX static library libpolygon.a
[ 46%] Built target polygon
[ 46%] Building CXX object common/CMakeFiles/pcbcommon.dir/lset.cpp.o
[ 46%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/basepcbframe.cpp.o
: In 
constructor ‘PAGE_INFO::PAGE_INFO(const wxString&, bool)’:
:111:62: 
warning: declaration of ‘IsPortrait’ shadows a member of 'this' [-Wshadow]
 PAGE_INFO::PAGE_INFO( const wxString& aType, bool IsPortrait )
  ^
: In member 
function ‘bool PAGE_INFO::SetType(const wxString&, bool)’:
:117:65: 
warning: declaration of ‘IsPortrait’ shadows a member of 'this' [-Wshadow]
 bool PAGE_INFO::SetType( const wxString& aType, bool IsPortrait )
 ^
[ 46%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/board_items_to_polygon_shape_transform.cpp.o
[ 47%] Building CXX object common/CMakeFiles/gal.dir/painter.cpp.o
[ 47%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/board_commit.cpp.o
[ 47%] Building CXX object common/CMakeFiles/gal.dir/worksheet_viewitem.cpp.o
[ 47%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_board.cpp.o
[ 47%] Building CXX object common/CMakeFiles/gal.dir/origin_viewitem.cpp.o
[ 47%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_board_connected_item.cpp.o
[ 49%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_board_design_settings.cpp.o
[ 49%] Building CXX object 
common/CMakeFiles/gal.dir/gal/graphics_abstraction_layer.cpp.o
[ 49%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_board_item.cpp.o
[ 49%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_dimension.cpp.o
[ 49%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_drawsegment.cpp.o
[ 49%] Building CXX object common/CMakeFiles/gal.dir/gal/stroke_font.cpp.o
[ 49%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_drc_item.cpp.o
[ 49%] Building CXX object 

Re: [Kicad-developers] P-Cad patch

2017-12-17 Thread Eldar Khayrullin

Thank you for merging.
In future you can use PCAD2006 Viewer [1] for testing. It is freeware 
software [2].


[1] http://downloads.altium.com/P-CAD/PCAD2006_Viewer_19.02.9660.zip
[2] http://techdocs.altium.com/display/ALEG/Legacy+Downloads+for+P-CAD

В Воскресенье, 17 дек. 2017 в 1:33 П. П., Maciej 
Suminski  написал:

Hi Eldar,

No, you are not in a spam list. Unfortunately, there are times when I
cannot work on KiCad, so it happens that a patch is not merged
instantly. I have never committed a patch without reading and testing 
it

first and it takes time too. Please be patient.

Having said that, I have just read your patches and tested them with a
limited set of P-Cad files I have. I do not have P-Cad to verify the
imported results, so I simply trust you about the changes. Thank you 
for

your contribution, your patches have been merged.

Regards,
Orson

On 12/17/2017 08:09 AM, Eldar Khayrullin wrote:

 Am I in a spam list?

 В Суббота, 16 дек. 2017 в 3:33 П. П., Eldar Khayrullin
  написал:

 Rebased patches.

 В Четверг, 14 дек. 2017 в 9:00 П. П., Maciej Suminski
  написал:
 Thank you for quick tests, I have just pushed both patches to the 
master

 branch. Regarding the previous patches - I checked the bug reports
 tagged 'pcad' and browsed the mailing list, but I could not find 
any

 patch that had not been applied. Would you point me to them?

 Regards,
 Orson

 On 12/14/2017 06:09 PM, Eldar Khayrullin wrote:
  Hi. I tested your patch. But found another one warning (see my 
patch).

  What about my previous patches for PCAD import improvement?

  В Четверг, 14 дек. 2017 в 6:11 П. П., Maciej 
Suminski

   написал:

  Hi Eldar,

  I have an impression that you are one of the main P-Cad 
importer

 users.
  Would you test the attached patch? It fixes a number of 
warnings

 in the
  P-Cad importer plugin, but I do not have any files to verify 
the

 code.

  Thank you,
  Orson




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] P-Cad patch

2017-12-17 Thread Maciej Suminski
Hi Eldar,

No, you are not in a spam list. Unfortunately, there are times when I
cannot work on KiCad, so it happens that a patch is not merged
instantly. I have never committed a patch without reading and testing it
first and it takes time too. Please be patient.

Having said that, I have just read your patches and tested them with a
limited set of P-Cad files I have. I do not have P-Cad to verify the
imported results, so I simply trust you about the changes. Thank you for
your contribution, your patches have been merged.

Regards,
Orson

On 12/17/2017 08:09 AM, Eldar Khayrullin wrote:
> Am I in a spam list?
> 
> В Суббота, 16 дек. 2017 в 3:33 П. П., Eldar Khayrullin
>  написал:
>> Rebased patches.
>>
>> В Четверг, 14 дек. 2017 в 9:00 П. П., Maciej Suminski
>>  написал:
>>> Thank you for quick tests, I have just pushed both patches to the master
>>> branch. Regarding the previous patches - I checked the bug reports
>>> tagged 'pcad' and browsed the mailing list, but I could not find any
>>> patch that had not been applied. Would you point me to them?
>>>
>>> Regards,
>>> Orson
>>>
>>> On 12/14/2017 06:09 PM, Eldar Khayrullin wrote:
  Hi. I tested your patch. But found another one warning (see my patch).
  What about my previous patches for PCAD import improvement?

  В Четверг, 14 дек. 2017 в 6:11 П. П., Maciej Suminski
   написал:
>  Hi Eldar,
>
>  I have an impression that you are one of the main P-Cad importer
> users.
>  Would you test the attached patch? It fixes a number of warnings
> in the
>  P-Cad importer plugin, but I do not have any files to verify the
> code.
>
>  Thank you,
>  Orson

> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] Symbol library descriptions

2017-12-17 Thread jp charras
Le 17/12/2017 à 00:05, Oliver Walters a écrit :
> I think it would be useful if the sym-lib-table entry descriptions could be 
> used within KiCad -
> perhaps in the component selector tree view?
> 
> For example, if a top-level item (library) is selected, display the text in 
> the sym-lib-table in the
> bottom-left panel?
> 
> 
> Inline image 1
> 
> AFAIK this descriptive text is not displayed anywhere outside the library 
> table editor window.
> 

This is a good idea.


-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] [PATCH] Wire-bus entry dangling points

2017-12-17 Thread Andrey Kuznetsov
Anyone else thinks the green wire bus entries should be blue and the wire
bus entry connection with a wire should have a junction?
>From that image, who is to say the wire and wire-entry, both green, do not
connect to the blue line twice, just look at the triangles that have been
made in the 2nd screenshot.

On Fri, Dec 15, 2017 at 10:15 AM, Seth Hillbrand 
wrote:

> The attached patch adjusts how dangling ends are shown for wire-bus
> entries to correct the behavior Nick reported.
>
> Previously, wire-bus entries were shown as dangling if there was a wire or
> a bus at both ends.  This broke in the case of the Coldfire demo where a
> bus was drawn over a wire and there was also an entry point (see attached
> image coldfire-broken.png).
>
> The patch implements the logic that if there is _at least_ a wire and a
> bus at each end, that the entry is considered not dangling. (see attached
> image coldfire-fixed.png)
>
> -Seth
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Remember The Past, Live The Present, Change The Future
Those who look only to the past or the present are certain to miss the
future [JFK]

kandre...@gmail.com
Live Long and Prosper,
Andrey
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp