On 23 October 2014 00:28, Wayne Stambaugh wrote:
> Adam,
>
> I just committed the fix with my original patch along with a fix for the
> missing files generated by make_lexer() in r5216. Hopefully, this
> solves the problem.
>
> Thanks,
>
> Wayne
Excellent work Wayne!
The duplicate specctra keyw
On 22 Oct 2014 23:00, "Marco Ciampa" wrote:
>
> Sorry I forgot to show directly the .po files. See by yourself:
>
>
https://github.com/ciampix/kicad-doc/blob/master/src/asciidoc/cvpcb/po/cvpcb.pot
>
> You will see that there are many big paragraphs
Yeah, that po file looks good. Hopefully the doc
On 22 Oct 2014 23:03, "Brian Sidebotham" wrote:
>
> The re-designed layout us much more appealing. It looks much better than
the previous layout.
>
> On 22 Oct 2014 19:14, "Mark Roszko" wrote:
> >
> > Actually I planned to do this:
> >
> >
The re-designed layout us much more appealing. It looks much better than
the previous layout.
On 22 Oct 2014 19:14, "Mark Roszko" wrote:
>
> Actually I planned to do this:
>
> Rename the netlist dialog to "Netlist Options"
> Add a "Generate Netlist" menu option which does the immediate
> netlisti
Kicad-Winbuilder was broke a few commits ago by removing some custom python
finding cmake module. I've not had the time to replace it with another
working version. I was hoping to replace it before it was removed.
Hopefully it should be fixed soon!
Best Regards,
Brian.
On 22 Oct 2014 21:30, "Tim
-- Forwarded message --
From: "Brian Sidebotham"
Date: 22 Oct 2014 22:50
Subject: Re: [Kicad-developers] new documentation format
To: "Marco Ciampa"
Cc:
On 22 Oct 2014 22:02, "Marco Ciampa" wrote:
>
> On Wed, Oct 22, 2014 at 05:57:22PM +0200
On 22 October 2014 14:16, Benoît Roehr wrote:
> It takes about 20 seconds for me.
>
> Ubuntu 14.04
> i7 @ 2.2GHz
>
> I've read somewhere linux is better for compiling because of something
> called pipelining. It is present on linux (or better implemented) but not on
> windows.
>
The compilers tur
On 22 October 2014 14:01, Tim Hutt wrote:
> Hi,
>
> I'm trying to do some kicad development on windows. I initially downloaded &
> built it with kicad-winbuilder which went without a hitch. Kicad runs fine.
>
> However, if I perform a null-rebuild (i.e. I don't change anything and just
> run `make
On 22 October 2014 11:22, Brian Sidebotham wrote:
> On 22 October 2014 11:11, Nick Østergaard wrote:
>> Hi
>>
>> I also think that Cirilo Bernardo should not be forgotten, he made
>> great contributions especially in regard to the 3D tools.
>>
>> Nick
>
On 22 October 2014 11:11, Nick Østergaard wrote:
> Hi
>
> I also think that Cirilo Bernardo should not be forgotten, he made
> great contributions especially in regard to the 3D tools.
>
> Nick
>
Oh, so sorry - that was mentioned in the original email!!
Will be there in a minute...
Best Regards
On 21 October 2014 22:58, Marco Ciampa wrote:
> Hello,
>
> talking about the project of switching the KiCad documentation to an
> easier to maintain and translate format, after some experiments, (I know,
> I am slow ... I am not a real programmer) I have produced something
> to check.
>
> This is
> On 21 October 2014 04:37, Andrew Zonenberg wrote:
>> Hi all,
>>
>> While browsing recent commits I saw some updates to authors.txt which
>> prompted me to take a look at the file and noticed two minor issues.
>>
>> 1) "maintener" (line 15) should be spelled "maintainer"
>> 2) Neither Cirillo Ber
On 21 October 2014 23:25, Wayne Stambaugh wrote:
> 3.0.0 sounds good to me.
>
> Wayne
I'm good with the triplet, and any number sounds fine to me! :D
Best Regards,
Brian.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-
Thank-you for the update Andrew.
When I updated the file I asked for any missing people to come forward
and I'd add them straight to the list. I'll do it tonight and sync the
list on http://www/kicad-pcb.org too.
Best Regards,
Brian.
On 21 October 2014 04:37, Andrew Zonenberg wrote:
> Hi all,
On 17 October 2014 14:10, Wayne Stambaugh wrote:
> On 10/17/2014 8:44 AM, jp charras wrote:
>> Le 17/10/2014 14:22, Mark Roszko a écrit :
>>> Alright, I've played around. It appears there is many CAM/gerber
>>> software that cannot handle G75 arcs that are full 360 degrees. I
>>> tested this with
can also take a look at the dialog to see if
they're experiencing the same problem.
Best Regards,
Brian Sidebotham.
On 16 October 2014 17:56, Garth Corral wrote:
> Thanks for the quick reply.
>
> Yes, already tried a sample of files; 1.11, 1.12 and 1.13 files open and
> seemin
Hi All,
I've just updated the AUTHORS.txt wtih some recent, and some
not-so-recent contributors to the list.
Some notes about the list:
(1) It's not in any order what-so-ever.
(2) It's not complete!
With regard to 2, please do not feel offended if you feel as though
you've made a contribution a
On 16 October 2014 17:30, Garth Corral wrote:
>
> Hi, guys.
>
> After the recent eeschema dialog commit, my build of wxFormBuilder won’t
> allow me to do anything with dialog_eeschema_options_base.fbp. It will open
> it just fine, but after that I can’t use the UI; clicking on anything does
>
On 15 October 2014 22:44, Brian Sidebotham wrote:
> On 15 October 2014 21:44, Wayne Stambaugh wrote:
>> On 10/15/2014 4:27 PM, Brian Sidebotham wrote:
>>> On 5 October 2014 00:12, Brian Sidebotham
>>> wrote:
>>>> Hi Wayne, I can't check right now, bu
On 15 October 2014 21:44, Wayne Stambaugh wrote:
> On 10/15/2014 4:27 PM, Brian Sidebotham wrote:
>> On 5 October 2014 00:12, Brian Sidebotham wrote:
>>> Hi Wayne, I can't check right now, but I'm sure it is to find
>>> python-a-mingw-us for kicad-winbuilder.
On 5 October 2014 00:12, Brian Sidebotham wrote:
> Hi Wayne, I can't check right now, but I'm sure it is to find
> python-a-mingw-us for kicad-winbuilder. I expect the answer is to remove the
> custom findpython cmake module and replace it with a findpythonamingwus
> modu
On 14 October 2014 22:09, Mark Roszko wrote:
> Ah, the only thing that changed is I moved all the comments from the
> .cpp to .h as you asked before so you can't ding me for that :P And a
> description.
> There is a white space line I just noticed.
>
>
>
> I am having trouble with wxFormBuillder.
On 14 October 2014 22:16, Mark Roszko wrote:
> Be it just semantics but for me
>
> Documentation != Manual != Specifications
>
It is probably just semantics, but then this is wrong because
apparently Documentation != Manual !?
> I wish the manuals were plain text based, I would be more than happ
On 14 October 2014 21:57, Brian Sidebotham wrote:
> On 14 October 2014 21:54, Mark Roszko wrote:
>>>The manual uses component throughout and indeed Component name in the UI
>>>Component properties dialog. All the screenshots show Component too.
>>>If eeschema has
On 14 October 2014 21:54, Mark Roszko wrote:
>>The manual uses component throughout and indeed Component name in the UI
>>Component properties dialog. All the screenshots show Component too.
>>If eeschema has changed these, they should be changed back
>
> An manual should never define the software
On 13 October 2014 17:22, Wayne Stambaugh wrote:
> On 10/12/2014 9:14 PM, Mark Roszko wrote:
>> Very minor but the main KiCAD window calls it "Schematic Library
>> Editor", eeschema calls it "Library Editor" and the window itself is
>> "Parts Library Editor".
>>
>> Can the name be standardized?
>>
Sorry, I didn't get much chance to look at it - but I liked the idea
of it - I think this is one of the very reasons behind the KiWay work.
It's certainly a bonus of that work which we should be reaping.
I didn't get a chance to apply and test though. Let me know if you need that.
Best Regards,
On 9 October 2014 10:01, Benoît Roehr wrote:
>
> Le 09/10/2014 08:36, Lorenzo Marcantonio a écrit :
>>
>> On Wed, Oct 08, 2014 at 11:33:39PM +0200, Benoît Roehr wrote:
>>>
>>> Does someone have a turnkey solution for building and running eeschema
>>> alone
>>> ? Can it be done by tweaking winbuild
Hi Mark,
Thanks for your work, I've not had a chance to look at the merge request.
Generally discussion is always a great idea because it's hard to glean
from a diff what the intended changes are and what the impact is going
to be. I'm at work at the moment so still can't review the diff.
I'm cu
>
> Hey Brian,
>
> I'm looking at the download page at kicad-pcb.org and I don't see a link
> to this page. Am I missing something? We should be pointing users here
> rather than asking them to build from source in order to run bleeding
> edge versions of KiCad. Would someone please add a link t
Excellent work Marco. Sorry, replying on my phone!
Picking the right tool is essential, we're just itching to make the
transition to text based documentation, that's all. We've had odt
documentation for a long time, and we can suffer that for a while longer
while we evaluate the text based solutio
On 6 October 2014 21:57, Wayne Stambaugh wrote:
> That was an easy fix :) Thanks again for taking on the task of
> providing regular builds for OSX users. Now we just have to get regular
> builds for windows users. I think once we get over this hurdle, we wont
> have to spend so much time provi
On 6 October 2014 16:23, Wayne Stambaugh wrote:
> Lorenzo,
>
> I know it's a pain to do but this really needs to be documented
> somewhere in the Pcbnew user's manual. Otherwise, no one will know how
> to use this excellent feature except those of us on the developers
> mailing list. The reason
On 5 October 2014 00:18, Wayne Stambaugh wrote:
> Here is a another teaser of the mingw64 version of kicad showing the
> wxPython shell so it appears to be working.
>
Hi Wayne,
There's no reason it shouldn't work really, KiCad-Winbuilder uses
mingw-w64 and builds fine with wxPython (Well, the wx
Hi Lorenzo,
Thanks for sorting this out, it'll make a great difference for my next
board!
Best Regards,
Brian.
On 4 Oct 2014 16:26, "Lorenzo Marcantonio"
wrote:
> Sorry about the delay, we had the automechanika fair and related stuff
> to handle :P
>
> In fact the patch is quite simple (I alre
version of FindPythonLib.cmake.
> >
> > Hi Wayne,
> >
> > Not being a Windows user I can't speculate as to the need for the
> > customisation, but CMakeModules/FindPythonInterp.cmake
> > and CMakeModules/FindPythonLibs.cmake were added by Brian Sidebotham in
>
On 14 September 2014 06:17, Lorenzo Marcantonio
wrote:
> On Sun, Sep 14, 2014 at 12:39:33AM -0400, Carl Poirier wrote:
>> Is there any way to have it not on silkscreen, besides editing the
>> .kicad_mod file by hand?
>
> Committed yesterday; now the text module dialog contains the layer combo like
On 10 September 2014 17:31, Lorenzo Marcantonio
wrote:
> On Wed, Sep 10, 2014 at 05:14:43PM +0100, Brian Sidebotham wrote:
>> I don't get that conclusion considering that module "text placed on a
>> front layer" is currently impossible as instead in a module
On 10 September 2014 16:54, Lorenzo Marcantonio
wrote:
> On Wed, Sep 10, 2014 at 04:49:55PM +0100, Brian Sidebotham wrote:
>> The world survives on convention. If that is ours, why invent new?
>
> Because *our* convention is Front/Back. The collector itself uses it for
>
On 10 September 2014 16:14, Lorenzo Marcantonio
wrote:
> On Wed, Sep 10, 2014 at 03:57:51PM +0100, Brian Sidebotham wrote:
>> Yep, I understood all that before I proposed the names.
>
> Then why not IgnoreMTextsOnFront and IgnoreMTextsOnBack ? Cu has no
> relationship with t
On 10 September 2014 14:56, Lorenzo Marcantonio
wrote:
> On Wed, Sep 10, 2014 at 02:20:48PM +0100, Brian Sidebotham wrote:
>> I think the rename should be done, but I think we should probably end up
>> with:
>>
>> IgnoreMTextsOnF_Cu
>> IgnoreMTextsOnB_Cu
On 10 September 2014 07:49, Lorenzo Marcantonio
wrote:
> While inspecting for text module usage, I found a couple of call which
> (for a little) puzzled me :D
>
> IgnoreMTextsOnCopper and IgnoreMTextsOnCmp in the collector 'guide'
> class. At first I tought the first was referring to actual copper
On 9 September 2014 04:56, Lorenzo Marcantonio
wrote:
> On Mon, Sep 08, 2014 at 10:27:45PM +0100, Brian Sidebotham wrote:
>> Sorry, but I don't like this patch because I want control of where the
>> reference text goes on both assembly and silk layers. It doesn't
>&
Sorry, but I don't like this patch because I want control of where the
reference text goes on both assembly and silk layers. It doesn't
necessary want to go in the centre of an electrolytic cap for example.
Only for the very basic components is the centre an okay choice.
I would rather just allow
On 4 September 2014 10:03, Maciej Sumiński wrote:
> On 09/03/2014 10:36 PM, Wayne Stambaugh wrote:
>> On 9/3/2014 12:33 PM, Brian Sidebotham wrote:
>>> I think we could do it in a similar fashion to EESCHEMA (it's a
>>> more pleasant experience when things work in
Moses,
Thanks for doing this work - config files instead of the registry
settings on Windows has been on my list forever and I never got round
to doing anything about it. So thanks for getting on and doing it as
well as tidying up the Linux files.
Best Regards,
Brian.
__
KiCad-Winbuilder is using a patched 3.0.0 so it's pretty stable at the
moment. I wanted to wait for a period of no bug reporting against
wxWidgets (with regards to KiCad) until I bumped the version in the
wxWidgets-cmake project that Winbuilder uses.
Best Regards,
Brian.
On 3 September 2014 20:04, yann jautard wrote:
>
> Le 03/09/2014 20:08, Wayne Stambaugh a écrit :
>
>> On 9/3/2014 8:08 AM, yann jautard wrote:
>>>
>>> Le 03/09/2014 12:32, yann jautard a écrit :
Le 02/09/2014 18:24, Wayne Stambaugh a écrit :
>
> I have this on my list of things
On 3 September 2014 17:03, Maciej Sumiński wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>> On Wed, Sep 03, 2014 at 10:22:03AM +0200, Maciej Sumiński wrote:
>>> Healing could be done another way. Instead of moving vertices,
>>> it could be better to add the missing segments. If they a
On 1 September 2014 20:17, Martijn Kuipers wrote:
>
> On 01 Sep 2014, at 19:54, jp charras wrote:
>
> Le 01/09/2014 11:44, Brian Sidebotham a écrit :
>
> On 1 September 2014 10:17, Javier Serrano
> wrote:
>
> On Sat, Aug 30, 2014 at 8:47 PM, Wayne Stambaugh
> wrot
On 31 August 2014 23:49, Aaron Pelly wrote:
> On 01/09/14 02:08, Maciej Sumiński wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 08/31/2014 12:13 AM, Cirilo Bernardo wrote:
>> [snip]
>>>
>>> Is there anyone on the list with web page skills?
>>
>> Sounds like a good opportuni
On 1 September 2014 10:17, Javier Serrano
wrote:
> On Sat, Aug 30, 2014 at 8:47 PM, Wayne Stambaugh
> wrote:
> [snip]
>> I am proposing that we move to a model more like the
>> Linux kernel where there is a merge window for new features followed by
>> a stabilization period.
> [snip]
>
> This lo
On 31 August 2014 22:52, Andrew Zonenberg wrote:
> What I did in my previous build systems is to regenerate the file in a
> temporary directory then check if the files had the same hash. If they
> didn't I'd update the file.
>
> This way, if you don't change the file's contents it doesn't get touc
On 31 August 2014 22:27, Andrew Zonenberg wrote:
> Why does CMake not recompute this particular value during the
> pre-compile configuration step? It runs checks for changed stuff every
> time you "make" anyway and only caches certain things. Is it really that
> hard to not cache this particular v
The version is essentially created during the CMake configure step -
when CMake generates its cache of variables. You need to re-create
this cache to update the value:
make rebuild_cache
That should update to the same as bzr revno.
Best Regards, Brian.
On 31 August 2014 21:47, Andrew Zonen
On 30 August 2014 23:13, Cirilo Bernardo wrote:
> - Original Message -
>
>> From: Brian Sidebotham
>> To: Wayne Stambaugh
>> Cc: KiCad Developers
>> Sent: Saturday, August 30, 2014 9:19 PM
>> Subject: Re: [Kicad-developers] kicad-pcb.org
>>
Looks like it just fell over, however I updated
http://www.kicad-pcb.org/display/KICAD/About+KiCad last night with the
information in AUTHORS.txt
There's some more to do, but at least the majority of it is up there.
I'd like to do some info on the individual programs under About KiCad.
I believe
gt; I obviously have confidence in his abilities, but I don't over estimate his
> staying power,
> nor should you. Please be kind and respectful to him.
>
>
> It is time for me to move out of the top spot and off the mailing list.
>
>
>
> I want to acknowledge
> Hi guys,
>
> Sorry for asking dumb questions, but what is this whole QuasiModal stuff
> for?
>
> Tom
Hi Tom,
No question is dumb.
See Yann's description (from earlier in this thread) of the problem
below, to which Quaimodal is a good solution.
Best Regards,
Brian.
---
Hi Dick, and all the
On 20 August 2014 13:44, yann jautard wrote:
> just FYI, 5084 does not compile any more.
>
> /home/yann/kicad_sources/kicad.bzr/pcbnew/dialogs/dialog_edit_module_for_BoardEditor.cpp:
> In member function ‘virtual void
> DIALOG_MODULE_BOARD_EDITOR::OnCancelClick(wxCommandEvent&)’:
> /home/yann/kica
On 4 August 2014 17:05, Dick Hollenbeck wrote:
>
> I pushed an early branch of this work to milestoneB.
>
> See the commit log for some of the details.
>
> The shared_ptr turned out to be a can of worms. No, several cans of worms,
> all stacked
> like a 2 miles of dominos.
>
> So I used a single
ntent and organization I
> believe.
>
> Who should I talk with about this?
>
> * Updating the binary distribution of KiCad for Windows
> The version linked to from the homepage is from over a year ago. If this is
> the current Stable version, it seems like that should be exp
On 16 August 2014 17:44, Wayne Stambaugh wrote:
> One of the tasks that I have committed to working on in the KiCad road
> map is to clean up the current mess we have created by allowing
> dependency libraries to be built as part of the KiCad source build. The
> only exception I see for the time
For the number of elements in an array, you can use:
./include/macros.h:#define DIM( x )unsigned( sizeof(x) /
sizeof( (x)[0] ) )
which is more consistent in the KiCad source code.
Best Regards, Brian.
___
Mailing list: https://launchpad.net/~k
Hi Jason,
Winbuilder doesn't currently support a debug version build. It's not a
good development environment, but it does at least give you the
dependencies you need to build KiCad on Windows successfully.
The problem with the debug build is with Python as Python searches for
different module na
Thanks for the release information Dick, we'll look to include that in
Winbuilder as soon as possible. At the moment the version used is a
patched v3.0.0, not a vanilla version. Therefore some vital fixes for
KiCad were already included. It will be good to upgrade to get the bug
fixes though.
Jaso
Hi Guys,
I should first say, this is not typical of Winbuilder. Both pcbnew and
cvpcb work fine for me on a fresh Windows 7 install using the github
fp-lib-table. So there's clearly something different about your setup.
Process monitor is (from sysinternals) is excellent at tracking
dependency lo
I know I had this same problem with the python console on Windows. I
don't t think this is something that changed, I think it's always been
there.
I can test on Windows tonight for you and let you know.
Best Regards, Brian.
___
Mailing list: https://la
Hi Guys,
KiCad-Winbuilder V3.4 is out which addresses a few issues. You can get
it from the Launchpad project page:
https://launchpad.net/kicad-winbuilder
3.4 11.06.2014 - BJS
* Copy *.kiface files to the kicad/bin directory. Fixes bug 1315945
* Fix issue with checking for wxPython (was
On 24 March 2014 08:34, dileep kushwaha wrote:
> I need team member(s) to complete this project. I feel I'm too noob to
> complete this part alone.
>
Hi Dileep,
The first thing you need to do is to get some code running - at least
get a basic wxPython application able to run which will be the s
Hi Henner,
Committed in BZR4686.
Thanks again for your contribution.
Best Regards,
Brian.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-develope
On 7 February 2014 16:17, Henner Zeller wrote:
> On 7 February 2014 02:37, Brian Sidebotham wrote:
>> On 5 February 2014 17:18, Henner Zeller wrote:
>>> Hi,
>>> I usually have a lot of windows stacked on my desktop, which often obscures
>>> the 'footp
On 7 February 2014 10:31, jp charras wrote:
> Le 07/02/2014 09:22, Henner Zeller a écrit :
>> Hi,
>> While moving a field text (REFERENCE, VALUE and such) in the
>> schematic, it is possible to loose the visual sight to which component
>> it belonged to, in particular in tight spaces (which is typ
On 5 February 2014 17:18, Henner Zeller wrote:
> Hi,
> I usually have a lot of windows stacked on my desktop, which often obscures
> the 'footprint window' in CvPcb. Pressing the 'view selected footprint'
> brings the window up the _first_ time, but when it is already there, it
> stays buried - w
On 5 February 2014 22:35, Blair Bonnett wrote:
> On 6 February 2014 10:31, Jake wrote:
>>
>> On Wed, 5 Feb 2014, Brian Sidebotham wrote:
>>
>>> On 5 February 2014 10:11, Jake wrote:
>>>>
>>>> I just want to say the same thing that a lot
On 5 February 2014 15:54, Nick Østergaard wrote:
>> However, I notice that changing the Delete function hotkey doesn't
>> work. This in fact should be filed as a bug; So please file a bug
>> report on Launchpad so it can be fixed, or else feel free to apply a
>> patch that fixes this bug instead.
On 5 February 2014 15:54, Henner Zeller wrote:
> On 5 February 2014 06:11, Brian Sidebotham
> wrote:
>>
>> Hi Henner,
>>
>> In EESCHEMA, under Preferences->Hotkeys->Edit Hotkeys, you can edit
>> the hotkeys and set Backspace as the Delete function
On 5 February 2014 14:39, Brian Sidebotham wrote:
> I've also not tested how two keys bound to the same function perform
> in the Hotkeys Editor - but I suspect not well.
Sorry, scrap that last comment, of course it would be absolutely fine.
Best Reg
On 5 February 2014 14:15, Chris Morgan wrote:
>
> If there isn't a binding for the backspace key might it also make
> sense to have the default binding for 'delete item' be both backspace
> and delete by default? In addition of course to fixing whatever bug
> there is in the hotkey assignment.
>
>
Hi Henner,
In EESCHEMA, under Preferences->Hotkeys->Edit Hotkeys, you can edit
the hotkeys and set Backspace as the Delete function.
However, I notice that changing the Delete function hotkey doesn't
work. This in fact should be filed as a bug; So please file a bug
report on Launchpad so it can b
On 5 February 2014 10:11, Jake wrote:
> I just want to say the same thing that a lot of other people have been
> saying for a long time. Bazaar is holding kicad back. I am yet another
> developer who would be contributing to improving the project if it weren't
> kept in an arcane and frustrating
On 4 February 2014 13:04, Joel Holdsworth wrote:
> Hi All,
>
> Thank you all for taking the time to respond to my original e-mail. It
> seems to me that whatever the outcome this discussion it is well worth
> having.
>
>
> On 04/02/14 11:57, Brian Sidebotham wrote:
>
On 4 February 2014 09:10, Simon Turner wrote:
> The process is probably single core anyway, my machine sat practically idle.
>
> Simon
Unfortunately until some source files have been created by CMake,
KiCad-Winbuilder cannot run parallel jobs because the generated source
files get corrupted. So t
I suspect it's all just a documentation issue too as someone else
suggested because it's so easy to branch the code and generate a patch
using Bazaar.
Perhaps the best place for anyone who has decided Bazaar is dead (it
works for me by the way!) and therefore cannot contribute (and
particularly gi
On 3 February 2014 18:38, Milan Horák wrote:
> Hi,
>
> and I am compiling KiCad on VirtualBox Windows XP machine, limited to one
> core of Phenom 955 and 512MB RAM :-)
>
> Milan
>
Ha! I'm impressed that works at all, but fair enough. With only a
single core you can't eat too much memory I guess!
machine with more memory to see if I get
> different results. I'll let everyone know the results.
>
>
>
> On Mon, Feb 3, 2014 at 2:52 AM, Brian Sidebotham
> wrote:
>>
>> Hi Guys,
>>
>> It's always worth when you can filling in bug reports against
&
On 30 January 2014 16:52, Wayne Stambaugh wrote:
> On 1/30/2014 6:59 AM, Brian Sidebotham wrote:
>> Hi Guys,
>>
>> I've just uploaded a new release for KiCad-Winbuilder which includes a
>> few fixes and bumps wxPython up to V3+ (V3.0.0 with a couple of
>> pat
Hi Guys,
It's always worth when you can filling in bug reports against
KiCad-Winbuilder. It helps focus my time and makes we aware of things
I don't know about. Although I can't fix the internal MinGW error
(Which I've never seen!), seeing a bug report means I probably would
have bumped the compil
atulations to both your families.
>> This will be the most import (and busy) part of your life.
>> Greetings,
>> Edwin
>>
>>
>> On Thu, Jan 30, 2014 at 3:13 PM, Brian Sidebotham
>> wrote:
>>>
>>> Thanks Miguel, it will be our first so we&#
Miguel Ángel.
>
> ---
> irc: ajo / mangelajo
> Miguel Angel Ajo Pelayo
> +34 636 52 25 69
> skype: ajoajoajo
>
>
> 2014-01-30 Brian Sidebotham :
>>
>> Hi Guys,
>>
>> I've just uploaded a new release for KiCad-Winbuilder which includes a
>> f
Hi Guys,
I've just uploaded a new release for KiCad-Winbuilder which includes a
few fixes and bumps wxPython up to V3+ (V3.0.0 with a couple of
patches mentioned on the KiCad developers list which are useful fixes
for KiCad). The library now also comes from GitHub (Simply by
downloading the master
vis Ayres wrote:
>> > My branch.conf file:
>> >
>> > parent_location =
>> > http://bazaar.launchpad.net/~brian-sidebotham/kicad-winbuilder/trunk/
>> > bound_location =
>> > http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/
>> >
The allowance of overlapping pads in the DRC is pretty essential at
the moment because KiCad cannot do polygon pads or multiple drill
holes (as Wayne pointed out). Therefore when people require unusual
pad shapes they end up making them out of overlapping pads, relying on
the current behaviour.
Ho
Hi Jean-Pierre,
I'm getting the following error, perhaps through a missing source file?
..\polygon\libpolygon.a(PolyLine.cpp.obj):PolyLine.cpp:(.text+0x4d74):
undefined reference to
`ClipperLib::SimplifyPolygon(std::vector > const&,
std::vector >,
std::allocator > > >&,
ClipperLib::PolyFillType)'
On 2 January 2014 03:27, Cirilo Bernardo wrote:
> Hi folks,
>
> I have put two sets of patches onto github for anyone to review or apply.
>
> The (bzr) patches:
> export_idf3.patch : Adds basic IDF3 export (board and cutouts / holes only)
>
> export_vrml.patch : Improved VRML export; include
On 3 January 2014 14:09, Chris Morgan wrote:
> I'm not actively making changes but in case it helps someone else,
> here is what was confusing me. This is something I do a few times a
> day with git in order to keep history clean and integrate patch review
> feedback.
>
> How to get upstream chang
Sorry, I've been off-list for a while whilst building my house over Christmas.
bzr works fine and is what Launchpad hosted projects work with most
easily. I don't see anyone wanting to change, especially as there's no
real reason to change; Besides, bzr usage is included in the build
system now to
> Orson
> >
> > On 11/15/2013 10:01 PM, Brian Sidebotham wrote:
> >> This dependency is not required on Windows? How come the Linux build
> >> needs it and the Windows build doesn't?
> >> What boot library was throwing the error?
> >>
>
This dependency is not required on Windows? How come the Linux build needs
it and the Windows build doesn't?
What boot library was throwing the error?
Best Regards, Brian.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-dev
On 13 November 2013 17:51, Carl Poirier wrote:
> Coming from Mercurial, I prefer "branch, commit, push" rather than
> "checkout, commit". :P
>
>
Pushing with Bazaar is horrible. It works while you're the only editor, but
once other people start pushing too it will likely all fall over.
You're be
101 - 200 of 521 matches
Mail list logo
