On Sun, Sep 08, 2013 at 07:42:55AM +0200, Lorenzo Marcantonio wrote:
> Neither have I. Still no response on the list, I assume I'll have to dig
> thru the code.
It's almost an easter egg (after the TEXT_SIZE/SIZE_TEXT of yesterday,
kicad is becoming full of suprises!). This is what gives the messa
On Sun, Sep 08, 2013 at 12:26:32AM -0400, Jacob Schmidt wrote:
> parallel to each other, I immediately think, "Bing!" -- "crosstalk"
I know that, but also a) I want these tracks parallel anyway and b)
a better message could be useful.
> Again, I have no idea if that is what "this looks bad" mea
I, of course, have no experience with the code-base or decisions
thereof, so this is a complete and total guess. Whenever I hear someone
routing tracks parallel to each other, I immediately think, "Bing!" --
"crosstalk"
http://en.wikipedia.org/wiki/Crosstalk_%28electronics%29
Again, I have
Congratulations, good work Brian :)
Miguel Angel Ajo Pelayo
http://www.nbee.es
+34 636 52 25 69
skype: ajoajoajo
2013/9/8 Brian Sidebotham
> Hi Guys,
>
> I have rolled a release, V3.0 of KiCad-Winbuilder. I've put this off for a
> while to address the scripting issues I was having. Also though
I forgot about the most important part of my previous message, the link :)
http://dev.kicad-pcb.org/doxygen-python-test/classpcbnew_1_1BOARD.html
Miguel Angel Ajo Pelayo
http://www.nbee.es
+34 636 52 25 69
skype: ajoajoajo
2013/9/8 Miguel Angel
>
> It's a first try, only "BOARD" class exten
It's a first try, only "BOARD" class extended descriptions are
imported from the C++ doxygen.
It's not perfect, but can be automated and much better than nothing.
We do:
C++ ->doxygen-> XML -> python_script-> .i
then
*.i's ->swig-> pcbnew.py
and finally
pcbnew.py -> doxygen ->
Hi Guys,
I have rolled a release, V3.0 of KiCad-Winbuilder. I've put this off for a
while to address the scripting issues I was having. Also though, MinGW
updated their released version to 4.8.1 from 4.7.2 - so this release is
rolled with mingw32 4.8.1.
This version obviously enables all the pyth
Funny thing I've found.
We have *both* DEFAULT_TEXT_SIZE and DEFAULT_SIZE_TEXT. A trap for the
unwary coders!
DEFAULT_TEXT_SIZE seems to be used for the initial pin text sizes and
sheet names.
DEFAULT_SIZE_TEXT for... the rest I assume, since it gives the defaults
for EDA_TEXT.
Also I'm having
8 matches
Mail list logo
