Now that RC2 is released, can we get a new target in the bug tracker for
things that should be fixed prior to v5 release? Currently, we only have
v6 as a target
Thanks-
Seth
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
but I needed to
rebase it to master before doing that. The conflicts were with inserting
the aWorker-CheckInterrupt() conditional in the itemList search.
-S
Am Fr., 25. Mai 2018 um 08:35 Uhr schrieb Tomasz Wlostowski <
tomasz.wlostow...@cern.ch>:
> On 25/05/18 05:16, Seth Hillbr
Hi All-
Here's an updated patch for working with large, complex boards in v5.
Tom, I took your advice and put a light layer over an RTree for the
connectivity search. Since this gets us bounding box collisions, we can do
commutative hits by using both items in the collision, eliminating the
Orson-
The new one looks good here.
I'd vote for skipping the extra string field for now and ignore hidden
files.
-S
Am Do., 24. Mai 2018 um 01:20 Uhr schrieb Maciej Sumiński <
maciej.sumin...@cern.ch>:
> Attached a revised patch set, as the previous one looked ugly on Windows
> (and fine
Hi Jeff-
I believe that this distinction has been removed for V5 with the new
connectivity algorithm (Tom, please correct me if I'm mistaken in this!)
-S
Am So., 29. Apr. 2018 um 02:19 Uhr schrieb Jeff Young :
> There was a discussion on the forum regarding the difference
ca Mini*
> > Via Brione, 11/C
> > 10040 Givoletto (TO)
> > EMAIL: luca.mini.freela...@gmail.com
> > <mailto:luca.mini.freela...@gmail.com>
> > Cell: +39 334 2459673
> >
> > 2018-05-21 18:54 GMT+02:00 Wayne Stambaugh <stambau...@gmail.com
> > &l
Hi Alexis!
Congrats and welcome! Good luck on your KiCad talk. If you're willing, it
would be neat to see your slide deck or, better yet, your presentation but
beggars and choosers, right?
Best-
Seth
Am Di., 22. Mai 2018 um 10:10 Uhr schrieb Chris Pavlina <
pavlina.ch...@gmail.com>:
> Hi,
I obvviously disagree, the correct solution would be to
>> > > > > > > have
>> > > > > > > both.
>> > > > > > >This does not hinder that, its not even the same
>> > > > > > > problem.
>> >
Hi Matt-
There's a couple odd things so I'll try to address them individually:
1) revision 30455092c is not KiCad 4. But perhaps you are trying to do
something else. If you wanted KiCad 4, you can checkout the tag with `git
checkout 4.0.7`
2) The variables you show in the build settings
Hi Devs-
Now that Wayne has declared rc2 and strings are frozen, does anyone have
objections to my posting a call for translators to the user forum? I just
checked the open items and it looks like there are a few languages that
haven't been touched in a number of years, so I thought we might
I've opened a bug report to address this item
https://bugs.launchpad.net/kicad/+bug/1772529
Please feel free to add elements to be considered for this feature on the
bug report. Kristoffer, I like the idea behind your patch. Clearly people
have many use cases for this; let's make sure that we
Hi JP-
I'm referring _only_ to the Tools->FreeRoute menu option and the
associated icon (two arrows on a yellow sign) on the menu bar.
-S
Am Mo., 21. Mai 2018 um 09:27 Uhr schrieb jp charras <jp.char...@wanadoo.fr
>:
> Le 21/05/2018 à 18:09, Seth Hillbrand a écrit :
&
Hi Wayne-
There's a couple minor differences between the strings shown the user in
modedit and pcbnew. I'd like to standardize these. This involves removing
a few strings from modedit and replacing them with the strings from
pcbnew. This does not change anything for our translators as we are
Hi Wayne-
In https://bugs.launchpad.net/bugs/1567790 you mentioned that we won't be
supporting FreeRouting for v5. Should we remove this menu item/icon from
the menus?
-S
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
The discussion of 5.x releases was delayed but perhaps seems relevant
again. Should we plan for a 5.1 release as Simon suggests with a goal of
working GTK3? I'm not sure that I agree with his preference for banning
non-GTK3 patches but I do have a preference for avoiding file format
changes
I like the extra tooltips in this, except for line 48 which talks about
centers and anchors interchangeably and is not clear.
-S
Am So., 20. Mai 2018 um 12:41 Uhr schrieb Robbert Lagerweij <
rlagerw...@hotmail.com>:
> Inspired by the discussion on bug 1771424
>
Hi Kristoffer-
This feels like a management issue rather than a tool issue. If the user
doesn't want any extra fields, how would your patch allow that?
-S
Am So., 20. Mai 2018 um 13:00 Uhr schrieb kristoffer Ödmark <
kristofferodmar...@gmail.com>:
> Hello!
>
> I will open this can of worms
Uhr schrieb Tomasz Wlostowski <
tomasz.wlostow...@cern.ch>:
> On 18/05/18 20:49, Seth Hillbrand wrote:
> > Gentle ping here. If this doesn't interfere with your connectivity
> > algorithm work Tom, I'd like to merge these as they make routing the
> > board I'm workin
.de>:
> Hello Seth,
>
> Am 18.05.2018 um 19:27 schrieb Seth Hillbrand:
> >
> > I'll second Tom's suggestion here. Distros are free to package KiCad
> > how they like, but we can create an AppImage[1] with GTK2 and wxpython
> > that users can download from
through cracks.
Best-
Seth
Am Di., 15. Mai 2018 um 17:23 Uhr schrieb Seth Hillbrand <
seth.hillbr...@gmail.com>:
> Hi Tomasz (and others if interested)-
>
> I'm attaching some patches to the connectivity search. I know you are
> looking at moving some of this to a backgroun
I'll second Tom's suggestion here. Distros are free to package KiCad how
they like, but we can create an AppImage[1] with GTK2 and wxpython that
users can download from the website. This would provide a way for all
users to run KiCad even if their distro doesn't package the required
libraries.
as these create many small segments for connection.
Thanks-
Seth
From fe2b4d222a80c9096de41d7707dbaaf6c4f0546c Mon Sep 17 00:00:00 2001
From: Seth Hillbrand <hillbr...@ucdavis.edu>
Date: Thu, 10 May 2018 13:11:53 -0700
Subject: [PATCH 1/5] Move some connectivity search to std::algs
Previously,
Sorry about the broke builds. I've adjusted the FindOCE section to a
better override, restoring how it searched previously. OpenCascade changes
should now only affect builds specifically requesting KICAD_USE_OCC.
-Seth
Am Di., 15. Mai 2018 um 05:42 Uhr schrieb Simon Richter <
Yup, just overlooked in the rush of bug reports. It's been pushed now.
Thanks for your contribution!
-S
Am Fr., 4. Mai 2018 um 05:26 Uhr schrieb Steven A. Falco <
stevenfa...@gmail.com>:
> I got no response to the attached email. Is there a problem with it, or
> was it simply overlooked?
-
Seth
Am Do., 3. Mai 2018 um 12:40 Uhr schrieb jp charras <jp.char...@wanadoo.fr>:
> Le 03/05/2018 à 20:23, Seth Hillbrand a écrit :
> > Hi Devs-
> >
> > I was looking over https://bugs.launchpad.net/bugs/1768862 as it
> relates to the PNS checks.
> >
>
missing anything? The proposed patch (attached here) renames the
SHAPE_CONVEX class to SHAPE_SIMPLE and adjusts how the vertices are added
for custom pads. Do people see any issues with this?
Thanks-
Seth
From 69140b743b9f6e7ce5fa9a94d24a39c0f0898b2b Mon Sep 17 00:00:00 2001
From: Seth Hillbrand
Hi JP-
The patch seems to function as expected. Minor issue is that the pad
properties dialog now opens to the second tab active and doesn't focus (so
pressing escape doesn't work until you click on the dialog).
I'm in favor of the change as long as we keep it minimized like you have.
-S
Hi Bernhard-
Sorry this question got lost in the traffic. Currently all netcodes get
cleared when pasting. This makes sense for most items but maybe not for
zones? It seems this could go either way. Do you have a use case in mind?
-S
Am So., 25. März 2018 um 02:43 Uhr schrieb Bernhard
Hi All-
Fabrizio Tappero pointed out one of the dialogs where we had some
colons/some not for sections. I went through most (all?) dialogs looking
for similar discrepancies to unify the layout appearance and, hopefully,
improve the responsiveness for screen readers as well as helping
I'm a bit late to this conversation so forgive the basic question.
Won't this break things for users that explicitly set XDG_CONFIG_HOME for
other reasons?
-S
2018-04-23 14:29 GMT-07:00 Nick Østergaard :
> Just open a terminal and "set" it as you you do on linux, where you
>
> Also, I believe that the colon (":") in the section title is totally
> superfluous. I the previous window (Print Window) colon is
> used (not really sure why) only in some sections.
>
>
Thanks for pointing out the discrepancy! Colons are useful for some screen
readers to determine when a new
For those of you who use these tools, I've added a couple of optional cmake
flags to integrate them more easily.
-DUSE_DISTCC=ON/OFF
-DUSE_CCACHE=ON/OFF
You can use either or both or neither flags. These default to off, so this
should not affect you unless you use these tools.
If you do use
Hi Darrell-
Please see https://bugs.launchpad.net/kicad/+bug/1466962
Pads on inner layers is a good idea but it needs a full implementation.
This would include (at a minimum) adding the pads to arbitrary layers (not
just In2_Cu), new netnames layers, GAL layers and zone filling
Hi Jon-
The major issue I think we would need to address is migration. I don't
think that only an ERC warning is sufficient in this case. Users will
rightfully expect that their old schematics will generate valid netlists
when opened in a newer KiCad.
One option here would be to translate the
If we are going to support multiple versions, on the developer side, we
should add a preference versioning to the user configuration directory.
Otherwise, fp-lib-table will being either pointing to v4 or v5 footprints.
Likewise, there are a few preferences that only exist in v5 and will be
lost
otation applied not
>> being imported correctly too.
>>
>>
>> On Sat, 31 Mar 2018 14:03 Seth Hillbrand, <seth.hillbr...@gmail.com>
>> wrote:
>>
>>> Hi Russell-
>>>
>>> Will you have time to update this patch? If not, I'm happy to revise it
>
Hi Devs-
Just a heads up that there was a minor issue with the output formatting in
pcbnew when handling invalid polygons. I fixed the issue and pushed
532bf0981. It should have no effect of valid shapes generated in pcbnew
but will prevent invalid boards from being created in the scripting
Hi Russell-
Will you have time to update this patch? If not, I'm happy to revise it to
handle the cases this weekend. We're getting close to rc2 and I'd like to
get your fix in before it is released.
Best-
Seth
2018-03-27 13:12 GMT-07:00 Seth Hillbrand <seth.hillbr...@gmail.com>:
k
> everybody's configuration who uses CHECK_SYMBOL_EXISTS.
>
> On 3/30/2018 5:15 PM, Seth Hillbrand wrote:
> > Hi Adam-
> >
> > You will need to downgrade to CMake 3.10 or lower. In 3.11, they
> > revised the internals of CheckSymbolExists.
>
Hi Adam-
You will need to downgrade to CMake 3.10 or lower. In 3.11, they revised
the internals of CheckSymbolExists.
Our macro depends on the internal CMake macro _CHECK_SYMBOL_EXISTS (note
the underscore at the beginning). In 3.11, they replaced it with
__CHECK_SYMBOL_EXISTS_IMPL.
-S
Hi Thomas-
Your analysis is correct. m_LastEditTime was recently changed to
timestamp_t but holds time_t information and (for now) can be safely cast.
I've pushed an update, let me know if it's still problematic.
-S
(Sorry for the double-email.)
2018-03-29 9:14 GMT-07:00 Thomas Figueroa
GMT-07:00 jp charras <jp.char...@wanadoo.fr>:
> Le 29/03/2018 à 18:04, Seth Hillbrand a écrit :
> > Thanks for the feedback. It helps me get my head around how the
> subsheets are meant to work.
> >
> > Here is one of the bugs:
> >
> > 1) Take the at
inking behavior as is unless people feel otherwise. It
confused me but I think I can clarify it in the dialog text.
-S
Hmm... Apparently Gmail has started blocking my attachments. So here is
the zipped project
https://drive.google.com/file/d/1W9aEzpx_mh4sS2ebtAOPQrw5QeuJrlKK/view?usp=sharing
20
Hi All-
I'm working on a bug in renaming sub-sheets. In testing the fix, I've run
up against a set of conflicting paradigms for how subsheets are handled.
I'd like some feedback on how we expect to handle the subsheets.
Either:
1) we treat them as actual objects such that renaming the sheet's
Russell Oliver <roliver8...@gmail.com>:
> The cream setting is the eagle equivalent to enabling/disabling the
> soldering paste layer for the pad. Hence the change in the layer set.
>
> On Wed, 28 Mar 2018 03:14 Seth Hillbrand, <seth.hillbr...@gmail.com>
> wrote:
&g
use issues down the road. The eventual goal is to implement the
> "property" token to define key/value pairs for third party applications
> to add user specific information to any board object without polluting
> the controlled part of the file format. The beauty of this is that w
Hi Russell-
Thanks for the patch. However, currently, if there is no e.cream setting,
the local solderpaste margin gets set. In your patch, if the setting is
missing, that doesn't happen.
Is this your intention?
-S
2018-03-27 5:06 GMT-07:00 Russell Oliver :
> This
Hi Jeff-
I assume you have a populated cmake build directory. If so, you can run
"make edit_cache" and you should be see what is toggled on and off and
adjust. Then hit "c" to reconfigure and "g" to generate your makefiles.
You can also delete cache entries using this tool, in case there is
CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT is a relatively recent
addition to cmake. Maybe 3.7 or so? I'd hesitate using that in the
install script yet but maybe that's overly cautious. If you do use it, we
need to bump the minimum version at the top as well.
-S
2018-03-22 7:20 GMT-07:00
Hi Eeli-
My comment above was to note that previously, we could get into a state
where you needed to delete the module to get back to a valid board. With
the patch, the state became that you had a valid board but could no longer
delete or edit the module. This is what I meant by solving one
tprint if any of it's layers are removed from the layer
> list and warn the user that removing said layer(s) would result in
> footprints being removed.
>
> Thanks,
>
> Wayne
>
> On 3/20/2018 4:19 AM, Eeli Kaikkonen wrote:
> > 2018-03-20 0:19 GMT+02:00 Se
Hi Jon-
I don't see anything inherently problematic here. Works as advertised and
seems to be minimally invasive.
I suspect that your primary speed bump is the BOARD_COMMIT being called on
each segment error marker. You might get bang for the buck by
conditionally starting a BOARD_COMMIT at
2018-03-19 17:18 GMT-07:00 hauptmech <hauptm...@gmail.com>:
> On 20/03/18 11:19, Seth Hillbrand wrote:
>
> Hi hauptmech-
>
> I disagree with your assessment of whether we should allow the creation of
> broken boards. I don't think that we should ever allow K
uld possibly be comitted as is if that debug log is
> removed. It seems to work fine if you are not switching between OCE and OCC
> in the same build dir, that is, a clean config.
>
> Nick
>
>
> 2018-03-17 0:51 GMT+01:00 Nick Østergaard <oe.n...@gmail.com>:
>
>> Thank
Hi Jeff-
A few questions on how you are implementing this:
1) How does the user know what was skipped? I can imagine team members
with different versions getting into difficulty, especially if the features
being skipped change the board layout.
2) You are removing strict checking for most of
they are a ninja
> doing things that kicad should stay out of the way of or they are a very
> confused beginner for whom a little extra cruft in the file is the least of
> their problems.
>
> -hauptmech
>
>
>
>
> On 15/03/18 05:17, Seth Hillbrand wrote:
>
> Hi haut
Hi Nick-
I finally found a moment to figure out Docker and get this up and running
in your build configuration.
Please take a look when you have a chance and let me know if you have any
issues with this patch.
Best-
Seth
2018-02-10 7:12 GMT-08:00 Seth Hillbrand <seth.hillbr...@gmail.
Hi hautmech-
Looks good. Two comments:
- Code style. There are a couple of small issues: one line is too long,
there should be spaces in parentheses for pad->GetParent()->Remove(pad) and
no space before parentheses in "if ( pad->GetLayerSet()..."
- We need to handle the case where all items
Hi JP-
I gave it a spin and definitely like it! I have been using custom
footprints for capacitive sensors, but this is much better. A couple
thoughts:
1) I'd prefer to have the angle saved as a parameter in the file rather
than a fixed list of options.
2) We'll definitely need to address the
the text color changes. Right now, we
simply ignore units that are mistyped or that we don't know.
-S
2018-03-13 9:18 GMT-07:00 Jeff Young <j...@rokeby.ie>:
> Hi Seth,
>
> https://bugs.launchpad.net/kicad/+bug/1660156
>
> Cheers,
> Jeff.
>
>
> On 13 Mar 2018, at 1
Hi Jeff-
I can't find which bug report this can you send the link? I'm not sure
that I follow what the issue is and I'd like to understand the problem it's
addressing.
Thanks!
-S
2018-03-13 2:58 GMT-07:00 Jeff Young :
> There’s a wishlish item to make support for typed-in
Hi Jeff-
The underscore is a macro to call wxGetTranslation(). There's some null
checking there but more importantly, it returns a wxString that will be
valid regardless of the the contents. If you cast a wxString with no data
to a C string, you still get the valid pointer to the data segment
On MIPS and PPC, the call convention is blank (no special decl). I think
we can just set the default to blank.
Anyone have an objection to this?
-S
2018-03-09 11:05 GMT-08:00 Simon Richter :
> Hi,
>
> On 03/09/2018 07:45 AM, Carsten Schoenert wrote:
>
> > The
You should take a look at Mitja Nemec's action plugin here:
https://github.com/MitjaNemec/Kicad_action_plugins
I think the replicate layout covers a lot of the functionality you are
looking for.
-S
2018-03-07 10:25 GMT-08:00 Andrey Kuznetsov :
> Not sure how you would turn
Hi Tom-
Relevant discussion here:
https://lists.launchpad.net/kicad-developers/msg25762.html
FWIW, I don't think there's a technical reason why.
-S
2018-03-06 9:44 GMT-08:00 Tomasz Wlostowski :
> Hi,
>
> I've been trying to fix [1] without success: ngspice will not
Does the compile error exist after you make clean and re-make?
2018-03-05 10:20 GMT-08:00 Steven A. Falco :
> I just got a build error on Linux, at git commit 218f66a08, which appears
> to be the latest commit.
>
> In file included from
Ha!
Sounds like a job for Alpha Zero to me.
-S
2018-03-05 9:09 GMT-08:00 Tomasz Wlostowski :
> Ladies and gentlemen, there's a lot of work for us ahead!
>
> https://www.reddit.com/r/AskElectronics/comments/
> 815fz2/what_eda_is_really_the_best_out_there_for_macos/
>
I see no issues on Mac OS.
-S
On Mar 4, 2018 10:00 AM, "Wayne Stambaugh" wrote:
> I didn't notice any issues on linux builds. Has anyone else confirmed
> this doesn't break anything on macos builds?
>
> On 03/04/2018 07:26 AM, Bernhard Stegmaier wrote:
> > Hi,
> >
> >
In the current nightly MacOS builds, we package the applications, symbols
and 3d models but no footprints.
Is this an oversight?
-S
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Jeff-
As a fellow refuge from centralized VCSs, I sympathize. It took me a while
to learn to love git branch but it is your friend.
Here's a quick way to get into the layout Wayne was recommending:
git checkout master (you are now in your branch that has all the V6 stuff)
git checkout -b
ey Kuznetsov <kandre...@gmail.com>:
> Only KiCad app has Open in Low Resolution Mode, and I already had it
> enabled!
>
> On Thu, Mar 1, 2018 at 7:53 PM, Seth Hillbrand <seth.hillbr...@gmail.com>
> wrote:
>
>> Andrey-
>>
>> I'm moving thi
Hi All-
I was playing with this last night (don't normally compile on the mac) and
found that using homebrew's llvm 3.8.1 seems to compile fine with
-fopenmp. Running some OMP test code from
https://gist.github.com/sethhillbrand/45dfb50e5a1865ad65bda1d6522778c5
shows expected result of 4
Oops! Noticed that 1+2 should have been in the same patch (fixing my own
bug there)
I've squashed them down to three patches.
-S
2018-02-28 16:52 GMT-08:00 Seth Hillbrand <seth.hillbr...@gmail.com>:
> Attached are 4 patches for various alignment issues.
>
> The fi
most for X-center and top-most for
Y-center. You can then move one item into place and align the others to
it. Delaying this has no affect of the other patches, so I'm happy to hold
it for post-5.
From c861f742e42a1cdb3dccf3a6668a375d3b2c4c25 Mon Sep 17 00:00:00 2001
From: Seth Hillbrand <hillbr..
In case this thread comes up in a search in the future, my commandline for
exporting without the GUI is:
/Applications/Inkscape.app/Contents/Resources/bin/inkscape
--export-area-snap -e
${input}.png -f ${output}.svg -z
Inkscape version 0.48.5
-S
2018-02-26 9:26 GMT-08:00 Jeff Young
Jeff-
Use the "-z" commandline option to execute things without the gui on Mac.
-S
2018-02-26 9:04 GMT-08:00 Nick Østergaard :
> On linux it does not open a GUI, it just converts the images when I make.
>
> 2018-02-26 18:01 GMT+01:00 Jeff Young :
>
>> When I
Jeff-
On my mac, I use /Applications/Inkscape.app/Contents/Resources/bin/inkscape
for the command-line access. It is installed with the standard GUI.
-S
2018-02-26 8:23 GMT-08:00 Jeff Young :
> Yeah, it looks like inkscape and pngcrush.
>
> I have the inkscape GUI app; does it
Playing with the tool some more, I can see that Andrzej is right. There
are a number of missing features in the polygon tool that exist in the zone
editor. Adding corners is a large one.
If you have an existing non-copper zone, it seems you can keep it, change
its layer, add cut-outs, etc.
u draw 10x10mm zone, resulting object will have the same
>> dimensions, but polygon will be 10x10mm + outline width.
>>
>> Andrzej
>>
>>
>> W dniu 2018-02-24 o 00:49, Seth Hillbrand pisze:
>>
>> The graphical polygon tool works for non-copper layers
The graphical polygon tool works for non-copper layers.
Andrzej, does this tool not work?
-S
2018-02-23 15:28 GMT-08:00 Wayne Stambaugh :
> Orson,
>
> Is there any reason not to allow zones to be drawn on non-copper layers?
> The changes you made in this commit would
Hi Jeff-
I was working on that but just got slammed at work, so there's been less
time for testing/fixing all of the places where it touches. But there's a
three-day weekend coming up here in the states, so I'm hopeful (eternally
so) that there will be sufficient time to complete it.
That said,
reatly appreciate it!
-S
From 814ec9885a1a07a882b598d4c77f5cccf57c3242 Mon Sep 17 00:00:00 2001
From: Seth Hillbrand <hillbr...@ucdavis.edu>
Date: Wed, 14 Feb 2018 13:37:43 -0800
Subject: [PATCH] Eeschema: Set initial default widths in BOM editor
---
eeschema/dialogs/dialog_fields_editor_global.cpp | 2 +-
ee
ditor can
>>>>>>>> also save an entire library file without going through the
>>>>>>>> fp-lib-table so
>>>>>>>> it's important that we don't break this behavior. I may have missed
>>>>>>>> this
> Seth,
>
> What is the current status of this patch? I would like to get it merged
> before rc1 so the package devs can test it.
>
> Cheers,
>
> Wayne
>
> On 01/30/2018 02:12 PM, Seth Hillbrand wrote:
> > Nick-
> >
> > Thanks for the test. I'm attach
ork for 7.1 for me either. It should be
> noted, that
>
> I built OpenCascade from source, and I’ve tried to manually change it to
> point
>
> to the Standard_Version header, but it still doesn’t parse it correctly
> with the same
>
> error outputted.
>
>
>
in_oce otherwise (unresolved symbols SelectMgr_Selection,
> PrsMgr_PresentableObject, and AIS_InteractiveObject respectively).
>
> I also had to remove the version checking, as it was unable to get the
> version via regex matching for some reason.
>
>
>
> -Thomas
>
>
>
>
erwise, the patch wont mean anything once the new file formats are
> complete.
>
> Thanks,
>
> Wayne
>
> On 1/26/2018 3:00 PM, Seth Hillbrand wrote:
> > Wayne-
> >
> > Would you object to a patch like the attached? It reads the name line
> > in reverse ord
Hey Seth,
>
>
>
> I was able to successfully use OpenCascade 7.1 and export using kicad2step!
>
>
>
> Now to find out why…
>
>
>
> -Thomas
>
>
>
> *From: *Seth Hillbrand <seth.hillbr...@gmail.com>
> *Sent: *Friday, February 2, 2018 11:10 AM
> *To:
Jeff-
Will removing a footprint library trigger a refresh? Or will that mess up
the checksum calculation?
-S
2018-02-05 13:04 GMT-08:00 Jeff Young :
> This one for Place Footprint (specifically the List All dialog found
> therein).
>
> On my machine it knocks the first-use
Well done Wayne. Excellent talk and congrats on the DigiKey donation!
2018-02-04 12:13 GMT-08:00 Piotr Esden-Tempski :
> haha! it is! Well I guess I rewatch the talk from last year first to get
> ready for the one from this year… to try to reverse the confusion I might
>
lete, errors occurred!
> See also "/home/nickoe/kicad-source-mirror/test/CMakeFiles/
> CMakeOutput.log".
> See also "/home/nickoe/kicad-source-mirror/test/CMakeFiles/
> CMakeError.log".
>
>
> If you like I can share a Dockerfile which tries to replicate
try them out.
>
>
>
> - Thomas
>
>
>
> *From:* Kicad-developers <kicad-developers-bounces+tom_figueroa=
> hotmail@lists.launchpad.net> *On Behalf Of *Seth Hillbrand
> *Sent:* Monday, January 29, 2018 12:55 PM
> *To:* KiCad Developers <kicad-devel
eas, I’d be very willing
> to try them out.
>
>
>
> - Thomas
>
>
>
> *From:* Kicad-developers <kicad-developers-bounces+tom_figueroa=
> hotmail@lists.launchpad.net> *On Behalf Of *Seth Hillbrand
> *Sent:* Monday, January 29, 2018 12:55 PM
>
> the code under GPLv3 to make the desired combination. To learn more
> about compatibility between GNU licenses, please see our FAQ."
>
> I hope this clarifies why I am hesitant to merge this patch and what
> needs to clarified. Isn't licensing fun! ;)
>
> Thanks,
>
lating and
> licensing terms.
>
> Cheers,
>
> Wayne
>
> [1]: https://www.opencascade.com/content/licensing
> [2]: https://www.gnu.org/licenses/license-list.en.html#
> GPLCompatibleLicenses
>
> On 1/29/2018 1:54 PM, Seth Hillbrand wrote:
> > Hi All-
> >
t about the
> slashes?
>
> Tom
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://h
Works great for me as well. Thanks Jeff!
Seth
On Jan 26, 2018 4:49 AM, "jp charras" wrote:
> Le 25/01/2018 à 16:24, Jeff Young a écrit :
> > More performance enhancements:
> >
> > 1) Edit Symbol gets similar fix as Place Symbol
> > 2) progress-dialog-updating reduced to
Filter would actually increase
> the cross-section, rather than decreasing it.
> >
> > I’ve attached another version of the patch which includes Orson’s
> changes along with a guard for the issue you mentioned earlier. Can you
> let me know if it helps?
> >
> &
I observe a similar issue following Orson's procedure and the new patch.
For me, the selection tool will lock selected when there is no element in
the selection, causing the screen to scroll when I move the mouse to the
edge and I can't get out of the tool selection.
I tried to poke through the
hat clearly says
>> this.
>>
>>
>>
>> On 11/01/2018 13:16, Clemens Koller wrote:
>>
>>> Hi!
>>>
>>> On 2018-01-11 02:07, Seth Hillbrand wrote:
>>>
>>>> I don't recall when this change happened but I'd like any f
801 - 900 of 975 matches
Mail list logo