On 13/12/15 01:20, Wayne Stambaugh wrote:
I just tried this. Nice! This is definitely nicer than the Python
shell we are using. I'm with Nick, where's the patch?
On 12/12/2015 10:00 AM
Attached is A ROUGH PATCH, but its not correct yet. I am posting it for
comments, and maybe someone can he
Hello Jose,
If you could, please follow the bug on the bug tracker. In case you
didn't, please try this build (
http://downloads.kicad-pcb.org/osx/nightly/kicad-r6370.20151212-152723.dmg)
and please report if it fixes the issue for you.
Thank you.
Adam Wolf
On Sat, Dec 12, 2015 at 1:15 PM, Ada
Bens code looks good, and seems to do a lot that I am trying to achieve
with my python scripts. I am not sure what state its in with regard to
integrating it with the latest KiCad. But I would be keen to see it happen.
With regard to the patch I propose, the referenced code implements a
sche
Hi Steven,
Ben has developed some code for RF design...
https://lists.launchpad.net/kicad-developers/msg19528.html
https://lists.launchpad.net/kicad-developers/pngMPwkPIbzFA.png
may be you could work together for a merging patch :)
PS please keep me informed :)
On 12/12/2015 02.41, Strontium
Wayne, would you rather I make this change and submit an updated monolithic
patch (will take a few days), or would you rather I make a second patch on top
of this one to be applied in a second commit?
JP, the horizontal grid is already flexible, but the autoplacer doesn't do
vertical texts. How
This appears to be fixed.
> On Dec 12, 2015, at 11:09 AM, Nick Østergaard wrote:
>
> AFIK that issue has been fixed, but I don't really know for sure,
> since I don't have OS X.
>
> 2015-12-12 19:55 GMT+01:00 Adam Wolf :
>> Does this actually work with OS X in KiCad, or just in OS X in general?
I committed your patch in the product branch r6370. I tested it on
msys1/mingw32, msys2/mingw32, msys2/mingw64, and Debian testing without
issues. You should also be able to be more aggressive with your
optimization settings should you so desire. Please keep in mind, if you
do this and it breaks
Yeah. I will redo the cairo/pixman recompile soon, but I really think I
set it up the same way as I did in February when I rebuilt them.
I hope I'm not hitting a homebrew bug--but everything on that machine is
pretty heavily logged so I should have the information I need to fix that
bug if that i
AFIK that issue has been fixed, but I don't really know for sure,
since I don't have OS X.
2015-12-12 19:55 GMT+01:00 Adam Wolf :
> Does this actually work with OS X in KiCad, or just in OS X in general?
> Last time I tried to use the python shell in KiCad on OS X you couldn't
> enter any key that
We had a long thread about this back in February. I don’t remember what the
outcome was, but it was during the debate about whether to support 10.7, and I
thought that a line was drawn at supporting Core Duo and 10.7 in the nightlies.
https://lists.launchpad.net/kicad-developers/msg17055.html
Does this actually work with OS X in KiCad, or just in OS X in general?
Last time I tried to use the python shell in KiCad on OS X you couldn't
enter any key that also was used as a command with a modifier button, and
when I tried to chase it down, it was actually a complicated Wx issue.
This also
Le 12/12/2015 18:26, Chris Pavlina a écrit :
> I actually thought a bit about that, and wasn't sure how to reconcile
> "make the labels look nice" with "we like 50mil grids". But then, I went
> off-grid for horizontal _anyway_, so... *shrug*
>
> It'll take some reworking of the placement code to
If someone else can prepare a patch that removes the OS X packaging from
the tree, I will test it. I will put "make a patch that removes the OS X
packaging from tree" on the bottom of my list, so it can be a (slow) race :)
Adam Wolf
On Sat, Dec 12, 2015 at 7:24 AM, Nick Østergaard wrote:
> I t
I actually thought a bit about that, and wasn't sure how to reconcile
"make the labels look nice" with "we like 50mil grids". But then, I went
off-grid for horizontal _anyway_, so... *shrug*
It'll take some reworking of the placement code to make the vertical
grid flexible - not something I'd p
I finally got a chance to test this patch, I like it. It works as
advertised and is very handy. I have only one minor gripe is that it
appears to space the fields with the same delta no matter what the text
size (see screenshot). It looks like your placing the center of the
text height at a fixe
Duh? Ignore this. Sorry for the noise.
On 12/12/2015 12:16 PM, Wayne Stambaugh wrote:
> I finally got a chance to test this patch, I like it. It works as
> advertised and is very handy. I have only one minor gripe is that it
> appears to space the fields with the same delta no matter what the
I just tried this. Nice! This is definitely nicer than the Python
shell we are using. I'm with Nick, where's the patch?
On 12/12/2015 10:00 AM, Nick Østergaard wrote:
> I have heard that it opens fine on linux, windows and OS X. I don't
> expect it to break anything. I am just waiting for the p
I finally got a chance to test this patch, I like it. It works as
advertised and is very handy. I have only one minor gripe is that it
appears to space the fields with the same delta no matter what the text
size (see screenshot). It looks like your placing the center of the
text height at a fixe
On 12/11/2015 3:20 PM, Simon Richter wrote:
> 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.
>
> Tha
I'm looking at my notes from when I started the Mac nightlies last February
and I have the flags for the way they were compiled before. It'll be a
good start at least.
On Sat, Dec 12, 2015, 7:07 AM Jose A. Saumell
wrote:
> The Core 2 Duo is the first batch of Intel macs with 64-bit processor.
>
I have heard that it opens fine on linux, windows and OS X. I don't
expect it to break anything. I am just waiting for the patch to test
that.
2015-12-11 20:36 GMT+01:00 Wayne Stambaugh :
> What say our Python devs. I'm fine with it assuming it doesn't break
> anything (read all platforms).
>
> O
I think it will be find ot remove the windwos stuff, because it is
easier to maintain outside the source. And it is currently not used by
the package build anyway.
2015-12-11 17:48 GMT+01:00 Wayne Stambaugh :
> I'll leave the decision to remove the /package folder up to the package
> devs. If the
Hi Wayne,
following your previously mail
I haven't had a chance to use this yet but it sounds really interesting
so it will be near the top of my list of things to include during the
next development cycle.
https://lists.launchpad.net/kicad-developers/msg20210.html
do you think it could be mor
The Core 2 Duo is the first batch of Intel macs with 64-bit processor. The
'core duo' are 32-bit, if you go back enough to cover Core2duo would be
great! at least for me :)
Cheers. Jose
On Sat, Dec 12, 2015 at 9:49 AM Bernhard Stegmaier
wrote:
> If I remember correctly the first Intel Mac’s ca
If I remember correctly the first Intel Mac’s came with Core Duo.
With gcc IMHO —march=nocona was the way to go with those.
I don’t know what clang supports and how far back we want to be compatible.
Regards,
Bernhard
> On 11 Dec 2015, at 21:32, Adam Wolf wrote:
>
> That looks right. Now to
Hi Strotium
I have not really used the python shell that much in KiCad, but will
this also allow tab completion like we see in ipython?
2015-12-11 15:57 GMT+01:00 Strontium :
> Hello Kicad developers,
>
> I have been a very long time follower of kicad and I think the work done to
> it over the ye
26 matches
Mail list logo
