Create Project Parameter from Shared Parameter

[m.rijsmus]

Hi @erfajo

I ran this on a new project started by choosing none when it ask me for the project-template.
Can you explain?

[erfajo]

i am not aware what Autodesk has put in their “empty” project template!?

I got these… doing the same

if you want to use my nodes in the current document, then you don’t need to add the document, since I have coded this as the default value if the port is unassigned.

likewise can the ootb node for element.name do the job for getting the name

[Marcel_Rijsmus]

I use Element.Name+ beacause someone made it to use a bigger scope getting names. so my initial thought was why not use the bigger scope.
Maybe @JacobSmall can shed some light on what these parameters are/do, cleaning up my models i need to know what can be deleted
can’t seem to find them in here. further exploring needed, im on it, want to know @Luke_Johnson, @Jeremy_Tammik
btw @erfajo deleting a parameter by name is ok, but deleting a parameter by GUID is better i think, it will force you to know exactly what you are doing

PUBLIC: Revit Category Guide

[erfajo]

Delete by guid… I will try to see what I can do asap

However, I am struggling these days with the growth of my package. It holds now more than 150 nodes and I need to see if they can be organized better. Moving methods around comes with the backside of a need for migration, so users don’t end up with graphs not working. Therefore, have I started doing a UML diagram to gain an overview

[Marcel_Rijsmus]

You help a lot of people out in difficult situations.
I like it

[erfajo]

I have released the beta build nodes…

Orchid package --> released at Github

Orchid version 134.3.10 / 202.3.10 has been released. The largest change in this version is that the package has been refactored to comply with naming conventions. The next largest change is all FamilyDocument nodes don’t pass the document as an output, likewise, other nodes there passed project documents. I have made this rather large change to be able to support ”ListLevel” better, I have noticed many users have problems understanding that the output changes dramatically for passing the open…

[Marcel_Rijsmus]

@erfajo
I just had this thought:
What if i could make those “loose” shared parameters into Shared Project Parameters with the categories still attached (no data loss). I can them delete them and investigate further if needed. But now i have control from the UI.

[erfajo]

I don’t know what happens if you dig something up from the graveyard, I could give it a try asap…

Right now am I once more troubling with the closed Dynamo API, you need to build some many features over and over again due to protection by the Dynamo team.
I need to solve this one first and it is driving me crazy