Skip to content

Mark nodes promoted to OOTB as obsolete - #111

Open
sharafutdinovdi wants to merge 1 commit into
johnpierson:masterfrom
sharafutdinovdi:chore/deprecate-ootb-nodes
Open

sharafutdinovdi wants to merge 1 commit into
johnpierson:masterfrom
sharafutdinovdi:chore/deprecate-ootb-nodes

Conversation

@sharafutdinovdi

Copy link
Copy Markdown

Follow-up to #24. Three of the remaining unticked items now exist as out-of-the-box nodes in Dynamo for Revit, so this marks the Rhythm versions obsolete following the existing pattern in the repo:

  • Sheets dropdown (RhythmUI) → OOTB Sheets (Revit > Selection), marked with [Obsolete] as in LinkSelectionMethods.cs
  • View Family Types dropdown (RhythmUI) → OOTB View Family Types (Revit > Selection), same pattern
  • View.Origin (RhythmRevit) → OOTB View.Origin property, marked with [IsObsolete("Node removed, use the OOTB nodes, View.Origin")] as in Tag.cs

Not touched: View.SetCropRegion is already commented out; Tag.SetLeaderElbow / Tag.SetLeaderEnd have no Rhythm implementation in the current source (the Leaders.* nodes operate on Leader objects, not tags), so those two items look like bookkeeping on the list rather than code changes. Details in the comment on #24.

Built RhythmRevit and RhythmUI locally with the Release R25 configuration (MSBuild, Visual Studio 2022): 0 errors.

Sheets and View Family Types dropdowns and View.Origin now exist as
out-of-the-box nodes in Dynamo for Revit, so mark the Rhythm versions
obsolete following the existing deprecation pattern. Remaining items
from the deprecation list are covered in johnpierson#24.
@sharafutdinovdi sharafutdinovdi mentioned this pull request Sep 8, 2026
24 of 30 tasks

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant