Advertisement

Sunday, November 15, 2026

Orkestra (OkPy) Version 2.7 Review: New Events and Panels (with Examples)!

Recently, Orkestra released version 2.7, introducing events and panels to OkPy. As you'll see, this is a hugely significant development.

Events are add-ins that run all the time, and respond to specific events. I first tried to create a listener for a keyboard shortcut, ZM for Zoom Multiple, which would first fit the view and then zoom region in a loop. I had already implemented this with OkPy, but it requires that a dialog box first be opened and that it remain open, though it can be minimized.


Unfortunately, OkPy informed me that its events cannot listen for keyboard shortcuts, so I would have to keep my previous implementation.

OkPy actually recommended my next event add-in, a tool that would automatically fit views when opened or activated. The prompt was simple: Create an event application that automatically fits views upon activation.

One change to OkPy in version 2.7 is an obvious one, it first asks if you want to create add-ins with C# or Python. Previously, it just worked with Python, hence the name OkPy. The application now recommends C# for a few reasons. One is that C# makes native API calls, so it should be marginally faster (though I've been very satisfied with how responsive my OkPy Python add-ins have been). More significantly, OkPy informs you that you must use C# for events and panels. 


Another noticeable change is that OkPy now surfaces the code as the OkPy Agent is running, at least when using the C# option. 


My event add-in worked as designed out of the chute. 

There's a new Events button in the Orkestra ribbon. From here, you can enable or disable event add-ins. When enabled, they start automatically when Revit is launched—set it and forget it.



Next, I looked at creating a panel application. Panels are resizable, dockable, and persistent. Examples of panels are the native Project Browser and Properties windows.

I had an idea from years ago—seven years to be exact. You see, back then I was working for the add-in developer StrucSoft, and I shared this idea with them. Unfortunately, I left the company not longer after, and they never implemented it.

My big idea was for a Recents panel, where the most recently used commands would live. I know Revit has this natively on the right-click menu, but, having once had a repetitive strain injury (not quite as severe as carpal tunnel syndrome), I avoid the right-click menu like the plague. And a panel implementation would be better; it would be heads-up, you could have more recents, and you could have icons too. Because I envisioned it as a panel, there would be a lot of room for other recents too, like components and wall, floor, and ceiling types.

I would name this panel Recall (as an homage to the Arnold Schwarzenegger movie Total Recall).

Unlike other add-ins I've created with OkPy, Recall couldn't be distilled to a handful of prompts, and, because I would implement and test each category of recents individually, it would take hours instead of minutes to create. But it would totally be worth it.

My first prompt was simple, Create a new panel project named "Recall". 

Fortuitously, the OkPy Agent then asked me what I wanted to recall, and the first suggestion was recent views. I thought that could be interesting, so I added it to my list of things to implement. More on that later.

I incorporated recent commands first. OkPy assigned four icons by default, one for regular button clicks, a different one for add-in button clicks, another for keyboard shortcuts, and, lastly, one for Quick Access Toolbar button clicks (which I almost never use). While this was helpful, I wanted the native command icons. Unfortunately, OkPy informed me that a panel cannot query the ribbon, even in read only mode (the recent commands in the panel are actually compiled from a journal file).

I messed around with the size of the recent command tiles, and the number of recent commands before finally settling on twelve.


Next I tackled recent views. A single prompt added a pretty good implementation to Recall. OkPy again assigned unique icons to the different view types, and also appended the view type as text. At first, I thought this would only be useful as a quicker way to activate an already open view. However, Recall remembers that last six opened in a project, including between sessions! If you work with a handful of views in Revit models, this is a huge timesaver for opening those views.


Next came components. Again, a single prompt added a pretty good implementation. I added the thumbnail previews with a subsequent prompt, and they look great. Next, I pre-populated the list of recent categories from the active file, showing the most used in order with counts. Then, as components that aren't in the list are placed, they're added to the list as the most recent component, and the oldest one is dropped off. As with views, Recall remembers these recents between sessions for each project.


Last came types. I spent the most amount of time on this category, especially trying to get the number and size of the tiles right. Ultimately, I went with a smallish size and allowed OkPy to increase the size in order to wrap long type names. Fortunately, at my employer Woolpert, our standard type names are mostly short ones. I tried to implement thumbnails on types as I did for components, but they weren't as useful as the different icons OkPy already suggested for wall, floor and ceiling types, so I ultimately went with them.


Here's the final product. When you click on something, Recall of course initiates the correct command, such as Door for placing doors or Component for placing furniture. I may be biased, but I think Recall is a gamechanger, totally worth the $100/month Orkestra subscription to distribute it.


An important note: for events and panels to work, Orkestra V2.7 must be installed on all downstream systems.

Grade: A+. Orkestra is absolutely killing it!

Want Recall? Well, you'll have to build it yourself. I've reached out to Orkestra CEO Mostafa El Ayoubi about creating an OkPy clearinghouse for paid OkPy users, and he thinks that's a great idea. Hopefully we'll see that implemented in the future so we can share our OkPy creations with the community!

Related:



Advertisement

No comments: