Hi,
I managed to find a workaround for Windows. I could not make dynamic
tree widget updates work correctly on Windows, at best I got duplicate
components and libraries whenever new entries are added. The only
solution that worked for me is to recreate the tree upon a change.
The price to pa
The attached patch fixes
https://bugs.launchpad.net/kicad/+bug/1167714
This happens when you drag a full line that is connected to a component.
Previously, the component would disconnect from any other lines as it was
dragged. Images documenting this are in the linked bug report
Best-
Seth
F
The attached patch fixes a minor issue in the Eeschema block selector code.
You can demonstrate the issue by placing a multi-pin component on your
schematic and then connecting multiple pins with wires. Next, drag the
component. Not all wires/junctions connected to your component will drag
(se
On Thu, Nov 16, 2017 at 1:42 AM, Wayne Stambaugh
wrote:
> Gentlemen,
>
> I'm not sure about breaking the library table file format for the
> version 5 release. If we do, the footprint library table will not be
> compatible with older versions. I would prefer that we push this change
> into vers
Thanks Wayne, I'm really pleased with how it is all turned out! Thanks to
all who assisted and guided.
On 16 Nov 2017 04:47, "Wayne Stambaugh" wrote:
> For those of you who have not seen the recent libraries section of the
> kicad website, I highly recommend you check it out when you get a
> c
Kudos to Oliver and everyone else to had a hand in that. I can't imagine
how much time it took to assemble all that information, write the tooling,
and to make it so aesthetically pleasing.
- Ben
On Wed, Nov 15, 2017 at 11:46 AM, Wayne Stambaugh
wrote:
> For those of you who have not seen the
On 15/11/17 18:38, Wayne Stambaugh wrote:
> It looks like the PCB_COLLECTOR objects are not swigged yet but that
> would be the way to do it. Properly swigged, there would be nothing
> preventing you from collecting all objects connected to an net or any
> other collection criteria for that matter
For those of you who have not seen the recent libraries section of the
kicad website, I highly recommend you check it out when you get a
chance. It is really well done. Hats off to the library development
team for their efforts to make this happen. Our libraries are really
nice thanks to their e
Adam,
Sounds like someone found some spare time! Thank you Adam for your
efforts. I appreciate the help. I'm sure our osx users do as well.
Cheers,
Wayne
On 11/14/2017 5:02 PM, Adam Wolf wrote:
> Hi folks!
>
> I have some things I've been working on for KiCad for quite a long
> time, and I'
It looks like the PCB_COLLECTOR objects are not swigged yet but that
would be the way to do it. Properly swigged, there would be nothing
preventing you from collecting all objects connected to an net or any
other collection criteria for that matter. That's what the collector
object is for. Let's
Where did you get your symbol library table file from?
${KICAD_SYS_SYMBOL_DIR} is not correct. It should be
${KICAD_SYMBOL_DIR}. This is the environment variable used in the
default library table at
https://github.com/KiCad/kicad-library/blob/master/template/sym-lib-table
On 11/15/2017 12:05 PM
please see KICAD_SYS_SYMBOL_DIR != KICAD_SYMBOL_DIR
> On 16/11/2017, at 06:05, Fabrizio Tappero wrote:
>
> Hi,
> I am not sure what the problem is but after a recent nightly build update I
> have lost all my schematic libs. This is the lib table config
>
>
>
> all lib files are in /usr/sh
On 15/11/17 15:37, miles mccoo wrote:
> Hello,
>
Hello Miles,
Thanks for the patch. My comments below:
>
> A couple code review type observations on the existing code.
>
> 1. The new connectivity stuff is in connectivity.h. Perhaps it should
> be called class_connectivity.h to match the n
Hi Orson,
I think you write this assuming the v5 file format will have
m_requiredVersion set to 5. If I recall correctly, we have decided to
use dates for file versioning and this method will be kept for v5 and
later versions, so we should be safe here.
if this the new Version policy I misse
I merged your patch into the development branch. Thank you for your
contribution to KiCad.
Cheers,
Wayne
On 11/12/2017 7:24 AM, Константин Барановский wrote:
> Remove inappropriate tooltip "Unload the selected library" from Remove
> button of Equ files dialog in CvPcb.
>
>
> _
Gentlemen,
I'm not sure about breaking the library table file format for the
version 5 release. If we do, the footprint library table will not be
compatible with older versions. I would prefer that we push this change
into version 6.
I'm OK with the progress dialog. If you split that out as se
Hi Maurice,
On 15/11/2017 1:21 PM, easyw wrote:
Just a clarification request:
Kicad Stable has version assigned to 4
Previous stable had version assigned to 3
I imagine that next stable would have version assigned to 5...
Am I right in supposing the next numbering release?
If I'm fine, with t
On 15/11/17 15:30, Maciej Suminski wrote:
> Hi Oliver,
>
> Thank you for restoring the progress bar dialog. While the library load
> time has recently decreased a lot, the UI freeze still happens with long
> library lists.
> Disclaimer: I have not looked at the code yet, I am just praising the ide
Hello,
This is my fourth patch to Kicad. Each of those instances have had process
errors, hopefully I'm not repeating any of those.
some time ago, the connectivity model of pcbnew was reworked to improve
ratsnest calculations.
One of the side effects of that change was that the Pads() api on net
Hi Oliver,
Thank you for restoring the progress bar dialog. While the library load
time has recently decreased a lot, the UI freeze still happens with long
library lists.
Disclaimer: I have not looked at the code yet, I am just praising the idea.
As you are looking on the Symbol Library Table
Le 15/11/2017 à 01:27, Seth Hillbrand a écrit :
> Attached is the updated line styles patchset. This implements the
> COLOR4D_PICKER_DIALOG and ensures
> that the alpha channel remains opaque.
>
> The dotted line, I agree doesn't look too dotted. This is the wxDOT style
> but apparently, it
>
Just a clarification request:
Kicad Stable has version assigned to 4
Previous stable had version assigned to 3
I imagine that next stable would have version assigned to 5...
Am I right in supposing the next numbering release?
If I'm fine, with the proposed patch the new stable release, if assig
22 matches
Mail list logo
