[Kicad-developers] "Save and Exit" problem?

2017-02-19 Thread Joseph Chen
Is it a know issue? Just compiled the latest and found "Save and Exit" is no longer saving the changes of not using the rescued parts. The net effect is that a new start keeps popping up "Rescue Helper" asking if to rescued the old parts from the old cache library. Here is the version info

[Kicad-developers] [PATCH] Swapping Part Editor Icon Order to be consistent to Footprint Editor

2017-02-19 Thread Joseph Chen
The attached patch is a very trivial change for swapping an icon order inside eeschema's part editor. This change will make the part editor to be consistent with the footprint editor's icon order. The issue, no mater how trivial it may be to other user, is that when editing a part, you need t

Re: [Kicad-developers] [PATCH] kicad: tree_project_frame: fixup drawframe style

2017-02-19 Thread Clemens Koller
Hi! Thanks! Well, removing wxSW_3D solves the flickering on Linux... wxNO_BORDER doesn't seem to do any effect here - can someone test this on the other platforms? : diff --git a/kicad/tree_project_frame.cpp b/kicad/tree_project_frame.cpp index a00bd98ee..ee9de0338 100644 --- a/kicad/tree_proje

Re: [Kicad-developers] [Kicad-lib-committers] Fwd: Footprint library developer notice.

2017-02-19 Thread Jan Krieger
Hi all! is the warning below still valid? JAN Am 27.01.2017 um 14:36 schrieb Nick Østergaard: Forwarding to kicad-lib-comitters. -- Forwarded message -- From: Wayne Stambaugh Date: 2017-01-27 14:23 GMT+01:00 Subject: [Kicad-developers] Footprint library developer notice. To:

Re: [Kicad-developers] [PATCH] hiding nets from ratsnest

2017-02-19 Thread Nick Østergaard
I know this is not directly related to the ratsnests, but it is highly related. Hmm, I am not sure how much value it makes to highlight the rastnest colors. But keep in mind the patch to add netclass coloring from a year ago: https://bugs.launchpad.net/kicad/+bug/1530637 Some nice screnshots: Ne

Re: [Kicad-developers] PANEL_PREV_3D_B

2017-02-19 Thread Chris Pavlina
On Sun, Feb 19, 2017 at 09:33:56AM +0100, jp charras wrote: > Le 19/02/2017 à 04:25, Chris Pavlina a écrit : > > In panel_prev_model.h, there is this line: > > > > #define PANEL_PREV_3D_B PANEL_PREV_3D > > > > After this, "PANEL_PREV_3D_B" is used in the code in place of > > "PANEL_PREV_3D". > >

Re: [Kicad-developers] RICHIO performance - 3 to 30 times slower than std::ifstream

2017-02-19 Thread Nox
Really good to know. Maybe these results should be noted down somewhere (code or guidelines?) so this information is not lost over time. Am 19.02.2017 um 10:27 schrieb John Beard: On Sat, Feb 18, 2017 at 1:08 AM, Nox wrote: What about wxFFileInputStream instead of wxFileInputStream? wxFFil

Re: [Kicad-developers] RICHIO performance - 3 to 30 times slower than std::ifstream

2017-02-19 Thread John Beard
On Sat, Feb 18, 2017 at 1:08 AM, Nox wrote: > What about wxFFileInputStream instead of wxFileInputStream? > wxFFileInputStream appears to be about 5-6 times faster than wxFileInputStream, but that's still much much slower than RICHIO or std::ifstream. $ qa/io_benchmark/io_benchmark /tmp/all.lib

Re: [Kicad-developers] [PATCH] kicad: tree_project_frame: fixup drawframe style

2017-02-19 Thread jp charras
Le 19/02/2017 à 00:00, Clemens Koller a écrit : > Thank you... I'll manage on my own, what's merged, then. > > I do test my stuff on Linux/X11/XFCE for now. Testing for Win7 is possible on > request. > > Clemens > On 2017-02-08 22:13, Clemens Koller wrote: > wxNO_BORDER and wxSW_3D see

Re: [Kicad-developers] Pushed new component selector

2017-02-19 Thread John Beard
On Sun, Feb 19, 2017 at 10:46 AM, Chris Pavlina wrote: > I just pushed the revamped component selector. > > Please, test thoroughly. Hi Chris, I get a bunch of asserts and then a crash on trying to place a part on an empty sheet. This on Linux on a few pull from LP. I have opened a bug for it t

Re: [Kicad-developers] PANEL_PREV_3D_B

2017-02-19 Thread jp charras
Le 19/02/2017 à 04:25, Chris Pavlina a écrit : > In panel_prev_model.h, there is this line: > > #define PANEL_PREV_3D_B PANEL_PREV_3D > > After this, "PANEL_PREV_3D_B" is used in the code in place of > "PANEL_PREV_3D". > ...WHY? > > Really...why?? > > I don't see any explanation for this bizarr