Quote:
|
Originally Posted by peewee
This may be the reason
"If you have a file named set.keys in your current directory, then SeqEd, LineUp, GelEnter, and GelAssemble only respond to the keys that you have defined in it; all other keys will be silent. In the SeqLab sequence editor, keys that are not defined in the set.keys file retain their normal definition" |
Thanks, but that's a totally different program you're looking at, it's part of a package from the National Institute of Health:
"The GCG Wisconsin Package is an integrated package of over 130 programs that allows you to manipulate and analyze nucleic acid and protein sequences. Scientists from all over the world have collaborated to develop and refine the Wisconsin Package, making it a flexible tool with which to analyze your sequence data."
The one Darkfin refers to is SetKeys for SH3, found here:
http://www.subsim.com/subsim_files/p...SetKey1_11.rar
It allows you to edit the Command_en.cfg in SH3 with a GUI interface, and apparently also works with Command.cfg in SH4.
My problem with the "broken keys" was because I copied the SH3 command_en.cfg file that had been modified to add keystrokes to commands only accessible thru icons, to SH4. There are some conflicts apparently.
SetKeys will allow me to edit the original Command.cfg from SH4 and add keystrokes to the commands I need - hopefully avoiding conflicts and "broken" keys.