I HATE the current "user directories" functionality...

I HATE the current "user directories" functionality...

johnwYMVVZ
Advocate Advocate
327 Views
5 Replies
Message 1 of 6

I HATE the current "user directories" functionality...

johnwYMVVZ
Advocate
Advocate

Yeah, strongly worded.  Sorry if I offended you.

 

I do not want to work the way Autodesk is forcing me to.  I do not want separate library files on every machine I work on.  I am a single developer and work on multiple machines, using dropbox to mimic a network share.  Think work, home and laptop (on the road).  Forcing my user folders to the local PC is really annoying, even more so when I try saving a design block or library, deliberately navigating manually on every freaking save, to the folder where I want to save the file, and Eagle saves it to the local documents folder anyway!!!

 

PLEASE change this incredibly annoying, overbearing,  domineering, dominating, autocratic, tyrannical, despotic, high/heavy-handed, oppressive, bullying, high and mighty, lordly, officious, masterful, dictatorial, bossy, imperious, pontifical, pompous, peremptory, arrogant, cocksure, proud, overproud, overweening, presumptuous, opinionated  and/or dogmatic behavior by allowing ME to set a document root for the $HOME variable.  Feel free to default it to the local documents folder when the software is installed because you feel it's the best option!  But allow me to change it.

 

Thanks for your consideration!

0 Likes
328 Views
5 Replies
Replies (5)
Message 2 of 6

rachaelATWH4
Mentor
Mentor

@johnwYMVVZ wrote:

 

I do not want to work the way Autodesk is forcing me to. 

 

Then don't. Smiley LOL

 


@johnwYMVVZ wrote:

 

PLEASE change this incredibly annoying, overbearing,  domineering, dominating, autocratic, tyrannical, despotic, high/heavy-handed, oppressive, bullying, high and mighty, lordly, officious, masterful, dictatorial, bossy, imperious, pontifical, pompous, peremptory, arrogant, cocksure, proud, overproud, overweening, presumptuous, opinionated  and/or dogmatic behavior by allowing ME to set a document root for the $HOME variable.  Feel free to default it to the local documents folder when the software is installed because you feel it's the best option!  But allow me to change it.

 

You can completely customise the directory setup. I personally have it set up so all my machines point to locations on iCloud. The reason Autodesk changed it in v9 to create a deliberate separation between the installed EAGLE root location and the user location is because too many people were just using the install folders as work folders and complaining every time a new version came out. But it's always been completely configurable. You can do now what you were always able to do, it's just good practices are set by example.

 

In summary, if you don't like it, in the EAGLE control panel go to Options->Directories and change to to how it suits you.

 

Best Regards,

 

Rachael

Message 3 of 6

johnwYMVVZ
Advocate
Advocate

It does not work reliably.  And it would be best if, on the directories panel, the first option was to set a $HOME root folder, then use $HOME/Design Blocks, $HOME/Libraries, etc.  One change instead of 8

0 Likes
Message 4 of 6

rachaelATWH4
Mentor
Mentor

@johnwYMVVZ wrote:

It does not work reliably. 


 

I've been using EAGLE for years with custom directory setups on numerous different machines. It works exactly as it should for me. Can you elaborate on where it isn't working reliably?

 


@johnwYMVVZ wrote:

 

And it would be best if, on the directories panel, the first option was to set a $HOME root folder, then use $HOME/Design Blocks, $HOME/Libraries, etc.  One change instead of 8


 

Press F1 to open the help and type HOME into the search. In there it will tell you how to specify the home location on your machine. You basically need to set the EAGLE_HOME environment variable. I will admit, it might be nice if there was a convenient UI widget to set it, but the functionality is there and quite easy to find and configure.

0 Likes
Message 5 of 6

tinkercadXSL49
Enthusiast
Enthusiast

To act as devils advocate here, personally I love the clear separation between application and user directories.

 

I have also used Eagle for years, and also work on multiple machines, and the solution I use is to set up a (free) github account, and sync my libraries via a (free, private) github repository - the benefit being that I then have full revision control over them. Even if I *were* to fiddle with the directories as  Rachael mentions, I'd still set it up this way. 

 

git add, git commit, git push are not hard to use - especially when it's just you doing it and there's no merge-conflicts and branching trees.

Message 6 of 6

one-of-the-robs
Advisor
Advisor

@tinkercadXSL49 wrote:

I have also used Eagle for years, and also work on multiple machines, and the solution I use is to set up a (free) github account, and sync my libraries via a (free, private) github repository


Ditto. Well, s/git/subversion/ and with a local server rather than cloud, but that's just detail.

0 Likes