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 plugin fully functional for the
>
There shouldn't be that many since the bug was only introduced 3 days
ago. The best way I know of is to look at the text objects in in the
module and see if the hide token is inside the effects definition. If
it is, then it has been created with the broken code.
Tomorrow I'm going to commit a pa
Wayne,
This could (potentially) impact many footprints, although the majority of
new additions have been scripted using external python toolset.
Is there a quick-n-dirty way of grepping all .kicad_mod files to search for
this bug, to determine which ones need fixing?
Regards,
Oliver
On 28 Jan 2
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 plugin fully functional for the
>
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 plugin fully functional for the
> >> current schematic and symbol library file
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 if I've missed anything. I'v
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 test this to see if I've mis
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 if I've missed anything. I've pushed it
> to my repo on launchpad here:
> htt
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 anything. I've pushed it
> to my repo on la
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
Hi all,
As we discussed attached is a patch to correct SetFocus issues and the
CancelButtonIssue.
SetFocus requires DLGSHIM_USE_SETFOCUS to be set, which is only set when
__WXMAC__ is defined.
I've tested this on my system and it is working -> example is the eeschema
edit reference value dialog w
Here is a patch for a couple of consts in class BOARD, plus a
suspicious const return-by-value (which does nothing but disable move
operations).
I looked at GetBoardPolygonOutlines too, but that needs the
GetBoardPolygonOutlines function in specctra.cpp to be constified, and
theres (at least) a me
This doesn't work on windows at all. Changing any of the values either
with the spin buttons or direct entry into the edit control does not
update 3D view of the model. This issue will need to be resolved before
the patch can be committed.
On 1/27/2017 8:16 AM, Kristoffer Ödmark wrote:
> Glad to
I forgot to mention, if you created or modified any footprints with
nightly build d4acfb9f5acf26f6bd479405eb029588d2ff486e or later, please
revert the changes or users will not be able to open them. I apologize
for any inconvenience.
Cheers,
Wayne
On 1/27/2017 8:36 AM, Nick Østergaard wrote:
>
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 developers who are adding footprints, please do
*not* use
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
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:
It's on my list for today. It would be nice if an
It's on my list for today. It would be nice if an osx dev could test it
before it's committed just in case there is some unexpected behavior on osx.
On 1/27/2017 7:43 AM, Chris Pavlina wrote:
> Just tried this. It's REALLY nice to be able to nudge the model around
> by turning the scroll wheel ov
Just tried this. It's REALLY nice to be able to nudge the model around
by turning the scroll wheel over the fields. <3
Anyone test this on something other than Linux yet? I'd like to see this
merged.
On Thu, Jan 26, 2017 at 05:24:17PM +0100, Kristoffer Ödmark wrote:
> Yes, you can still manually
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
>
Le 27/01/2017 à 13:02, Jean-Noël AVILA a écrit :
> Le 27/01/2017 à 12:50, jp charras a écrit :
>> Le 27/01/2017 à 12:26, Chris Pavlina a écrit :
>>> I noticed the artifacts in the code too, but didn't see anything in the
>>> graphic.
>>>
>>> I would definitely take another update from anyone who wa
JP, even in your country the BIPM says kilo is lowercase "k":
http://www.bipm.org/en/measurement-units/prefixes.html
I have absolutely no idea what you mean by the "legal" notation,
everything I can find published by any standards organization whatsoever
(again, including BIPM who 1. is French, 2.
Le 27/01/2017 à 12:26, Chris Pavlina a écrit :
> I noticed the artifacts in the code too, but didn't see anything in the
> graphic.
>
> I would definitely take another update from anyone who wants to further
> edit this:
>
> - Remove any artifacts that may be present
> - Use lower-case "k"
Inter
I noticed the artifacts in the code too, but didn't see anything in the
graphic.
I would definitely take another update from anyone who wants to further
edit this:
- Remove any artifacts that may be present
- Use lower-case "k"
- Center the multiplier column better
On Fri, Jan 27, 2017 at 05:08
Dear All,
As requested please find attached a patch to create 2 samples for the
action menu:
- add_automatic_border.py
Automaticaly found smaller area including all modules/coper area/text...
and build or update rectangular PCB edge
- text_by_date.py
Change any text with content "$date$" on the P
The common library uses CURL.
---
common/CMakeLists.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/common/CMakeLists.txt b/common/CMakeLists.txt
index e9c7e4338..549a2c86b 100644
--- a/common/CMakeLists.txt
+++ b/common/CMakeLists.txt
@@ -4,6 +4,7 @@ include_directories(
./dialog_ab
Hi,
this is for the 4.0 branch, and fairly obvious, I think. The master branch
already has this.
Simon
Simon Richter (1):
Add missing include directory
common/CMakeLists.txt | 1 +
1 file changed, 1 insertion(+)
--
2.11.0
___
Mailing list: ht
27 matches
Mail list logo
