2015-01-15 20:14 GMT+03:00 Andy Peters :
>
> > On Jan 14, 2015, at 7:46 PM, Fat-Zer wrote:
> > yep, but for user can be able to easily chose it, kicad library should
> provide them out of the box... And I propouse a way to store them in
> library more straightforward IMO.
>
> I guess I don't se
Le 16/01/2015 03:19, LordBlick a écrit :
> In response to a message written on 16.01.2015, 01:38, from LordBlick:
>> I just discovered that for some reason Pcbnew does not display
>> complete zones in
>> just designed project.
>> Looking into project file:
>>(layers
>> -> (0 Gorna jumper)
>>
Le 16/01/2015 08:14, Mark Roszko a écrit :
> First patch fixes the Save library file as dialog which had the library
> extension instead of library extension wildcard used.
>
> Second patch fixes a null termination in eeschema/cross-probing.cpp. The
> char array line is in block scope and is never
Ok, I see you have fixed it in rev 5371.
But I still see two semicolons in github/github_getliblist.cpp I
don't see why there are two.
2015-01-15 22:57 GMT+01:00 Nick Østergaard :
> Ahh, I just found the place. I have attached a patch that removed the
> extra slash and the extra semicolon.
>
> T
On 15 January 2015 at 10:20, Miguel Ángel Ajo wrote:
> Yesterday I wrote a proposal for discussion here:
>
> http://pads.kicad-pcb.org/p/kicad-scripting-layer (please write your name
> for your color
> using the top right icon, so what you write can be identified to you).
>
> I tried not to look
Hi Brian,
I see your point, but the problem with that is interoperability, for example
if we mix up modules which work with pcbnew, they could change units,
and mix them all up.
I have proposed on the ether pad to do something like:
Point.mm(10, 10), which would, under the hood do:
class
In response to a message written on 16.01.2015, 13:09, from Miguel Ángel Ajo:
I’m also trying to think if there is any way to handle it within a context,
with Units(MM):
point = Point(10,10)
I think that any similar constructions debate are waste of time. If somebody
wants to crea
In my opinion it’s not a waste of time.
A decent API will lead to more standardized scripts, and the
people ability to share and look at other’s work.
Cheers,
Miguel Ángel.
Miguel Ángel Ajo
On Friday, 16 de January de 2015 at 13:24, LordBlick wrote:
> In response to a message written on 16.0
In response to a message written on 16.01.2015, 09:38, from jp charras:
The pcb file has no issue, no mess.
The Layers section is perfectly valid
Copper layers can be renamed by the user.
OK, I'm also wondering about how is possible to achieve and modify list of used
layers in python interface.
Le 16/01/2015 13:38, Daniel Dawid Majewski a écrit :
> In response to a message written on 16.01.2015, 09:38, from jp charras:
>> The pcb file has no issue, no mess.
>> The Layers section is perfectly valid
>> Copper layers can be renamed by the user.
> OK, I'm also wondering about how is possible
In response to a message written on 16.01.2015, 13:26, from Miguel Ángel Ajo:
In my opinion it’s not a waste of time.
A decent API will lead to more standardized scripts, and the
people ability to share and look at other’s work.
All right, IMHO this could itself be provided at that condition if
On 16.01.2015 14:06, LordBlick wrote:
> In response to a message written on 16.01.2015, 13:26, from Miguel Ángel
> Ajo:
>> In my opinion it’s not a waste of time.
>>
>> A decent API will lead to more standardized scripts, and the
>> people ability to share and look at other’s work.
>>
> All right,
Why don't we start with a Python repo on Launchpad or GitHub. I'll
leave that decision to the Python developers. This way the Python
developers can share ideas and contribute their Python expertise. Once
a script reaches some level of usefulness and maturity, the script can
then be submitted for
In response to a message written on 16.01.2015, 14:02, from jp charras:
I'm checking on that list Checkbox("I don't like any extra, not ordered
„/” in net name.") :]
Like C/C++ variables, there are local or global netnames.
Local netnames are prefixed by the name of the sheet path.
global netn
First of all, let me first clarify, we’re discussing two things at the same
time:
[people scripts (2, 2.1, 2.2)] —> [kicad-python-api(1)i] —> [C++ swigged-API]
1) Building an API to access the kicad objects in a way that is not
tightly coupled to the KiCad internals, a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[snip]
> BTW. I've found, that in GAL mode additional intermediate points
> between area and subareas are displayed, which seems to be
> incorrect. See attached image.
Hi LordBlick,
Thanks for the notification, should be fixed in 5374.
Regards,
Or
About units: For me it was a big benefit to be able to just use any 2
element tuple like object for coordinates and sizes, and direct numbers for
other values, and not having to use a conversion to internal units all the
time. I do a lot of my calculations with numpy, so it makes things a lot
easie
In response to a message written on 16.01.2015, 18:10, from Piers Titus van der
Torren:
About units: For me it was a big benefit to be able to just use any 2 element
tuple like object for coordinates and sizes, and direct numbers for other
values, and not having to use a conversion to internal un
About using mm as the default unit, other people may disagree, we should provide
facilities to let people specify their unit.
On Friday, 16 de January de 2015 at 18:30, LordBlick wrote:
> In response to a message written on 16.01.2015, 18:10, from Piers Titus van
> der
> Torren:
> > About u
In response to a message written on 16.01.2015, 18:43, from Miguel Ángel Ajo:
About using mm as the default unit, other people may disagree, we should provide
facilities to let people specify their unit.
wxPoint and wxSize can be subclassed to allow any arithmetical operation and
unit conversion
Miguel Ángel Ajo
On Friday, 16 de January de 2015 at 20:01, LordBlick wrote:
> In response to a message written on 16.01.2015, 18:43, from Miguel Ángel Ajo:
> > About using mm as the default unit, other people may disagree, we should
> > provide
> > facilities to let people specify their unit
I recently discovered that the mirrored printing in Pcbnew is broken on
windows. At first I thought it was a 32 bit versus 64 bit issue but I
discovered that it is due to the wxWidgets version. When I use
wxWidgets 3.0.0, the mirrored printing works fine (at least on 32 bit
MinGW builds). Using
In response to a message written on 16.01.2015, 18:02, from Maciej Sumiński:
Thanks for the notification, should be fixed in 5374.
Seems to be OK, Thank you
--
Best Regards,
LordBlick
___
Mailing list: https://launchpad.net/~kicad-developers
Post to
Le 16/01/2015 22:03, Wayne Stambaugh a écrit :
> I recently discovered that the mirrored printing in Pcbnew is broken on
> windows. At first I thought it was a 32 bit versus 64 bit issue but I
> discovered that it is due to the wxWidgets version. When I use
> wxWidgets 3.0.0, the mirrored printin
24 matches
Mail list logo