Tools/Customize/Keyboard

SW2005 SP0.0

It appears that there is a bug in that once you assign a hotkey to a command, you can't undo it. It lets you go through the procedure, and they disappear right in front of your eyes, but then when you restart SW, they are back. Even if you reassign one, it keeps remembering them, and all are still active. Someone please confirm before I send it in.

WT

Reply to
Wayne Tiffany
Loading thread data ...

I got a confirmation of this from SW - hopefully fixed in SP1.0.

WT

Reply to
Wayne Tiffany

"Wayne Tiffany" wrote in news: snipped-for-privacy@uni-berlin.de:

Yeah, lets hope. I lost my "B" hotkey. Now I have to use ctrl+B for rebuilds. Life is so hard.

Good hunting. Thanks for tracking it down.

Reply to
Dale Dunn

One way I found to undo hotkeys is to blow away the SW2005 key for CU. Then the next time you start SW it will rebuild it from the LM key. However, you also lose any other changes you made.

WT

Reply to
Wayne Tiffany

"Wayne Tiffany" wrote in news: snipped-for-privacy@uni-berlin.de:

That's the problem. If only I could make sense of those keys. I see that the data in the key entry corresponds to hex ASCII character codes, but I don't immediately see whay controls the rest of the key chord.

For example, in HKEY_CURRENT_USER/Software/SolidWorks/SolidWorks

2005/Customization/tplate0/Custom Accelerators/AddArray/11_76 is see several entries:

cmd 36408 fVirt 11 key 76 name 1_less_place:Module1_less_place

This is the accelerator for a macro called "1 less place". The value 76 (I've shown decimal values) is ASCII code for "L". I'm guessing the fVirt

11 means "ctrl". This adds up to my accelerator key assigned to this macro, ctrl-L.

In another folder (11_72) I find:

cmd 34103 fVirt 11 key 72

This would add up to ctrl-H which is my accelerator for HLR display.

It seems obvious that the cmd values are the command in SW that the accelerator keys are bound to. Now then, does anyone know of a reference explaining these, or do we have to reverse engineer them?

fVirt 7 seems to be shift fVirt 27 seems to be ctrl+alt fVirt 15 seems to be ctrl+shift

With some experimentation binding other chords to macros (since they are labeled in the registry), I'm sure we could figure out the rest.

Reply to
Dale Dunn

Kind of interesting in that I copied out my settings before & after adding all the hotkeys, and then compared the files. Macro hotkeys are recorded differently than the others. I still don't understand why the hotkeys are recorded in 3 different keys. Intriguing, but not sure it's worth spending the time on it.

WT

Reply to
Wayne Tiffany

I still don't understand why this is not a table somewere anywhere that a human can read and edit. I'm absolutely tired of having to monkey with this stuff each time there is a major release. Absolutely tired of it. Does anyone know what my alt-f key is mapped too? Please e-mail me with the results, because the person who programmed the hotkey system only had enough time to tell me that the key is already mapped and did not bother to tell me to which function. Ok - they gave me a hint - it's a pop-up dialogue called "find & replace detailing text", but does that actually map to one of the cute functions names in the custom list, you know, the one where you can only use the "hot touch" key to reach the first level of the heirarchy, but none of the sub functions (i.e. hitting "s" takes you to the Sketch heirarchy, but will not "penetrate" down a level to "split"). Do the people who program this stuff know how important hotkeys and their easy management are to the end user?

BOOO - We all deserve something better than this. I'm tired of the stupid management of the hotkeys and the needless hiding of the currently mapped data and the (new) registry abstractions and the inability to just so "Ok Thanks for telling me that this is already mapped, could you just please un-map this hot key and simply assign it to what I just asked you to assign it to without sending me on a likely fruitless life-quest for the hidden mapping like I was frodo looking for the lost ring or someone in search of a new tomb in the valley of the kings or deciphering a lost aramaic script . . .l

SIMPLE NEED:

-ONE LIST THAT I CAN READ

-ONE LIST THAT I CAN EDIT

COMPILED OR INTERPRETED, I DON'T CARE - JUST DONT LOCK ME OUT OF THE HOUSE ANYMORE YOU CRAZY KIDS . . .

SMA

Reply to
Sean-Michael Adams

alt-f= fix all parts in an assembly.

See Wayne's post from last week- he made a master lest, but I don't know how or where it came from.

Reply to
jk

Actually, there is a bit of confusion here. The issue at hand was the fact that SMA was lamenting over the fact that his alt-F is already mapped and the system would not tell him where. You were correct in pointing out that my list shows alt-F mapped to the macro of Fix all parts. But that would only apply to him if he either loaded my hotkeys, or set that one himself, and I would think he would have remembered either instance.

So, my conclusion is that he was, instead, referring to ctrl-F, which the system does say is in use, but doesn't say where, as is its normal method. So this is obviously a bug, and is acknowledged by SW as such, and was assigned SPR 212054. SW2004 also had this problem.

Now, I see that ctrl-F does actually do something - it opens a box called Find and Replace Detailing Text that allows you to search through notes for specified text & optionally replace it. To read about it, go to Help: notes, find and replace text. This was not a feature in SW2004, and the issue still exists in that the system says the key combination is in use, but doesn't list that command, or even tell you what it is.

The list of mine is something I started back about the SW2000 days out of frustration. I wanted to know what all was available for hotkeys and nobody had any kind of complete list. So, I sat down with a clean installation and stepped through all the commands & menus and wrote them all down. And I have kept it up and done it for every version since. Every once in a while someone will feed me one that I either missed, or is undocumented, but works.

Previous to SW2005, the hotkeys were stored in a separate file on your hard drive in your SW installation folder in a folder called User. This file had the name of your login with the extension .CUS. To give someone your hotkeys, they just had to put the file there, rename it to their login, and SW would pick it up. Not bad, but the CopyOptionsWizard would not pick it up. The file was also not readable ASCII text. Why not? I don't know, I didn't code it. Anyway, with 2005, the hotkeys are stored in the registry and the CopyOptionsWizard has been rewritten to allow you to copy them with the other settings, by themselves, or not at all. If you haven't tried the Wizard, take a look. By the way, 2005 will also recognize the .CUS file, so that's still an option if sometimes you don't want the hotkeys active, or maybe want a different set active.

WT

Reply to
Wayne Tiffany

Indeed, I am grateful that my cynically crafted rhetorical ramblings were not taken too seriously by anyone, including me.

Here we go - maybe SW corp should pay you $1000 to consult with them to point out all the liabilities of this keymapping funtionality and get it fixed. It's a bummer, but I don't know who's ticking their ear on what is needed (new & fixup). Getting things like this squared away would make SW so much better in a real way.

:)

SMA

Reply to
Sean-Michael Adams

Amen to that I here ya talking, and I'll second that motion

Reply to
Neville Williams

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.