Repository navigation
[Context] Read the API context and the UI application from the Revit 2027 internals - #130
Merged
Merged
Conversation
Nice3point
marked this pull request as ready for review
October 15, 2026 20:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of the Pull Request
What is this about:
RevitContextreads the API context and the UI application from internal members of the Revit 2027 API.Description:
What changed
IsRevitInApiModecalls the internalApplication.IsInAPIContext()through anUnsafeAccessor.IsRevitInApiModecalls the nativeAPICallDepthManagerfunctions ofRevitDBAPIthrough function pointers. It no longer invokes them through reflection or loadsAPIUIAPI.UiApplicationis the sessionUIApplicationfrom the internalUIApplication.Instance. Earlier versions construct it fromApplication.Where to look
APIUIAPIandRevitDBAPIboth declareAPICallDepthManager.singletonfactoryandisRevitInAPIModeas P/Invoke into the same native functions, in Revit 2023 to 2027.UIApplication.InstancereturnsUIApplication::getInstance(). The public constructor resolves the same native object throughgetUIApplication(getMFCApp(...))and rejects a call while a DB application is active.DialogBoxShowinghandlers in a static map keyed by the native pointer, soBeginDialogSuppressionScopesubscribes and unsubscribes through any wrapper of the session.How verified
Release.R20,Release.R24,Release.R26,Release.R27, zero errors.IsRevitInApiModereturnsfalsefrom a thread pool thread, and on the Revit thread for work queued through the dispatcher outside the API context. The second test fails for an implementation that compares threads.IsRevitInApiModeimplementationApplication.IsInAPIContext()UiApplicationchange.Quality Checklist