Jose Guia has also responded to the challenge. Here is a direct link to the program he created:

EDIT: Jose’s blog seems to be down, here is a link that works

He has done a nice job – his program is a little bit more advanced than Rod Howarth’s version. He includes a few more statistics, and the folders are already setup for RAC.  It also links into the Revit Forum thread.

This is a scary stat from my analysis:
Total times you used the ESCAPE KEY          : 8520  (387 presses on average per session)

Here is his blog post: | Revit Journal Analysis and Parsing Program (Rank Keyboard Shortcut Use)

Here is the Revit Forum post.  You can put your results here.
Revit Journal Analysis and Parsing Program (Keyboard Shortcut Use)

Give it a go.

Revit does not want you to place a slab edge on part of a slab that is sloping (because it has been shape-edited).

However, you can ‘trick’ Revit into letting this happen by:

  1. Setting the edge you want the Slab Edge to go on to be ‘flat’ by temporarily point editing the slab.
  2. Then place the Slab Edge (Revit will allow you to, now that the edge is flat).
  3. Adjust the points back to how you want them.

The Slab Edge should happily follow the sloping edge now.

A bit of a workaround, but it does work…

Rod Howarth has done a great job in responding to the challenge I presented a fortnight ago.  He has created a simple yet effective program that analyzes your journal files and tells you the Top 20 commands that you are triggering WITH Keyboard Shortcuts, and the Top 20 commands you are triggering WITHOUT Keyboard Shortcuts.

Most of us realize that the fastest way to trigger a command is by using the keyboard.  Yes, the Ribbon is lovely in its own way, but once you know what command you want, why would you want to spend 3 or 4 clicks getting there, when a simple press or two on the keyboard will do the same thing?

Here is a link to the Journal File Analyzer post by Rod.

Here is a direct link to the Journal File Analyzer program.

I will post later about the paths to use if you don’t know them already.

Also, don’t include “” marks in the path entries.