There is
#define STAND_ALONE 1 in layer_widget.cpp
which is typically commented out, due to this being used to enable a test
application that i assumed was used at first for designing the widget. Due
to insufficient includes this (test) code no longer works, should the code
just be removed or
On 12/11/2015 3:25 AM, Maciej Sumiński wrote:
> On 12/08/2015 09:57 PM, Wayne Stambaugh wrote:
> [snip]
>> I'm not the biggest github fan either. I think its OK but it was
>> expecting a lot more given all of the fan fair. I do like working with
>> git. I've been using it exclusively for my
I'll leave the decision to remove the /package folder up to the package
devs. If they are interested in keeping the platform specific package
build stuff in the kicad source repo, I'm OK with that. I know that
packaging stuff is maintained in the source tree by other projects.
The /new folder
I'll leave the decision to remove the /package folder up to the package
devs. If they are interested in keeping the platform specific package
build stuff in the kicad source repo, I'm OK with that. I know that
packaging stuff is maintained in the source tree by other projects.
The /new folder
Hello Kicad developers,
I have been a very long time follower of kicad and I think the work done
to it over the years is simply amazing.
I would love to contribute where I can.
I have had need to play with the python scripting of Kicad. Kicad uses
wxpython.
Wxpython includes within it, a
I second this suggestion. It's way nicer than the dinky little
Notepad-with-REPL we're using right now.
--
Chris
On Fri, Dec 11, 2015 at 10:57:26PM +0800, Strontium wrote:
> Hello Kicad developers,
>
> I have been a very long time follower of kicad and I think the work done to
> it over the
I am working on a couple of RF designs, proper layout requires the use
of "Via Curtains/Via Filling", Further they are HDI boards and I am
using both through-hole and micro vias.
I am aware of the "Pro Tip" which suggests simulating a via with a
component with a single pad. The "Pro-Tip"
Hi,
I've updated kicad to stable version 4.0.0 today, but I can't open pcbnew
or footprint editor anymore. Did anyone experience this issue? kicad.app,
eeschema, gerbview, pl_editor and pcb_calculator open fine.
This is the crash report I get, any help appreciated:
Jose
Process:
Yes, this is on the bug tracker.
This is probably the same issue as
https://bugs.launchpad.net/kicad/+bug/1522987.
I recompiled pixman and cairo on the build server multiple times from 11/16
to 11/19 for another issue. It fixed that issue, but some people, I'm not
sure who/why, have a different
On Dec 10, 2015, at 10:11 PM, Simon Richter wrote:
>
> Hi,
>
> I'm thinking about adding some support for pin and unit swapping. To
> make it maximally useful, I'd like to generate a list of alternative
> mappings inside the netlist, and add the actual swap
Not until after the new schematic and symbol library file formats are
implemented. Support for pin and unit swapping will be built in to the
new symbol library file format. I have attached the original file
format documents that I generated during our previous discussion.
Please look over them
We probably should make it work just in case we need to do some stand
alone debugging. Who knows what future versions of wxWidgets will throw
at us. It's a lot easier to debug the stand alone than loading Pcbnew
into a debugger.
On 12/11/2015 9:37 AM, Simon Wells wrote:
> There is
>
> #define
What say our Python devs. I'm fine with it assuming it doesn't break
anything (read all platforms).
On 12/11/2015 10:03 AM, Chris Pavlina wrote:
> I second this suggestion. It's way nicer than the dinky little
> Notepad-with-REPL we're using right now.
>
> --
> Chris
>
> On Fri, Dec 11, 2015
Hi Wayne,
On 11.12.2015 20:23, Wayne Stambaugh wrote:
> Not until after the new schematic and symbol library file formats are
> implemented. Support for pin and unit swapping will be built in to the
> new symbol library file format.
That would be fairly orthogonal to what I'm suggesting -- I'd
That looks right. Now to figure out what a better "more generic" set of
CFLAGS and CPPFLAGS we need...
On Fri, Dec 11, 2015 at 2:11 PM, Bernhard Stegmaier wrote:
> EXC_BAD_INSTRUCTION almost looks like maybe pixman chooses some
> CPU-dependant optimisation from the
On 12/08/2015 09:57 PM, Wayne Stambaugh wrote:
[snip]
> I'm not the biggest github fan either. I think its OK but it was
> expecting a lot more given all of the fan fair. I do like working with
> git. I've been using it exclusively for my Eeschema refactor work. Has
> anyone tried using the
16 matches
Mail list logo