Location of settings

Asked by Chris Gibson

Where are the custom field names stored for eeschema? I've googled and find the same question asked many, many, times, but never answered. Searching my entire computer fails to find them. I'm baffled!

Question information

Language:
English Edit question
Status:
Solved
For:
KiCad Edit question
Assignee:
No assignee Edit question
Solved by:
Chris Gibson
Solved:
Last query:
Last reply:
Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#1

Sent from my Galaxy S®III

-------- Original message --------
From: Chris Gibson <email address hidden>
Date:02/15/2014 12:26 PM (GMT-06:00)
To: <email address hidden>
Subject: [Question #244049]: Location of settings

New question #244049 on KiCad:
https://answers.launchpad.net/kicad/+question/244049

Where are the custom field names stored for eeschema? I've googled and find the same question asked many, many, times, but never answered. Searching my entire computer fails to find them. I'm baffled!

With a flashlight?  Take the cover off?

Did you look on the  disk?  What about

~/.eschewa

If that's not it, then use the source Luke.

(You are on the developer's mailing list, where interaction with the source is the prime objective.)

Grep is your friend, your editor should have that.  Start by grepping for the window title of the dialog.  That's how I start to zero in, can't keep it all in the head.

Hopefully you can now catch your own fish now.

Again, grep is your friend.  And JEdit serves me well.  I think I had about 400 source files in ram all week, and jedit can grep thru ram or disk copies.  It's simply sensational for me.

--
You received this question notification because you are an answer
contact for KiCad.

Revision history for this message
Chris Gibson (chris-w-gibson) said :
#2

I'm on Windows. I found it eventually. It's in the registry!

Who decided that was a good idea? It makes duplication of installations on multiple machines an absolute nightmare. I'm confused why a straightforward file wasn't used. Either I've missed something or someone has a really odd sense of humour.

Revision history for this message
Lorenzo Marcantonio (l-marcantonio) said :
#3

On Sat, Feb 15, 2014 at 07:21:24PM -0000, Chris Gibson wrote:
> Who decided that was a good idea? It makes duplication of installations
> on multiple machines an absolute nightmare. I'm confused why a
> straightforward file wasn't used. Either I've missed something or
> someone has a really odd sense of humour.

Dick has a strange sense of humour but I don't think he's the culprit
except for the funny response :D

It's a long standing issue: on Linux these are files in the home (some
even without the leading dot, being ugly as hell), on Windows they are
in the registry. Why not in application data? no idea... probably there
is some kind of wx convention/suckitude doing that (like for lockfiles)

But don't worry, kicad is full of strange design decisions:D

--
Lorenzo Marcantonio
Logos Srl

Revision history for this message
Wayne Stambaugh (stambaughw) said :
#4

On 2/15/2014 2:36 PM, Lorenzo Marcantonio wrote:
> Question #244049 on KiCad changed:
> https://answers.launchpad.net/kicad/+question/244049
>
> Lorenzo Marcantonio posted a new comment:
> On Sat, Feb 15, 2014 at 07:21:24PM -0000, Chris Gibson wrote:
>> Who decided that was a good idea? It makes duplication of installations
>> on multiple machines an absolute nightmare. I'm confused why a
>> straightforward file wasn't used. Either I've missed something or
>> someone has a really odd sense of humour.
>
> Dick has a strange sense of humour but I don't think he's the culprit
> except for the funny response :D
>
> It's a long standing issue: on Linux these are files in the home (some
> even without the leading dot, being ugly as hell), on Windows they are
> in the registry. Why not in application data? no idea... probably there
> is some kind of wx convention/suckitude doing that (like for lockfiles)
>
> But don't worry, kicad is full of strange design decisions:D
>

This is legacy baggage in KiCad. On my personal todo list is to dump
wxConfig which is a macro that expands to wxRegConfig on Windows builds
and use wxFileConfig so that the settings on Windows are plain text
files just like Linux and OSX. Please do not hold your breath on this
one as you may turn a pretty shade of blue waiting for it. I will get
to it but probably not on your (or anyone else's for that matter) time
table.

Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#5

Sent from my Galaxy S®III

-------- Original message --------
From: Chris Gibson <email address hidden>
Date:02/15/2014 1:21 PM (GMT-06:00)
To: <email address hidden>
Subject: Re: [Question #244049]: Location of settings

Question #244049 on KiCad changed:
https://answers.launchpad.net/kicad/+question/244049

    Status: Answered => Solved

Chris Gibson confirmed that the question is solved:
I'm on Windows. I found it eventually. It's in the registry!

Who decided that was a good idea?

Microsoft.

 It makes duplication of installations
on multiple machines an absolute nightmare. I'm confused why a
straightforward file wasn't used. Either I've missed something or
someone has a really odd sense of humour.

Agreed.  When they introduced the registry is about the time I left the microsoft parade, but not for that reason.  It was the constant wrong turns, that led me to conclude I had to start thinking for myself.  That was 1996.  Way "back in the 1900's".

The wx developers followed all the rest of the lemmings when they made wxConfig use the registry.  It takes a 50,000 foot view to stray from Microsoft's view.  The fact that you are still using windows supports my point.

The new work being done in kicad is positioning us to move out of the registry.  At some point Wayne and JP can flip the switch in less than ten minutes if they want.  That is to the wx team's credit.

--
You received this question notification because you are an answer
contact for KiCad.