
So, my implementation actually shows you that ID string. While trying to setup our shortcuts, I ran into a lot of redundant situations where the CommandID was actually the best piece of information. This file gives you access to 100% of the content available in the KS editor and even various things that this dialog is somewhat hiding from the user most notably the CommandID. When you export the current shortcuts, they produce a very basic XML file. My solution to this is a complete redo of the Revit Keyboard Shortcuts (KS Command) editor. If you’ve played this game, then you get the point… I could easily map all the AutoCAD comparable commands to Revit commands…. I was no longer making commands that start with “S” a minimum of 3 characters to avoid these conflicts. This was pretty much life altering because I was no longer playing an extreme game of chess using super odd character combinations to avoid these conflicts. Eventually I figured out that absolutely everything could be mapped to explicitly have that next obstruction and that forces Revit to consistently require a Space or Enter smash for the “go do stuff” initiation. Being an avid keyboard user, I find that quite intolerable, confusing and honestly I’d rather die than play a perpetual game of where’s waldo with Revit’s labyrinth of an interface. However, the “CC” command will fire immediately. When using the “C” command, you’ll have to hit Spacebar or Enter to execute it. For Example, if you wanted to use “C” for copy and “CC” for Create Similar, what you wind up with is inconsistent behavior. When trying to create a custom Revit shortcut configuration, you will very quickly run into what I call the “Traffic Jam” scenario.
#Delete keyboard shortcut on revit software
To me a software is just a tool and we are the skilled labor. I am a long time AutoCAD (ab)user and you might think that I can’t live without the command line, but that just isn’t the case.

If we can’t align those to some degree, then we would be dooming our staff to a perpetual warm up cycle trying to switch between them and that is ultimately the problem I needed to solve.

Which means, we have no choice but to use 2 wildly different software packages to go from Design and Coordination all the way to Fabrication.
#Delete keyboard shortcut on revit generator
The point I am making, is that we literally can’t get rid of AutoCAD until Revit gives us the ability to properly edit DWG content or the Plant3D PCF->DWG generator can create an editable Revit sheet instead of a DWG. For example, you could remake the SL1 command in less than 20 lines of code. The API is again very different from what I am used to, but fairly well equipped to let me fill in a few of the (major) outstanding gaps. These philosophical principals are quite hard to pair with Revit, mostly because it is such a large deviation from the way many design software’s interact with their users.įor us, we have been “waiting” for Revit to give us everything we need to do our jobs for many years and because of our desired dependency on generating 2D isometric fabrication drawings, I keep coming up with the same answer of: “its not ready yet” which is still true… However, they have been progressively bridging the gap and they are most of the way there thanks to the integration of the Fabrication Database. I fundamentally believe people should be enabled to work whatever way they can be the most productive and accurate. From my perspective, if you have skills, then you should be able to use them and the design software should be a nearly irrelevant factor on whether or not you can competently coordinate a project.


A pure-Revit guy would consider this blasphemy, but for an AutoCAD user, what I have done could be a real blessing.
