Hehe, well, I guess everything can be renamed in the opposite
direction. But consistency is needed.
On Wed, Oct 8, 2014 at 2:45 AM, Lorenzo Marcantonio
wrote:
> On Wed, Oct 08, 2014 at 02:37:40AM -0400, Mark Roszko wrote:
>> So from what I remember, Kicad used to call alot of pcb footprints as
>>
On Wed, Oct 08, 2014 at 02:37:40AM -0400, Mark Roszko wrote:
> So from what I remember, Kicad used to call alot of pcb footprints as
> "modules". Sometimes it was "module", other times "footprint module"
> and now "footprint". Footprint seems to have picked up in usage so
> let's use it everywhere!
So from what I remember, Kicad used to call alot of pcb footprints as
"modules". Sometimes it was "module", other times "footprint module"
and now "footprint". Footprint seems to have picked up in usage so
let's use it everywhere!
Right now new users just get confused and its a popular compliant. I
On 8 October 2014 17:34, Mark Roszko wrote:
> I was thinking it could be "Total issues", "Warnings", "Errors",
> having the word "count" repeat 3 times seems...redundant. Total errors
> is also wrong since its warnings + errors.
Sounds even better.
___
I was thinking it could be "Total issues", "Warnings", "Errors",
having the word "count" repeat 3 times seems...redundant. Total errors
is also wrong since its warnings + errors.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kic
On 8 October 2014 16:43, Mark Roszko wrote:
>
> I submitted this as a merge request but it may be best to discuss it
> on the mailing list.
>
> I started to hit up the other Eeschema dialogs while I was working on
> the hotkey editor.
>
> https://code.launchpad.net/~mark-roszko/kicad/eeschema-dial
> would drop the [] around the tab names, use capitalization for the tab
>names, and change "libedit" to "Library Editor" (or something other than
>an abbreviation). If you find more of these abbreviations, please fix
>them to something sensible.
Fixed that in the latest branch commit.
>I woul
Also fixes ERC Dialog not counting errors at all. For some reason
SetLabel was used on wxTextCtrl isntead of SetValue.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https:/
I submitted this as a merge request but it may be best to discuss it
on the mailing list.
I started to hit up the other Eeschema dialogs while I was working on
the hotkey editor.
https://code.launchpad.net/~mark-roszko/kicad/eeschema-dialog-tweaks
Changes:
=
-Use the verb "Generate" rath
On 10/6/2014 11:52 PM, Mark Roszko wrote:
> New changes pushed to branch
> (https://code.launchpad.net/~mark-roszko/kicad/kicad), the interface
> has been revised a bit more heavily.
> Sections are now split into tabs!. This helps immensely bringing
> attention to different set of keys easily rathe
On Oct 7, 2014, at 10:48 AM, Nick Østergaard wrote:
>
> Den 07/10/2014 19.43 skrev "Wayne Stambaugh" :
> >
> > In Andy's defense, the OSX compile instructions show:
> >
> > # patch -p0 ../kicad/patches/wxwidgets-3.0.0_macosx.patch
> >
> > so I can understand his confusion. I missed that when I
I don't see why I can't try at disabling the original wxGrid behavior
at using the arrow keys (and home/end and other keys). I don't see a
point in retaining them in a hotkey editor.
On Tue, Oct 7, 2014 at 10:11 AM, Mike Crawford wrote:
> Question on your new hotkey editor. Will there be a way t
Fixed this and the patch error in r5167
Wayne
On 10/7/2014 2:59 PM, Bernhard Stegmaier wrote:
> Yes, sorry… I also missed that.
> There is also another problem… copy/paste seems to have messed up
> closing quotes on the configure command:
> CPPFLAGS="-stdlib=libstdc++*"* \
> LDFLAGS="
Yes, sorry… I also missed that.
There is also another problem… copy/paste seems to have messed up closing
quotes on the configure command:
CPPFLAGS="-stdlib=libstdc++" \
LDFLAGS="-stdlib=libstdc++" \
Regards,
Bernhard
On 07.10.2014, at 19:48, Nick Østergaard wrote:
>
> Den 07/10/
Hi Henri,
I applied the patch with minor tweak in r5166. Thank you for the patch.
Regards,
Wayne
On 10/5/2014 8:21 AM, Henri Valta wrote:
> I had a similar problem to bug 1285878, where the pcb_plot_params_lexer.h was
> not yet available when building the 3d-viewer or pcad2kicadpcb_plugin on
On Oct 7, 2014, at 10:10 AM, Mike Crawford wrote:
> patch is expecting its input on stdin there, re-run the command with:
> patch -p0 < ../kicad/patches/wxwidgets-3.0.0_macosx.patch
> That should apply the patch
Hah, that worked.
Looks like a patch is needed for the patch instructions!
-a
On Oct 6, 2014, at 7:44 PM, Garth Corral wrote:
> On Oct 6, 2014, at 5:39 PM, Andy Peters wrote:
>
>> Hi, guys -- I have been doing daily builds on OS X, and I haven't had any
>> build issues. Now, I did build and install the various prerequisites (glew,
>> whatnot). Do recent builds use what
Den 07/10/2014 19.43 skrev "Wayne Stambaugh" :
>
> In Andy's defense, the OSX compile instructions show:
>
> # patch -p0 ../kicad/patches/wxwidgets-3.0.0_macosx.patch
>
> so I can understand his confusion. I missed that when I committed
> Bernhard's patch. I will update it so that it is correct.
In Andy's defense, the OSX compile instructions show:
# patch -p0 ../kicad/patches/wxwidgets-3.0.0_macosx.patch
so I can understand his confusion. I missed that when I committed
Bernhard's patch. I will update it so that it is correct. Sometimes
it's these setbacks that help us find issues and
Else, read the man page for patch, see the option -i.
Den 07/10/2014 19.26 skrev "Andy Peters" :
> On Oct 7, 2014, at 10:10 AM, Mike Crawford wrote:
>
> > patch is expecting its input on stdin there, re-run the command with:
> > patch -p0 < ../kicad/patches/wxwidgets-3.0.0_macosx.patch
> > Tha
patch is expecting its input on stdin there, re-run the command with:
patch -p0 < ../kicad/patches/wxwidgets-3.0.0_macosx.patch
That should apply the patch
On Tue Oct 07 2014 at 6:06:54 PM Andy Peters wrote:
> On Oct 6, 2014, at 7:44 PM, Garth Corral wrote:
>
> > On Oct 6, 2014, at 5:39 PM,
In response to a message written on 03.10.2014 16:08, from LordBlick:
> In response to a message written on 03.10.2014 15:11, from Wayne Stambaugh:
> can I hope on create something like a pcbnew.getConfigDir() to provide best
> configuration storage in all supported OS's ? ;)
There's no hope…
Sin
Hi Bernhard,
I sent the wrong link previously:
https://github.com/wayneandlayne/KicadOSXBuilder/tree/oct_2014_beta
Adam Wolf
Cofounder and Engineer, W&L
On Tue, Oct 7, 2014 at 7:07 AM, Adam Wolf
wrote:
> Bernhard,
>
> I have uploaded a build script at GitHub over at
> https://github.com/wayne
Question on your new hotkey editor. Will there be a way to use the arrow
keys as hot keys with it? With the current one all that happens when I try
to use them is the focus is shifted from the field. I'm eventually looking
to add hotkeys for panning, and I'd love to use the arrows for that.
On
On 06/10/14 23:44, John Beard wrote:
> Hello,
>
> Attached is a small patch
Sorry, that's inlined. Here's the patch as an attachment if that is
preferred.
Cheers,
John
diff --git a/eeschema/dialogs/dialog_choose_component.cpp b/eeschema/dialogs/dialog_choose_component.cpp
index 9352c94..9b00
>
> 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
On 9/29/2014 2:28 AM, Francesco Del Degan wrote:
> Hi,
> I found that if you have multiple versions of wxPython (2.8 and 3.0)
> installed and
> enabled WX_PYTOHN_SCRIPTING macro, the wxPyCoreAPI_IMPORT call will
> select the default one (in my case 2.8), and it will SEGV.
>
> This because it doe
On Tue, Oct 07, 2014 at 08:23:40AM -0400, Wayne Stambaugh wrote:
> > Do we have to choose this important tool quickly? I hope not...
>
> No, we do not have to hurry. I prefer that we take our time and make a
> choice that works the best for the project. I think you are going about
> it the right
On 10/6/2014 6:19 PM, Brian Sidebotham wrote:
> 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
This must be unique to OSX because I just tested this on Windows and it
work fine. I guess the OSX devs will need to use CMake 3.0.2.
On 10/6/2014 5:14 PM, Bernhard Stegmaier wrote:
> At least I can confirm this behavior with my CMake 2.8.12.
> If I run the same configure command twice in a row,
On 10/6/2014 5:09 PM, Marco Ciampa wrote:
> On Mon, Oct 06, 2014 at 12:13:30PM -0400, Wayne Stambaugh wrote:
>> On 10/5/2014 11:26 PM, Mitch Davis wrote:
>>> Hi,
>>>
>>> On Mon, Oct 6, 2014 at 1:46 PM, Blair Bonnett
>>> wrote:
On 6 October 2014 14:33, Mitch Davis wrote:
>
> Is there
Bernhard,
I have uploaded a build script at GitHub over at
https://github.com/wayneandlayne/KicadOSXBuilder. It's nothing special,
but works for me.
Let me know what you think.
Adam Wolf
Cofounder and Engineer
W&L
On Tue, Oct 7, 2014 at 4:19 AM, Bernhard Stegmaier
wrote:
> Hi,
>
> and to an
Hi,
and to answer the first question: it now uses everything installed on
your system, the only dependency currently being built in the KiCad
CMake build process is boost.
But, as Garth already mentioned you must not use a "stock" wxWidgets,
because unfortunately still the overlay support is
33 matches
Mail list logo
