Thank you Jon! I pushed your patch to the master branch.
Regards,
Orson
On 11/30/2017 02:59 AM, Jon Evans wrote:
> Another quick bug fix
>
> -Jon
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to :
JP, Wayne,
Any update on how we want to handle this?
On Mon, Nov 27, 2017 at 9:48 PM, Oliver Walters <
oliver.henry.walt...@gmail.com> wrote:
> jp,
>
> Sorry I forgot to reapply that patch on top.
>
> Updated patch set is attached.
>
> Thanks,
>
> On Mon, Nov 27, 2017 at 6:48 PM, jp charras
Yes I understand that conding policy and I have been done some quite big
corrections. It would be helpful, if someone show me in my code some
examples what I must do differently. And what are those object and
non-object code mixing places Tom mentioned? Even one example.
-hp
On Wed, Nov 29, 2017
Another quick bug fix
-Jon
From 1b44ddc372d1bafba7e0132a04d09eadf5bdb449 Mon Sep 17 00:00:00 2001
From: Jon Evans
Date: Wed, 29 Nov 2017 20:58:47 -0500
Subject: [PATCH] Restore "Flip Board" checkbox state when switching canvases
Fixes: lp:1733936
*
>.B_ImpedanceControlled,(Yes|No)
Simple true false but is there a mechanism to actually call out impedance
of traces on the gerbers? Otherwise I have to send the fab a drawing
instead of job file so they know what traces they need to
redimension/adjust to match the random FR-4 they are using.
.B_Substrate,{,}
=(FR4|Polyimide|Polyolefin|
Al|PTFE|Teflon|Ceramic|)
Is that supposed to be a list in a particular order of layers? I don't see
otherwise how to define a specific layer to a specific substrate.
On Wed, Nov 29, 2017 at 9:43 AM, jp charras wrote:
> As you
On 11/29/2017 05:04 PM, Chris Pavlina wrote:
> On Wed, Nov 29, 2017 at 03:56:20PM -0500, Wayne Stambaugh wrote:
>> I typically use '%s' mainly because it's easier than escaping the double
>> quote but I'm not opposed to "%s". <%s> should be avoided because some
>> text controls interpret the <>
On 11/29/2017 06:21 PM, Tomasz Wlostowski wrote:
> On 30/11/17 00:18, Wayne Stambaugh wrote:
>> Hi Andreas,
>>
>> Per our previous conversation, if you want to write your solver in C++,
>> then I would prefer that you do it as part of a solver plugin rather
>> than a command event handler in
On 30/11/17 00:18, Wayne Stambaugh wrote:
> Hi Andreas,
>
> Per our previous conversation, if you want to write your solver in C++,
> then I would prefer that you do it as part of a solver plugin rather
> than a command event handler in Pcbnew. I image there would be other
> uses for a solver
Hi Andreas,
Per our previous conversation, if you want to write your solver in C++,
then I would prefer that you do it as part of a solver plugin rather
than a command event handler in Pcbnew. I image there would be other
uses for a solver plugin object such as a thermal mapping solver which
has
On Wed, Nov 29, 2017 at 03:56:20PM -0500, Wayne Stambaugh wrote:
> I typically use '%s' mainly because it's easier than escaping the double
> quote but I'm not opposed to "%s". <%s> should be avoided because some
> text controls interpret the <> as html tags. I thought we got ride of
> most if
On 11/29/2017 08:07 PM, Tomasz Wlostowski wrote:
> On 29/11/17 19:09, Andreas Buhr wrote:
[snip]
>> The input which my solver needs would be an array of polygons,
>> representing the copper-filled areas on each layer.
>> I then want to create a 2D triangle mesh and based on that a 3D prism
>>
I typically use '%s' mainly because it's easier than escaping the double
quote but I'm not opposed to "%s". <%s> should be avoided because some
text controls interpret the <> as html tags. I thought we got ride of
most if not all of the <%s> occurrences but apparently not.
On 11/29/2017 3:26
Hi,
we don't seem to have a consistent convention on quoting in messages
shown to the user, and thus we have all three of
'%s'
"%s"
<%s>
in format strings when referring to names (files, nets, netclasses, …).
For the untranslated strings, I'd prefer either double or single quotes,
Here is the re-based patchset. No code changes but I repaired the coding
policy violations.
Best-
Seth
On Wed, Nov 29, 2017 at 7:40 AM, Wayne Stambaugh
wrote:
> Seth,
>
> I've done some minimal testing with this patch set and it appears to
> work as expected. I like the
On 29/11/17 19:09, Andreas Buhr wrote:
> Dear Kicad developers,
>
> I'm new to Kicad development. Maybe you could give me some starting tips?
>
> I am a 5th year PhD student at the university of Münster in Germany,
> website:
> https://www.uni-muenster.de/AMM/en/ohlberger/team/andreas_buhr.shtml
On 29/11/17 19:09, Andreas Buhr wrote:
> Dear Kicad developers,
>
> I'm new to Kicad development. Maybe you could give me some starting tips?
>
> I am a 5th year PhD student at the university of Münster in Germany,
> website:
> https://www.uni-muenster.de/AMM/en/ohlberger/team/andreas_buhr.shtml
Hi Andreas,
This is a neat idea! It would be great to have a nice open-source tool for
this, as all of the useful ones today are very expensive and proprietary.
As far as I know (others please correct me if I am wrong), there isn't
currently any functionality to generate polygons from the
Dear Kicad developers,
I'm new to Kicad development. Maybe you could give me some starting tips?
I am a 5th year PhD student at the university of Münster in Germany,
website:
https://www.uni-muenster.de/AMM/en/ohlberger/team/andreas_buhr.shtml
I am doing mathematical research targeted at
On 11/29/2017 10:41 AM, Maciej Sumiński wrote:
> Hi Miles,
>
> On 11/29/2017 03:53 PM, miles mccoo wrote:
>> Since BOARD_COMMIT was a requested item to be added to the Python
>> interface, since it's related to be previous questions about getting a
>> redraw on the GAL canvas, and since it could
FYI, this patch can be ignored, I inadvertently rolled it up with the other
patch that JP has already committed, so all fixes are now in.
-Jon
On Wed, Nov 29, 2017 at 7:19 AM, Jon Evans wrote:
> Oops, attached!
>
> On Wed, Nov 29, 2017 at 4:27 AM, Nick Østergaard
Hi Miles,
On 11/29/2017 03:53 PM, miles mccoo wrote:
> Since BOARD_COMMIT was a requested item to be added to the Python
> interface, since it's related to be previous questions about getting a
> redraw on the GAL canvas, and since it could make a good entry to my kicad
> python tutorials, I have
Seth,
I've done some minimal testing with this patch set and it appears to
work as expected. I like the way it handles junctions and it does
resolve the undo issue I was having with the overlapped wires/buses. I
am assuming this is the latest patch set and that there are no other
patches that
Seth,
If you have time, it would be nice to get this fixed.
Thanks,
Wayne
On 11/28/2017 8:06 PM, Seth Hillbrand wrote:
> Wayne-
>
> I see what is happening here. This is a separate issue but I'm happy to
> submit a second patch. Because you are dragging a full wire, Eeschema's
>
Le 29/11/2017 à 15:51, Tomasz Wlostowski a écrit :
> On 29/11/17 12:46, jp charras wrote:
>> Le 29/11/2017 à 00:32, Tomasz Wlostowski a écrit :
>> <...>
>>
>>> I also investigated why the zones are filled slowly - the major reason
>>> was a bug in the GAL zone filling algorithm, which was filling
Hi Tom,
Its okay now.
Heikki
On Wed, Nov 29, 2017 at 4:54 PM, Tomasz Wlostowski <
tomasz.wlostow...@cern.ch> wrote:
> On 29/11/17 14:57, Heikki Pulkkinen wrote:
> > Hi Wayne,
> >
> > Thanks Wayne for answering me.
> >
> > "if you want to be a member of Kicad developers," that is blackmailing.
On 29/11/17 14:57, Heikki Pulkkinen wrote:
> Hi Wayne,
>
> Thanks Wayne for answering me.
>
> "if you want to be a member of Kicad developers," that is blackmailing.
>
Hi Heikki,
I had no intention at all to insult or blackmail. In fact, I like very
much the features you showed (especially the
Since BOARD_COMMIT was a requested item to be added to the Python
interface, since it's related to be previous questions about getting a
redraw on the GAL canvas, and since it could make a good entry to my kicad
python tutorials, I have some questions.
My questions will be mostly in the form of
On 29/11/17 12:46, jp charras wrote:
> Le 29/11/2017 à 00:32, Tomasz Wlostowski a écrit :
> <...>
>
>> I also investigated why the zones are filled slowly - the major reason
>> was a bug in the GAL zone filling algorithm, which was filling all zones
>> by performing N independent fills of every
Seth,
I merged your patch in the development branch. Thank you for your
contribution to KiCad.
Cheers,
Wayne
On 11/27/2017 5:51 PM, Seth Hillbrand wrote:
> In Eeschema, if you draw two lines on top of each other that are not
> the same type, e.g. wire and bus; or bus and graphic line, and
Heikki, That is not blackmailing, it is the exact same rules everyone
else that is a kicad developer or wants to be is expected to follow.
It makes working on the same project easier.
Tom did not mean to kick you out of the mailing list, he meant that your
code is not going to be put into
Hi Wayne,
Thanks Wayne for answering me.
"if you want to be a member of Kicad developers," that is blackmailing.
And I am not going to argue with those rules.
Heikki
On Wed, Nov 29, 2017 at 3:22 PM, Wayne Stambaugh
wrote:
> On 11/29/2017 8:08 AM, Heikki Pulkkinen
On 11/29/2017 8:08 AM, Heikki Pulkkinen wrote:
>
> Hi
>
>
> On Wed, Nov 29, 2017 at 1:32 AM, Tomasz Wlostowski
> > wrote:
>
> On 28/11/17 18:25, Heikki Pulkkinen wrote:
> >
> > Zones filling new record with new
Hi
On Wed, Nov 29, 2017 at 1:32 AM, Tomasz Wlostowski <
tomasz.wlostow...@cern.ch> wrote:
> On 28/11/17 18:25, Heikki Pulkkinen wrote:
> >
> > Zones filling new record with new connectivity algo with A64-Olinuxino
> > board. 13s.
>
> Heikki,
>
> I would be very glad to include your improvements
Oops, attached!
On Wed, Nov 29, 2017 at 4:27 AM, Nick Østergaard wrote:
> No patch is attached to this email.
>
> Den 29. nov. 2017 4.00 AM skrev "Jon Evans" :
>
>> Hi all,
>>
>> I started working on [1] but haven't solved it yet. I did fix a few
>> minor
Le 29/11/2017 à 00:32, Tomasz Wlostowski a écrit :
<...>
> I also investigated why the zones are filled slowly - the major reason
> was a bug in the GAL zone filling algorithm, which was filling all zones
> by performing N independent fills of every zone causing the isolated
> copper islands to
Le 29/11/2017 à 05:04, Jon Evans a écrit :
> Hi all,
>
> I figured out why DRC markers were disappearing... The call to SetBoard()
> erases the view and
> repopulates it from the board objects, but didn't include the DRC markers.
>
> I'm not actually sure why we need to call DisplayBoard() on
No patch is attached to this email.
Den 29. nov. 2017 4.00 AM skrev "Jon Evans" :
> Hi all,
>
> I started working on [1] but haven't solved it yet. I did fix a few minor
> bugs discovered along the way, in the attached patch. The polygon wasn't
> closed, so weird draw
Sorry, I will try to rephrase. In your previous emails you mentioned
different times for filling, but it is not clear what change you made. Did
you update the kicad master branch, or is this a local change you have? I
we don't have any clue abour this, the value you mention is not useful,
since we
39 matches
Mail list logo