UI Components seperations #72
AmeerMansour
started this conversation in
Ideas
Replies: 1 comment
-
|
In the previous patch (2027), I moved UI-dependent extensions to the Nice3point.Revit.Extensions.UI namespace, like here: https://github.com/Nice3point/RevitExtensions/blob/main/source/Nice3point.Revit.Extensions/ContextMenuExtensions.cs Check out the end of the changelog: https://github.com/Nice3point/RevitExtensions/releases/tag/2027.0.0 so you can safely use anything outside the UI namespace; in unit tests, where RevitAPIUI also doesn’t work, all non-UI extensions are available |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
i would recommend having new project of RevitUIExtensions so we can seperate extenstion of elements , documents and database elements from UI extesnions and that would be helpful for APS right ?
so i mean we shall remove
from current project and create new one for UI compnents .
Iknow that mean extra projcect to maintain but seperation is important
Beta Was this translation helpful? Give feedback.
All reactions