Re: [Kicad-developers] PATCH: Footprint wizard helpers

11/09/14, 23:32, John Beard kirjoitti: > I also attach a follow-up patch (fpw-tests.diff) containing a really > basic test harness to run though a few footprints with pre-defined > parameters, save them to a PCB board and also optionally "rip" the > modules out to a .pretty directory. I use someth

Re: [Kicad-developers] New icons for KiCAD

Hello, Fabrizio, most of old icons was modified (pixel alignment, colors was corrected for use common color palette, resizing svg etc.). Doesn't remained unchanged icons (maybe a couple). All icons in new set are used (currently some icons are compiled but doesn't used). So I propose fully upgrade

Re: [Kicad-developers] New icons for KiCAD

Please let me know when the icon situation is clarified and I will merge the changes at that time. On 9/11/2014 2:34 PM, Fabrizio Tappero wrote: > Hello, > Kostantin, IS this icon set an update of the current one? In the > screenshot you attached shows some old icons in the top horizontal set. > C

Re: [Kicad-developers] PATCH: Footprint wizard helpers

I can confirm that applying the fpw-overhaul.diff fixes #1366299. 2014-09-11 22:32 GMT+02:00 John Beard : > Hi, > > I have a patch (fpw-overhaul.diff) for the Python footprint wizard > helpers. This adds a few more drawing functions, such as for circles, > and also uses a matrix-based transform st

[Kicad-developers] PATCH: Footprint wizard helpers

Hi, I have a patch (fpw-overhaul.diff) for the Python footprint wizard helpers. This adds a few more drawing functions, such as for circles, and also uses a matrix-based transform stack with greatly simplifies constructing footprints consisting of regularly spaced elements (e.g. in lines, grids, c

[Kicad-developers] I FOUND IT Was: How to track down an exception?

On Thu, Sep 11, 2014 at 08:48:44PM +0200, Lorenzo Marcantonio wrote: > Maybe some old style printf in RN_DATA::Add will help. They helped, and after a wild pointer chase I found the following: The bad_alloc was due a huge netcode found on the pads (it's used as an index in a vector and as a param

Re: [Kicad-developers] How to track down an exception?

On Thu, Sep 11, 2014 at 08:23:04PM +0200, jp charras wrote: > Do you have this bug with any board? with any footprint on board ? with > any footprint lib? with any footprint lib type (legacy, Kicad, Github)? I found the error sporadically on a couple board I'm working on, usually when importing

Re: [Kicad-developers] New icons for KiCAD

Hello, Kostantin, IS this icon set an update of the current one? In the screenshot you attached shows some old icons in the top horizontal set. Could you please clarify? Thanks On Sep 8, 2014 8:05 PM, "Барановский Константин" < baranovskiykonstan...@gmail.com> wrote: > 08.09.2014 20:03, Vesa Solon

Re: [Kicad-developers] How to track down an exception?

Le 11/09/2014 20:00, Lorenzo Marcantonio a écrit : > On Thu, Sep 11, 2014 at 01:00:52PM -0400, Carl Poirier wrote: >> Did you try with the option "allow_pretty_writing_to_this_dir" for the >> corresponding entry in the fp-lib-table ? This way, the writing should be >> saved locally in there, and ne

Re: [Kicad-developers] How to track down an exception?

On Thu, Sep 11, 2014 at 01:00:52PM -0400, Carl Poirier wrote: > Did you try with the option "allow_pretty_writing_to_this_dir" for the > corresponding entry in the fp-lib-table ? This way, the writing should be > saved locally in there, and next time you load the module, you should see > your chang

Re: [Kicad-developers] How to track down an exception?

Hi Lorenzo, Did you try with the option "allow_pretty_writing_to_this_dir" for the corresponding entry in the fp-lib-table ? This way, the writing should be saved locally in there, and next time you load the module, you should see your changes. There is more information about that in the document

Re: [Kicad-developers] Usability test.

On 9/11/2014 7:53 AM, Tim Hutt wrote: > On 10 September 2014 22:25, Javier Serrano > > wrote: > > Assuming I have correctly understood what you mean (English is not > my native language) I'd have to disagree with it. All the opinions I > have re

Re: [Kicad-developers] How to track down an exception?

On Thu, Sep 11, 2014 at 01:52:24PM +0200, Lorenzo Marcantonio wrote: > Still wrestling with the random fault when doing a module change. > Sometimes it segfaults, sometimes it throws a std:bad_alloc exception. > > Usually symptoms of an heap smash... Update: I finally found a way to throw it reli

Re: [Kicad-developers] Usability test.

On 10 September 2014 22:25, Javier Serrano wrote: > Assuming I have correctly understood what you mean (English is not my > native language) I'd have to disagree with it. All the opinions I have read > here seem to me as coming from people who are genuinely convinced of what > they are saying. Ev

[Kicad-developers] How to track down an exception?

Still wrestling with the random fault when doing a module change. Sometimes it segfaults, sometimes it throws a std:bad_alloc exception. Usually symptoms of an heap smash... However it's catched by wx and pops up a dialog: Unhandled exception class: St9bad_alloc what: std::bad_alloc Totally un