kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

Wayne, I can pull the text into the DMG or else link to it--Seth's
idea of putting some text in the background to tell users who are
upgrading to actually read the README will remove any guilt I have
about excited users just assuming they know what to do and skipping
any docs.

Rather than a "we try to fix it" solution, is there any way for us to
just nag people based on a simple heuristic?  I have been heads-down
in esoteric macOS loader/linker/Python land for too long to know what
is going on with the majority of KiCad v5 :) but can we do something
like compare the sym lib and the fp lib and see if we think the sym
lib is v6 and the fp lib looks v5, we aim them at some online docs in
a nag window, along with a checkbox for "I know what I'm doing, please
don't ask me this again" that we save in preferences?  Please feel
free to literally ignore me if this is completely wrong.

Adam Wolf
On Fri, Jun 22, 2018 at 7:28 AM Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>
> On 06/22/2018 01:05 AM, Carsten Schoenert wrote:
> > Hi,
> >
> > Am 22.06.2018 um 04:52 schrieb Adam Wolf:
> > ...
> >> Is there any way we can detect if the fp-lib-table is out of sync and
> >> tell a user at run time?
> >
> > I'm too seeing this point not only related to the update now from V4 to
> > V5 and this is completely unrelated to the OS the user is running on at all.
> >
> > For my rather small local environment it was quite fast to remove the
> > old file and let KiCad put the new default file in place. But in more
> > complex installations this doing is very annoying and error prune
> > because users need to deal with manual reading of content. KiCad needs
> > some better (automatic) handling here. But not only telling the user
> > some required update, also doing this in a automatic way.
> >
>
> This is not a trivial fix.  Blindly copying the default global library
> tables every time they change would overwrite any user customization
> which is a not an option.  It then becomes a merge operation which is
> far more complex.  I'm not opposed to an optional merge solution if
> someone has the time to implement it.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp