Here is a pretty cool example by Ken Goulding of using the Idling event to work around a little gap in the current Revit API. Ken posted a comment which triggered a pretty interesting conversation and culminated in the SelectionWatcher sample.
Another interesting item that cropped up was the possibility to use PasteBin to share snippets of source code, as Ken did for parts of his initial implementation:
The code listed there is now obsolete, though.
Here are some excerpts from our conversation that led up to this sample:
Ken: When you mentioned "Element Level", I was hoping that included element selection events, but that does not seem to be the case. As a work-around, I created a class that subscribes to the application Idling event and checks for selection changes. Given that the Idling event is called very frequently, I tried to be as efficient as possible at figuring out whether a change has happened, but there may be a simpler way?
Jeremy: Thank you for your query with the interesting idea and the source code. Thank you also for the interesting PasteBin URLs. I was not previously aware of this possibility.
Regarding the element selection events, you are correct in your assessment that these are currently not provided by the Revit API.
Your use of the Idling event to implement a work-around sounds like a brilliant idea to me.
Ken: I'm glad you see potential for the selection watcher class. I was using it to link additional data (e.g. photographs) to room objects, but I'm sure your readers can find far more interesting uses for context-sensitive functionality. I added a few comments inline. Please let me know if anything is not clear,
Jeremy: Thank you very much for the illuminating sample. I like it very much! I fixed two details which simplify things:
Ken: Thanks for the suggestions. It is good to know that you don't need to copy the Revit API DLLs locally, since they are big.
Jeremy: Here are some screen snapshots from an example run testing this. The selection watcher is an external application and defines its own ribbon panel. Here it is ripped off the ribbon bar and placed over the graphics area, so that it remains visible through a ribbon context switch:
Here we have selected Room 5, which is displayed immediately by the selection watcher:
In this simple implementation, selection of multiple rooms is simply listed as such with no further details:
For further details including some comments, please look at the source code in the archive file SelectionWatcher.zip. It includes the full source code, complete Visual Studio solution and an add-in manifest file to load the application.
Here are a few implementation details to whet your appetite:
This allows the following minimalistic implementation of the external application class, which just needs to set up its ribbon panel and text box to display the results, instantiate and subscribe to the selection watcher, and update the text box when changes occur:
[Transaction( TransactionMode.Manual )] [Regeneration( RegenerationOption.Manual )] [Journaling( JournalingMode.NoCommandData )] public class SelectionChangedExampleApp : IExternalApplication { private SelectionChangedWatcher _selectionChangedWatcher; private TextBox _tb; public Result OnShutdown( UIControlledApplication a ) { return Result.Succeeded; } public Result OnStartup( UIControlledApplication a ) { _selectionChangedWatcher = new SelectionChangedWatcher( a ); _selectionChangedWatcher.SelectionChanged += new EventHandler( OnSelectionChanged ); // it does not seem to be possible to add items // to context-sensitive ribbon panels. // however the user can detach this panel from // the main ribbon so that it is not hidden by // context-sensitive panels. RibbonPanel rpSelectionWatcher = a.CreateRibbonPanel( "Selection Watcher" ); var t1 = new TextBoxData( "txtInfo" ); _tb = rpSelectionWatcher.AddItem( t1 ) as TextBox; return Result.Succeeded; } void OnSelectionChanged( object sender, EventArgs e ) { if( null == _selectionChangedWatcher.Selection ) { ShowInfo( "No selection" ); return; } // this example just reports the name of the // room that is selected. Obviously any other // kind of element can be handled instead. List<Room> rooms = new List<Room>( _selectionChangedWatcher.Selection.OfType<Room>() ); if( 0 == rooms.Count ) { ShowInfo( "No rooms selected" ); } else if( 1 == rooms.Count ) { ShowInfo( "Room " + rooms[0].Number ); } else { ShowInfo( "Multiple rooms selected" ); } } private void ShowInfo( string p ) { _tb.PromptText = p; } }
The SelectionChangedExample class is more interesting, of course.
Here it is in all its glory:
public class SelectionChangedWatcher { public event EventHandler SelectionChanged; /// <summary> /// Auto-implemented property storing a list /// of all currently selected elements. /// </summary> public List<Element> Selection { get; set; } private List<int> _lastSelIds; public SelectionChangedWatcher( UIControlledApplication a ) { a.Idling += new EventHandler<IdlingEventArgs>( OnIdling ); } void OnIdling( object sender, IdlingEventArgs e ) { // Idling events happen when the application has // nothing else to do, // They can happen very frequently and the user // will experience a lag if this code takes a // significant amount of time to execute. Application app = sender as Application; UIApplication uiApplication = new UIApplication( app ); SelElementSet selected = uiApplication .ActiveUIDocument.Selection.Elements; if( 0 == selected.Size ) { if( null != Selection && 0 < Selection.Count ) { // if something was selected previously, and // now the selection is empty, report change HandleSelectionChange( selected ); } } else // elements are selected { if( null == Selection ) { // previous selection was null, report change HandleSelectionChange( selected ); } else { if( Selection.Count != selected.Size ) { // size has changed, no need to check // selection IDs, report the change HandleSelectionChange( selected ); } else { // count is the same... // compare IDs to see if selection has changed if( SelectionHasChanged( selected ) ) { HandleSelectionChange( selected ); } } } } } private bool SelectionHasChanged( SelElementSet selected ) { // we have already determined that the size of // "selected" is the same as the last selection... int i = 0; foreach( Element e in selected ) { if( _lastSelIds[i] != e.Id.IntegerValue ) { return true; } ++i; } return false; } private void HandleSelectionChange( SelElementSet selected ) { // store the current list of elements in the // Selection property and populate _lastSelIds // with the current selection's ids Selection = new List<Element>(); _lastSelIds = new List<int>(); foreach( Element e in selected ) { Selection.Add( e ); _lastSelIds.Add( e.Id.IntegerValue ); } Call_SelectionChanged(); } private void Call_SelectionChanged() { if( SelectionChanged != null ) { SelectionChanged( this, new EventArgs() ); } } }
Very many thanks to Ken for this idea and implementation and the fruitful discussion!