16 at 11:33 AM, Nick Østergaard <mailto:oe.n...@gmail.com>> wrote:
>
> All the sources are ready. The windows build is ready, just needs
> someone to sanity check it. I don't know about the osx build or the PPA.
>
>
> Den 18/12/2016 18.12 skrev
On 12/21/2016 12:25 PM, Kaspar Emanuel wrote:
> Thanks for reading over this JP,
>
> I don't really understand why you are thinking the schematic file
> format should be modified.
>
>
> If you want to see a user field always existing in your component
> editor, just add this fiel
On 12/21/2016 1:01 PM, Kaspar Emanuel wrote:
> Thanks Wayne,
>
> I don't see how using a field versus a new file token makes any
> difference to external tools. The formatting of a field in a schematic
> file is no more or less difficult to parse than any other token such as
> a p
hanges as suggested - new patch attached.
>
> Regards,
>
> Oliver
>
> On Wed, Dec 14, 2016 at 6:22 AM, Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
>
> I finally got a chance to look at this patch. I like the changes for
> the most part.
On 12/22/2016 8:30 PM, Chris Pavlina wrote:
> There's another little project I'd like to work on in the month or so I
> have off now:
>
> https://misc.c4757p.com/outline-error.png
>
> We have way too many error messages like that. That is, in my opinion,
> completely unacceptable. It's confusing
On 1/3/2017 10:08 AM, jp charras wrote:
> Le 03/01/2017 à 15:30, jp charras a écrit :
>> Le 03/01/2017 à 14:03, Miguel Angel Ajo Pelayo a écrit :
>>> Sorry, I just found the email. Sorry for my delayed answer.
>>>
>>> The code looks good to me, I believe it's a good change, it's not backwards
>>>
On 1/4/2017 10:54 AM, jp charras wrote:
> Le 03/01/2017 à 16:30, Wayne Stambaugh a écrit :
>> On 1/3/2017 10:08 AM, jp charras wrote:
>>> Le 03/01/2017 à 15:30, jp charras a écrit :
>>>> Le 03/01/2017 à 14:03, Miguel Angel Ajo Pelayo a écrit :
>>>>>
What do you mean by action plugin? I'm working on the schematic I/O
plugin. AFAIK, that is the only plugin in progress.
On 1/3/2017 10:02 AM, Jean-Samuel Reynaud wrote:
> Dear All,
>
> Quick question about ActionPlugin. What is the current state ? Is there
> anybody working on it ?
>
> Regards
The page settings menu entry in Pcbnew is still in the file menu so I
restored it to the file menu in Eeschema for the sake of consistency.
Thanks for the heads up.
On 12/23/2016 4:30 PM, Chris Pavlina wrote:
> Can we put Page Settings back in the File menu where it was prior to
> de46873? That's
t;
>
> Le 04/01/2017 à 20:14, Wayne Stambaugh a écrit :
>> What do you mean by action plugin? I'm working on the schematic I/O
>> plugin. AFAIK, that is the only plugin in progress.
>>
>> On 1/3/2017 10:02 AM, Jean-Samuel Reynaud wrote:
>>> Dear All,
Thanks Chris. In the future, please make sure that contributions use
wxUpdateUIEvent for updating UI states. A single code path for updating
UI element states prevents potential state conflicts when setting the
state in multiple wxCommandEvents. We have had issues with this in the
past where a U
rework the patch to use wxUpdateUIEvent?
Don't bother unless you have the time. It might be a good exercise for
Diego to learn how to use wxUpdateUIEvent.
>
> On Thu, Jan 05, 2017 at 08:57:14AM -0500, Wayne Stambaugh wrote:
>> Thanks Chris. In the future, please make sure that contributio
I agree. We could do a better job with our commit messages. At the
very least the first line should be a short (< 72 characters, 80
character terminal - the offset of the `git log` command ) descriptive
overview of the changes. For commit messages with more than one line,
there should be at leas
I just stumbled across this:
https://www.adafruit.com/product/720
They claim "Badge created with permission by the KiCad team." Does
anyone know who gave them this permission? I don't ever remember anyone
asking us about this since I've been with the project. Not that I
wouldn't have given my
On 1/5/2017 4:50 PM, Martijn Kuipers wrote:
>
>> On 5 Jan 2017, at 21:42, Wayne Stambaugh > <mailto:stambau...@gmail.com>> wrote:
>>
>> I just stumbled across this:
>>
>> https://www.adafruit.com/product/720
>>
>> They claim "Badge cr
Here's my two cents. I share JP and Chris' concerns about developing
python scripts. As project leader, I can see where a lot of things can
go seriously wrong. Maybe we should make it clear that there should be
no expectation from python developers that the api will remain stable
during developm
pe to hang
themselves but I may be in the minority here.
>
>
> My last remark:
> To load python scripts (wizards and other python script)
> KICAD_SCRIPTING_WXPYTHON is not mandatory.
> KICAD_SCRIPTING is enough.
>
>
> Courage, Jean-Samuel.
>
>>
>>
I think this feature would be useful but we should proceed with caution
if we are going to include persistence. I'm guessing making groups
persistent will require a change to the pcb file format. We should
think this through thoroughly before moving forward. Is it possible
that this grouping cou
feature could be really powerful
if we think about the bigger picture rather than just the patch we have
in front of us.
>
> On 12 January 2017 at 16:37, Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
>
> I think this feature would be useful but we should proc
ed
>> rename of components and netnames to create reuses. This also applies
>> to the schematic entry, obviously.
>>
>> The word "intelligent" above means obviously, that there is some
>> infrastructure and coding work to consider.
>>
>> An example scre
Hi Kaspar,
I applaud your efforts here but you should heed the warnings about using
a colon as a separator within a field. I think using separate fields
would be cleaner and more reliable in the long run.
There are a lot of users who would like atomic symbols but no one can
ever seem to agree on
On 1/13/2017 9:20 AM, Kaspar Emanuel wrote:
>
> On 13 January 2017 at 13:35, Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
>
> Ithink using separate fields
> would be cleaner and more reliable in the long run.
>
>
> Yes, I am coming over to
rack of the hierarchy and parents/childs groups.
>>
>> I looked over my implementation and changed everything to use wxStrings
>> and wxArrayStrings, to be more like current things in Kicad, I do not
>> know if this was an issue or not.
>>
>> Is the file format u
On 1/14/2017 9:35 AM, Chris Pavlina wrote:
> This looks bad:
>
> https://misc.c4757p.com/ugly.png
>
> Really bad. Three of the same icon, with low enough contrast that I can
> barely tell what it's a picture of... and seriously, prepending "** " to
> mark the selected item? Really? Even text-mode
I can see the value in both per net visibility and local ratsnest.
Having local ratsnest (the current footprint selected) visibility is
handy when placing footprints to minimize the number of signal
crossings. Having per net visibility is handy in complex designed so
you can turn off nets to preve
On 1/16/2017 10:30 AM, jp charras wrote:
> Le 16/01/2017 à 14:18, Kristoffer Ödmark a écrit :
>> For basic work, maybe reusing zones functionality in the footprint editor
>> will be enough, and then the anchors would be added by regular circular or
>> rectangular pads. Similar to how one would add
You are not being ignored. I can't speak for all of the lead developers
but I've been really busy so pretty much everyone has been getting
ignored by me. It's not intentional, it's just the reality of my
current work load.
Patch is giving me an unexpected eof with 3d_viewer-pan_step.patch.
Did
Yes. This is a useful piece of information in case we suddenly get a
rash of python scripting bug reports.
On 1/16/2017 2:15 PM, Simon Wells wrote:
> Should this option be added to the about box->copy version info for
> completeness?
>
> On Tue, Jan 17, 2017 at 8:08 AM, Jean-Samuel Reynaud
> wr
антин Барановский wrote:
> Thank you, Wayne, for your response. I'm attached the checked patches.
>
> 2017-01-16 20:07 GMT+02:00 Wayne Stambaugh <mailto:stambau...@gmail.com>>:
>
> You are not being ignored. I can't speak for all of the lead developers
>
ching, just put them in own namespace, because there is no data
> to hide. All stitch data is in VIA class. So, hope that my idea is
> usable and it is worth of improve.
>
> Regards
>
> Heikki
>
> On Sun, Nov 13, 2016 at 8:03 PM, Wayne Stambaugh
>
nition so the stitch
setting should make no difference.
>
> - Kristoffer
>
>
> On 2017-01-16 22:09, Wayne Stambaugh wrote:
>> Heikki,
>>
>> What is the purpose of the "stitch" token added to the file format?
>> Vias already have a netcode field so adding
eel
> scroll doing the same thing when touchpad panning is enabled. Instead,
> shift+wheel scroll could perform horizontal scrolling in touchpad
> panning mode.
>
> Regards,
> Orson
>
> On 01/16/2017 07:38 PM, Константин Барановский wrote:
>
On 1/17/2017 8:33 PM, Simon Richter wrote:
> Hi,
>
> I just fixed the MSVC build by using a better FindPixman.cmake that
> doesn't make as many assumptions about the system.
>
> There are a few new warnings that popped up:
>
>> fp_lib_table.cpp:182, MSBuild, Priority: Normal
>> 'FP_LIB_TABLE::Pa
On 1/18/2017 11:56 AM, Jean-Samuel Reynaud wrote:
>
> For this particular point, I do exactly the same as
> KICAD_SCRIPTING_MODULES option.
>
> But for both option (KICAD_SCRIPTING_MODULES and
> KICAD_SCRIPTING_ACTION_MENU) you mean that it's better to fail the
> configuration if the options are
Thank you Carl for all of you efforts in maintaining the KiCad
libraries. The KiCad libraries have come a long way.
It's been a privilege working with you. Feel free to join us in the
future should you have the time and interest. Best of luck in all your
future endeavors.
Cheers,
Wayne
On 1/
Thank you Oliver for taking on the responsibility of maintaining the
KiCad libraries. Feel free to contact me if you have any issues or need
any help.
Cheers,
Wayne
On 1/18/2017 9:59 PM, Oliver Walters wrote:
> Hey everyone,
>
> Next time there is a scheduled release, I'll now be the one in ch
This was only a preliminary draft, not final draft which I am still
working on. The legacy canvas is not going to be removed during this
dev cycle. Via stitching is still planned but that could change. We
may have to move the feature freeze back because I still want to get the
new schematic file
I'm not opposed but I agree with your assessment that it needs to not
build when c++14 is defined. Is this something that devs are going to
use or is something we can push off until we are actually a c++14 project?
On 1/22/2017 10:51 AM, Chris Pavlina wrote:
> After reading about the application
Would one of our osx devs test these patches and let me know if I should
commit them. I don't see any coding policy violations so as long as
they fix the problems on osx then I will commit them.
Thanks,
Wayne
On 1/22/2017 5:52 PM, Diogo Condeço wrote:
> Hi all,
>
> I've attached 2 patches for
On 1/23/2017 8:30 AM, jp charras wrote:
> Le 23/01/2017 à 14:19, Nick Østergaard a écrit :
>> Should it be enabled in the windows nightlies now or should we wait a bit?
>>
>
> Before enabling it, please wait for a few tests from devs and J-S.
> Perhaps also a bit of doc and 2 or 3 samples which do
> panning and such work.
>
> On 23 January 2017 at 12:34, Wayne Stambaugh wrote:
>> Would one of our osx devs test these patches and let me know if I should
>> commit them. I don't see any coding policy violations so as long as
>> they fix the problems on osx then I wil
Diogo,
Your patches have been pushed to the master branch. Thank you for your
contribution to KiCad.
Cheers,
Wayne
On 1/22/2017 5:52 PM, Diogo Condeço wrote:
> Hi all,
>
> I've attached 2 patches for some SetFocus optimisations on Macos. Tested
> also on Linux where there wasn't the issue, an
;
>
> Many thanks,
> Diogo
>
> On Sun, Jan 22, 2017 at 8:59 PM, Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
>
> This was only a preliminary draft, not final draft which I am still
> working on. The legacy canvas is not going to be removed dur
Yes, this should be corrected. Double quotes in strings are quoted with
a backslash just like C strings.
On 1/24/2017 8:21 PM, Chris Pavlina wrote:
> In the file format specification at [1] via [2], we specify the
> following for string escapes:
>
>> Here is a legal string with an embedded quote
@Orson, would you please take a look at this patch when you get a
chance. They both look good to me.
I did see a few coding policy issues. Mostly this:
+if ( selection[0]->Type() == PCB_PAD_T )
which should be:
+if( selection[0]->Type() == PCB_PAD_T )
@John, please clean thes
I don't know for sure but my guess is that you did not enable the
KICAD_USE_OCE build configuration option. You will have install the oce
and oce-dev packages (or whatever they are called on Arch) to build
kicad with this option enabled.
On 1/25/2017 9:39 AM, Jose A. Saumell wrote:
> Hello,
>
>
Just a heads up. Dick's recent EDA_TEXT work exposed a bug in the pcb
file parser that has existed since it was written but was never
triggered due to issues with EDA_TEXT. Please hold off using commit
0c459ced972db24ff70b4efbbc672bbe1ab1f92d or later. I'm expecting a
patch soon to resolve the i
Both \ and " are escaped with \ in the output formatter. See
OUTPUT_FORMATTER::Quotes() in common/richio.cpp for all of the escaped
characters.
On 1/25/2017 5:02 PM, Cirilo Bernardo wrote:
> While we're on the subject of the s-expr formatting; can we ensure that
> all writers use quotes on litera
Would one of our osx devs please test these two patches to make sure
they don't break anything. I tested this on msys2 on windows and linux
but I want to be sure before I push them.
Thanks,
Wayne
On 1/17/2017 8:01 PM, Simon Richter wrote:
> ---
> CMakeModules/FindPixman.cmake | 162
>
On 1/26/2017 2:52 AM, Maciej Sumiński wrote:
> On 01/25/2017 08:14 PM, Diogo Condeço wrote:
>> Hi all,
>>
>> This patch corrects the CMD+C cancel dialog bug on macos... There are still
>> some both in the footprint editor, and the board editor. I will try to
>> patch them once i can get some free t
Just a quick heads up, I pushed the fix that Dick sent me for the pcb
file parser issue in commit d4acfb9f5acf26f6bd479405eb029588d2ff486e.
Thank you for your patience.
Cheers,
Wayne
___
Mailing list: https://launchpad.net/~kicad-developers
Post to
If no one is opposed to adding spin controls to the 3D model selection
dialog, I'll commit this patch when I get a chance. I've never been
convinced that using a spin control to change a floating point number is
terribly useful but I'm guessing some users will prefer this over manual
entry of calc
I'm
guessing that wxWindow::FindFocus() will return that window called from
Show() so you do not need direct access to the pointer to the control.
I could be wrong but it should be fairly easy to test.
>
> On Thu, Jan 26, 2017 at 2:26 PM, Wayne Stambaugh <mailto:stambau...@gmail.com>&
would not apply this patch.
>
> Mario
>
> From: Kicad-developers
> [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of
> Wayne Stambaugh [stambau...@gmail.com]
> Sent: 26 January 2017 14:49
> To: kicad-developers@lists.
Would one of our osx devs please test the attached patch? Dick sent me
this patch to fix the long standing issue of building _pcbnew.kiface
twice. It works fine on windows and linux but the fix requires copying
_pcbnew.kiface with the correct python extension and I'm not so sure
this isn't going
Simon,
Thanks for testing this. It was on my list but it looks like it has to
be fixed before we can commit it.
Cheers,
Wayne
On 1/23/2017 10:09 AM, Simon Wells wrote:
> this seems broken on pcbnew when python is enabled at least on osx. getting
>
> Air:~ simon$ /Volumes/simon/kicad-app/bin/k
Patch committed. Thanks Simon.
On 1/27/2017 4:20 AM, Simon Richter wrote:
>
> The common library uses CURL.
> ---
> common/CMakeLists.txt | 1 +
> 1 file changed, 1 insertion(+)
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
>
;
>> The only change I did to the code was to change the stepping of the offset
>> to 0.1mm instead of 1 in this patch. the best thing is that you can now use
>> the scrollwheel as well. Wich makes rotating stuff a breeze.
>>
>> - Kristoffer
>>
>> On 20
To all of our library developers who are adding footprints, please do
*not* use nightly builds to create or edit footprints for inclusion into
the github libraries. If you do, they will not load due to bug in the
parser that was recently exposed by refactoring of the EDA_TEXT object.
Until further
:
> Forwarding to kicad-lib-comitters.
>
> -- Forwarded message --
> From: Wayne Stambaugh
> Date: 2017-01-27 14:23 GMT+01:00
> Subject: [Kicad-developers] Footprint library developer notice.
> To: KiCad Developers
>
>
> To all of our library develo
gt; Glad to hear it!
>
> Also, I found that incrementing in steps of 10 for the rotations misses
> 45 deegrees, so changed that to 5 and made it wrap around at 180 as well.
>
> Attaching that one!
>
> -Kristoffer
>
> On 2017-01-27 13:47, Wayne Stambaugh wrote:
>>
I finally got the new schematic I/O plugin fully functional for the
current schematic and symbol library file formats. When you have some
time, please test this to see if I've missed anything. I've pushed it
to my repo on launchpad here:
https://code.launchpad.net/~stambaughw/kicad/+git/kicad-de
On 1/27/2017 6:02 PM, Chris Pavlina wrote:
> On Fri, Jan 27, 2017 at 05:21:42PM -0500, Wayne Stambaugh wrote:
>> I finally got the new schematic I/O plugin fully functional for the
>> current schematic and symbol library file formats. When you have some
>> time, please tes
On 1/27/2017 7:07 PM, Simon Richter wrote:
> On 27.01.2017 23:21, Wayne Stambaugh wrote:
>
>> I finally got the new schematic I/O plugin fully functional for the
>> current schematic and symbol library file formats. When you have some
>> time, please test this to see
On 1/27/2017 7:40 PM, Chris Pavlina wrote:
> On Fri, Jan 27, 2017 at 07:28:09PM -0500, Wayne Stambaugh wrote:
>> On 1/27/2017 6:02 PM, Chris Pavlina wrote:
>>> On Fri, Jan 27, 2017 at 05:21:42PM -0500, Wayne Stambaugh wrote:
>>>> I finally got the new schematic I/O p
to determine which ones need fixing?
>
> Regards,
> Oliver
>
> On 28 Jan 2017 01:16, "Wayne Stambaugh" <mailto:stambau...@gmail.com>> wrote:
>
> I forgot to mention, if you created or modified any footprints with
> nightly build d4acfb9f5acf26f6bd479
On 1/27/2017 7:40 PM, Chris Pavlina wrote:
> On Fri, Jan 27, 2017 at 07:28:09PM -0500, Wayne Stambaugh wrote:
>> On 1/27/2017 6:02 PM, Chris Pavlina wrote:
>>> On Fri, Jan 27, 2017 at 05:21:42PM -0500, Wayne Stambaugh wrote:
>>>> I finally got the new schematic I/O p
Dick graciously provided a small patch to restore the board file format
to what it was before the EDA_TEXT refactor. I pushed this patch as a
temporary measure to keep users happy until the version 5 stable
release. I am going to remove control bit provides the backwards
compatibility in the the
> On Fri, Jan 27, 2017 at 05:21:42PM -0500, Wayne Stambaugh wrote:
>> I finally got the new schematic I/O plugin fully functional for the
>> current schematic and symbol library file formats. When you have some
>> time, please test this to see if I've missed anythi
On 1/28/2017 3:56 PM, Chris Pavlina wrote:
> Hi,
>
> A number of users have been confused by the fact that the order of
> toolbar buttons in eeschema no longer corresponds to the order in which
> the tools are used, since changing the function of cvpcb. This patch
> reorders them to:
>
> https://
rt, it shows "Library: none" in
> the status bar, and if I press ctrl+E over the part, libedit makes me
> select a library.
>
> On Fri, Jan 27, 2017 at 05:21:42PM -0500, Wayne Stambaugh wrote:
>> I finally got the new schematic I/O plugin fully functional for the
>&
Thank you Alejandro. The refactoring looks good and the unit tests are
a nice touch. Since this patch is rather large, it might be worthwhile
pushing this to a new branch in you own development repo on launchpad so
other devs can clone it or merge it into there own development repos.
Developers,
This seems fine to me.
On 1/30/2017 4:57 PM, Chris Pavlina wrote:
> Hi,
>
> This patch makes libedit preselect the current part when choosing the
> next part to edit. That makes it easier to go through a library one part
> at a time and not lose your place. I figure this is pretty
> noncontrovers
windows. I'm not sure I'm good with this
regression. Anyone else have any thoughts on this.
On 1/30/2017 1:20 PM, Kristoffer Ödmark wrote:
> Hello!
>
> The patch now works under windows, mac and linux.
>
> -Kristoffer
>
> On 2017-01-27 16:40, Wayne Stambaugh
Welcome to the joys of cross platform development. :)
On 1/31/2017 1:18 AM, Kristoffer Ödmark wrote:
> I will look into it, the difference in behavior between the oses is very
> strange.
>
> -Kristoffer
>
> On Jan 31, 2017 2:30 AM, "Wayne Stambaugh" <mail
On 1/31/2017 10:55 AM, Chris Pavlina wrote:
> On Tue, Jan 31, 2017 at 10:45:42AM -0500, Wayne Stambaugh wrote:
>> On 1/31/2017 10:36 AM, Chris Pavlina wrote:
>>> On Tue, Jan 31, 2017 at 11:32:40PM +0800, John Beard wrote:
>>>> Hi,
>>>>
>>>
On 1/31/2017 10:32 AM, John Beard wrote:
> Hi,
>
> The attached patches add the "exchange footprints" command to the GAL edit
> tool.
>
> This is 1 out of 3 parts of
> https://bugs.launchpad.net/kicad/+bug/1541460. I'm not sure how to put
> this as a commit comment exactly.
I changed the descri
Diogo,
Please pay attention to you code formatting. I saw:
if ( ... )
instead of:
if( ... )
more than once in your patch.
Thanks,
Wayne
On 1/31/2017 2:13 PM, Chris Pavlina wrote:
> /home/cmp/git/kicad/eeschema/dialogs/dialog_edit_one_field.cpp: In member
> function ‘virtual bool DIALOG_ED
>>
>> My 2 cents,
>> Mario Luzeiro
>> ________
>> From: Kicad-developers
>> [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on
>> behalf of Wayne Stambaugh [stambau...@gmail.com]
>> Sent: 31 January 2017 0
eed to select a
>> different build tool.
>> CMake Error: CMake was unable to find a build program
>> corresponding to "MSYS
>> Makefiles". CMAKE_MAKE_PROGRAM is not set. You probably
>> need to select
..@gmail.com>> wrote:
>>
>> Just a side note... This is working 100% in macos... The focus is
>> working just fine... on 3D preview it zooms in and out...
>>
>> On Tue, Jan 31, 2017 at 8:03 PM, Wayne Stambaugh
>> mailto:stambau...@gmai
Thanks Bernhard. I'll commit the patch as soon as I get a chance.
On 2/1/2017 11:44 AM, Bernhard Stegmaier wrote:
> Seem to work fine for my setup (dependencies using MacPorts).
>
>
> Regards,
> Bernhard
>
>> On 26.01.2017, at 15:02, Wayne Stambaugh wrote:
&g
Your patches have been committed. Thanks!
On 1/17/2017 8:01 PM, Simon Richter wrote:
> ---
> CMakeModules/FindPixman.cmake | 162
> +++---
> 1 file changed, 135 insertions(+), 27 deletions(-)
>
>
>
> ___
> Mailin
I don't have a strong opinion one way or another but you should never
underestimate the power of branding. You can take the same car and
change the manufacturer and model names and the same person who liked
the car under one brand name will hate it under another brand name. I
never understood thi
s
> confused them as beginners, and only established developers have argued
> in favor of keeping them. ;)
>
> On Thu, Feb 02, 2017 at 12:40:10PM -0500, Wayne Stambaugh wrote:
>> I don't have a strong opinion one way or another but you should never
>> underestimate the
On 2/2/2017 1:03 PM, Andy Peters wrote:
>
>> On Feb 2, 2017, at 10:40 AM, Wayne Stambaugh wrote:
>>
>> I don't have a strong opinion one way or another but you should never
>> underestimate the power of branding. You can take the same car and
>> change th
ight on this.
>
> On Thu, Feb 02, 2017 at 11:03:48AM -0700, Andy Peters wrote:
>>
>>> On Feb 2, 2017, at 10:40 AM, Wayne Stambaugh wrote:
>>>
>>> I don't have a strong opinion one way or another but you should never
>>> underestimate the powe
Did anyone of our osx devs get a chance to test this patch yet? I would
like to get it merged. It saves a nice chunk of time from builds.
Cheers,
Wayne
On 1/26/2017 11:42 AM, Wayne Stambaugh wrote:
> Would one of our osx devs please test the attached patch? Dick sent me
> this patch
On 2/2/2017 1:33 PM, jp charras wrote:
> Le 02/02/2017 à 15:41, Pedro Martin a écrit :
>> Hi Chris,
>>
>> Maybe "Composant Vers pcb"? Component to pcb.
>
> Pedro, you are the winner!
> Merci, Pedro.
Know we all know. :) Thanks JP!
>
>>
>> Related to the other names, I don't mind.
>>
>> I vote
o change in that cmakelists, esspecially in
> regards to OSX and the order of things/when things are done
>
> On 3 February 2017 at 07:28, Wayne Stambaugh wrote:
>> Did anyone of our osx devs get a chance to test this patch yet? I would
>> like to get it merged. It saves
On 2/2/2017 7:40 PM, Cirilo Bernardo wrote:
> Hi folks, I'm fishing for comments on the handling of the 3D file caches:
>
> 1. As it is, the code is pretty good at regenerating a cache file when the
> model changes but there are a few exceptions such as when ModelA
> references ModelB and ModelB
On 2/3/2017 7:14 AM, jp charras wrote:
> Le 02/02/2017 à 20:20, Pedro Martin a écrit :
>> There is still the secret of the meaning of the Ki of Kicad.
>>
>> Regards,
>> Pedro.
>>
>
> Well, Ki has no meaning.
> But Ki has a story.
>
> A long time ago I was looking for a name, a good name.
> A good
To all our FOSDEM attendees. I've arrived in Brussels. I'm going to
get dinner and then I'll head over to the FOSDEM beer event to see what
that's all about. It's 5:50PM local time so I should be at the beer
event around 7PM. Hope to see some of you there.
Cheers,
Wayne
_
Oliver,
Thanks for looking at this. I was trying to find time to look at this
today but the airline has made a complete mess of things so all of my
between flight time has been spent at customer service. :( I'll try too
look at your patch if I have time between flights.
Sorry everyone for being
On 2/6/2017 7:59 AM, Chris Pavlina wrote:
> Eagle converts should like it, it's rather inspired by their component
> selector... ;)
>
> It's coming together nicely. Footprint preview/selection won't be done
> until probably the end of the week, but for now I just got clickable
> datasheet links to
On 2/6/2017 3:02 PM, Chris Pavlina wrote:
> On Mon, Feb 06, 2017 at 02:55:35PM -0500, Wayne Stambaugh wrote:
>> On 2/6/2017 7:59 AM, Chris Pavlina wrote:
>>> Eagle converts should like it, it's rather inspired by their component
>>> selector... ;)
>>>
&
I committed this patch. Thanks Oliver. Please keep in mind when
submitting patches that fix bugs to include the bug report information
in the commit message. At a minimum, "Fixes: lp:##" is required.
It's also not a bad idea to include the link to the bug report even
though our commit hook s
On 2/7/2017 9:00 AM, Chris Pavlina wrote:
> On Tue, Feb 07, 2017 at 08:57:23AM -0500, Jon Evans wrote:
>> Hi Simon, JP,
>>
>> I understand the issue with the colors chosen for OR-mixing. I thought a
>> good first step would be to set the framework for the future when that is
>> no longer relevant
On 2/7/2017 8:29 AM, Chris Pavlina wrote:
> Commit43cb4560bfcf0624e9707c4c512cc3ccce385ce9
>
> Rewrite code for PANEL_PREV_3D because the way events were previously managed
> are not compatible with a good mouse event management.
> To avoid a lot of tedious code, wxFormbuilder is used to
wxColour if it were not possible
> to choose "bad" colors in the the layout tool? It would be easy to
> restrict the colors to the current set in the pcb/footprint editors and
> just allow user selection in the schematic/symbol editors for now.
>
> On Tue, Feb 7, 20
901 - 1000 of 5946 matches
Mail list logo
