Hi,
I wonder if there's some how a way to export the Hotkeys I've assigned in Eagle to import them onto another maschine or to give away to other users?
ULP? If, then how?
Can't find them in any of the scr files in the program folder.
Any idea?
Hi,
I wonder if there's some how a way to export the Hotkeys I've assigned in Eagle to import them onto another maschine or to give away to other users?
ULP? If, then how?
Can't find them in any of the scr files in the program folder.
Any idea?
On 3/1/2013 9:56 AM, Charles Bigstone wrote:
Hi,
I wonder if there's some how a way to export the Hotkeys I've assigned in Eagle to import them onto another maschine or to give away to other users?
ULP? If, then how?
Can't find them in any of the scr files in the program folder.
Any idea?
--
To view any images and attachments in this post, visit:
http://www.element14.com/community/message/71020#71020/l/export-my-assigned-keys
Hi Charles,
I hope you're doing well. In this case I would set up all of the
assignments in the eagle.scr file(See the default eagle.scr file for an
example). Once you have everything setup in your eagle.scr file then you
can simply pass that file along to other users or machines.
They would replace their default eagle.scr file with the one you send them.
hth,
Jorge Garcia
Hi Jorge,
Thank's for the reply!
Eagle.scr....Well, that is to be but as for now all my assigned keys (and I have a couple) is trapped somewhere else inside Eagle or it's files.
Lazy as the human can get I hoped that there was a way to export them without the need copy them all by hand, a quite boring and timeconsuming task but when done I'll never assign keys directly in Eagle it self ever again (since there's seems no way to get hold of them easily).
A bit odd though, why don't the keys I assign from inside Eagle end up in that eagle.scr file in the first place?
Any other tip on this?
All the best!
Bigstone
On 3/6/2013 2:48 PM, Charles Bigstone wrote:
Hi Jorge,
Thank's for the reply!
Eagle.scr....Well, that is to be but as for now all my assigned keys (and I have a couple) is trapped somewhere else inside Eagle or it's files.
Lazy as the human can get I hoped that there was a way to export them without the need copy them all by hand, a quite boring and timeconsuming task but when done I'll never assign keys directly in Eagle it self ever again (since there's seems no way to get hold of them easily).
A bit odd though, why don't the keys I assign from inside Eagle end up in that eagle.scr file in the first place?
Hi Bigstone,
That's a very debated and long fought over topic, which I do not intend
to get into here. The hidden deep file you're asking about is the
eaglerc.usr file. It's a pain to find(especially in newer releases of
Windows) and I personally think working with the eagle.scr is simpler
and more robust.
With that said, I don't intend to start a flame war.
Best Regards,
Jorge Garcia
Jorge Garcia wrote:
............. The hidden deep file you're asking about is
the eaglerc.usr file. It's a pain to find(especially in newer
releases of Windows) and I personally think working with the
eagle.scr is simpler and more robust......................
eaglerc.usr needs expanding if it is to be used to recover the assigned keys
easily.
There are three sections within it containing assigned keys. The ones for
schematic and board are fine but the section for the library assigned keys
is not further broken down to Package, Symbol and Device and this causes an
issue. Eagle is currently shipping such that the package editor and the
symbol editor both use the ALT+P combination. One uses it for PIN and the
other for PAD . How can eagle.usr possibly reflect that, it can't, not both
at the same time. The one you can get at is the active editor or when a
'save all' / write was performed and eaglerc updated.
I have put some time into a ULP to export the key assignments. Board and
Schematic are fine and then it gets complicated as you must open each of the
Library editors, to get the assigns. Its a bit ugly as the assigns you
gather contain all the library assigns and you can't determine which editor
they specifically belong to. Importantly the ones pertaining to that editor
are included. Many are replicated across editors so they are fine. Others
call commands that wont work in that editor. The ULP has been abandoned for
now awaiting bad weather or a brain wave.
It would be nice if eaglerc had the LBR_assigns sections for Lbr Sym Pac
and Dev
Warren
--
Viewed / responded via the newsgroup at
news.cadsoft.de
Hi, I found an easy fix for this if using Windows.
ASSIGN SETTINGS ARE STORED IN:
C:\Users\Admin\AppData\Roaming\CadSoft\EAGLE
in eaglerc.usr.sav file
Just copy that file over in the same directory after doing a new install.
Note: this was using version 8.2.2 but I imagine will work in newer ones as well.
SSFD SSFD wrote:
Hi, I found an easy fix for this if using Windows.
ASSIGN SETTINGS ARE STORED IN:
C:\Users\Admin\AppData\Roaming\CadSoft\EAGLE
in eaglerc.usr.sav file
near miss,
try %appdata%\cadsoft\eagle\eaglerc.usr
everything that looks like: Brd.Key..., Sch.Key..., Lbr.Key...
represents a hotkey
--
Lorenz
SSFD SSFD wrote:
Hi, I found an easy fix for this if using Windows.
ASSIGN SETTINGS ARE STORED IN:
C:\Users\Admin\AppData\Roaming\CadSoft\EAGLE
in eaglerc.usr.sav file
near miss,
try %appdata%\cadsoft\eagle\eaglerc.usr
everything that looks like: Brd.Key..., Sch.Key..., Lbr.Key...
represents a hotkey
--
Lorenz
SSFD SSFD wrote:
Hi, I found an easy fix for this if using Windows.
ASSIGN SETTINGS ARE STORED IN:
C:\Users\Admin\AppData\Roaming\CadSoft\EAGLE
in eaglerc.usr.sav file
near miss,
try %appdata%\cadsoft\eagle\eaglerc.usr
everything that looks like: Brd.Key..., Sch.Key..., Lbr.Key...
represents a hotkey
--
Lorenz
Thanks looking for these for my project.