Hi Wayne,
I see the fragment code you mentioned, it is untouched. I will keep the
patches as a part of the library manager branch, so they get some extra
testing.
Cheers,
Orson
On 11/13/2017 12:05 AM, Wayne Stambaugh wrote:
> Hey Orson,
>
> Keep in mind that the symbol does not know which libra
>
>
> I like it. What options would you put in the "library options" section?
I'm not sure. I include it only with the thought that perhaps in the future
we will have global library options. It would probably not be present in
the initial version of the dialog.
On Mon, Nov 13, 2017 at 8:10 AM, T
Hey Orson,
Keep in mind that the symbol does not know which library it is in. That
is determined when the library is parsed in SYMBOL_LIB_TABLE. As long
as you don't break that, I cannot think of a reason not to unify the
symbol name but then again there are some quirks in the schematic code
tha
Hi,
I think this is a question to Wayne, but if others have any idea what
may go wrong, do not hesitate to reply.
I have noticed that part name and library values are duplicated in a few
places in LIB_PART class and it is possible to set them individually. It
means there is a way to set each of t
Tom,
Are planning on this being part of the stable 5 release? If so, you
have until Orson finishes up his symbol library editor work. Once that
is merged, I'm announcing the feature freeze.
On 11/12/2017 04:10 PM, Tomasz Wlostowski wrote:
> On 12/11/17 01:44, Oliver Walters wrote:
>
> Hi Olivi
On 12/11/17 01:44, Oliver Walters wrote:
Hi Olivier,
Many thanks for your comments, my answers below:
> Regarding the "advanced options" button, why not have an extra button
> (next to Add / Remove / etc) which says "Edit". Clicking on this brings
> up a dialog for the selected library with all
On 11/12/2017 07:13 AM, Russell Oliver wrote:
> Hi Lachlan,
>
> I was the main developer of the Eagle schematic import plugin and I know
> the layout of the Pcbnew Eagle import code pretty well. So If you can
> describe further the errors you are seeing that would be great, even if
> its just l
Hi,
I've just submitted a pull request (
https://github.com/KiCad/kicad-website/pull/236) trying to make a bit more
clear when/why you need to update the libraries. Also adding links to
github lib repos. Comments welcome :)
Thanks,
Diego
On Sun, Nov 5, 2017 at 10:33 PM, Diego Herranz <
diegoherr
Thanks Mark! I'll file this away for future reference.
On 11/12/2017 10:07 AM, Mark Roszko wrote:
> FYI, here's how you add icons
>
> https://github.com/KiCad/kicad-website/commit/893c902228c5d0a0d6fdbcdf783878cbbd439f6e
>
> Never did figure out how to make hugo set global asciidoc parameters
>
FYI, here's how you add icons
https://github.com/KiCad/kicad-website/commit/893c902228c5d0a0d6fdbcdf783878cbbd439f6e
Never did figure out how to make hugo set global asciidoc parameters
On Fri, Nov 10, 2017 at 2:28 PM, Wayne Stambaugh
wrote:
> I was hoping the icon would draw user's attention
Константин,
I merged your patch into the development branch. Thank you for your
contribution to KiCad.
Cheers,
Wayne
On 11/12/2017 07:20 AM, Константин Барановский wrote:
> --- a/common/wildcards_and_files_ext.cpp
> +++ b/common/wildcards_and_files_ext.cpp
> @@ -139,7 +139,8 @@ wxString EagleS
Marco,
Thanks for the heads up. I just pushed the fix.
Cheers,
Wayne
On 11/12/2017 05:30 AM, Marco Ciampa wrote:
> eeschema/lib_export.cpp:160
>
> "Write permissions are requured to save library '%s'."
>
> TIA
>
> --
>
>
> Marco Ciampa
>
> I know a joke about UDP, but you might not get i
Remove inappropriate tooltip "Unload the selected library" from Remove
button of Equ files dialog in CvPcb.
From 05410b907dfdbc37c4558ce2c8d0d4039a7fd41d Mon Sep 17 00:00:00 2001
From: Baranovskiy Konstantin
Date: Sun, 12 Nov 2017 14:17:20 +0200
Subject: [PATCH] Remove inappropriate tooltip from R
--- a/common/wildcards_and_files_ext.cpp
+++ b/common/wildcards_and_files_ext.cpp
@@ -139,7 +139,8 @@ wxString EagleSchematicFileWildcard()
wxString EagleFilesWildcard()
{
-return _( "Eagle XML files (*.sch *.brd)|*.sch;*." ) +
FormatWildcardExt( "brd" );
+return _( "Eagle XML files (*.s
Hi Lachlan,
I was the main developer of the Eagle schematic import plugin and I know
the layout of the Pcbnew Eagle import code pretty well. So If you can
describe further the errors you are seeing that would be great, even if its
just links to the original Eagle files and screen shots of the offe
Wayne,
Another potential spanner in the works - the footprint files do not store
the file version information. (should they?)
Thus, footprint files cannot be parsed differently based on their file
version. Changing "at" between mm and inches will work for the pcb but not
for the individual footpr
eeschema/lib_export.cpp:160
"Write permissions are requured to save library '%s'."
TIA
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
GNU/Linux User #78271
FSFE fellow #364
___
17 matches
Mail list logo
