6 posts were split to a new topic: Thoughts about template files/ parts
Really enjoy the thoughts and examples everyone has placed. I still haven’t seen one of my “favorites” come up.
The GetParameterValueByName, SetParameterValue and just Parameters always throw me off. Searching for these is a wild ride, and seem to always happen when doing a live demo, which really boosts your confidence. I know it reiterates many other comments, but to me, these are among the most important nodes, and having to be exact to have them appear is the worst.
Get and Set Parameter are two sides of the same coin, yet there names are off just enough to cause confusion. It would be nice if they all just came up with the word parameter, which yields results related to curves, not elements. It would also be nice to allow for pluralization of words as most of the time you are setting or getting multiple parameters.
Appreciate you taking the time to ask us!
Happen to be looking for some
Curve.Trim nodes today…
curve trim, and
curvetrim don’t return any of the
Trim nodes. Only
curve.trim return anything useful.
Have you search for a coordinate system node lately? There is a 99% chance you won’t find what you’re after by typing; I just tell people to go to expand the shelf in the library and put in nodes manually. Meanwhile the designscript search for the same is an order of magnitude faster…
A post was split to a new topic: Node components
I always have the same issue with finding the select elements button. if you type select it doesn’t come up. element select also doesn’t produce the result. I’m often trying to remember it and have to go to old scripts.
I’ve had similar search issues with getparametervaluebyname, element type, all elements of (type or category) anything by clockwork, archi-lab, or Rhythm nodes. search string only works half the time, oscillating between two options.
Then there’s the weird searches that work. Object will bring up string from object, but string will not. boo gives me filterbybooleanmask, but filter doesn’t. I can search current to get to the active view in current document, but not active or view.
Hopefully some of those help the cause.
Warning suggests “Convert Units” but no node exists and the search returns nothing.
“Convert By Units” will return its respective node but not
“ConvertByUnits” will return its respective node but not
Convert By Units.
What you need to do FIRST is to standardize Node NAMING.
Second, the search would cover node names AND node descriptions (or make the latter optional with “expanded search”)
First at all is, I think team need to define again node name standard, may node with standard is having space, many name nodes are standard with no space between word.
Select Model Element => It should be can follow standard
And then when user search, easy to consider search because at the moment :
Select Model Element=> have result
And then with create a new package, also have standard is recommended developer is following with name standard, it will be help first, and then can think for another algorithm to optimize search.
A huge thank you to everyone who has passed in failing cases here, we are happy to report that with initial work we have solved all of the Dynamo core failures by implementing Lucene and indexing heavily into… search indexing
Apache Lucene is a high-performance, full-featured text search engine library written in Java.
A handful of such successes show below with implementation in the right-click only search and failures currently in the Library search. Ongoing work will unify both and improve across the board
String from Object
Coordinate System Origin
Sneak peek of also seeing a mock-up of ability to search for Documentation in this search also (Such as Extended Node Help and Sample Files), referenced by the jarring icons
What would also be very helpful is the possibility to limit the search to nodes with a specific input type and/or output type. (I don’t think this is possible yet, correct me if I’m wrong).
Could be solved via checkboxes or additional input fields. Or by simply typing it into the search bar with “input:xyz” and “output:abc” in addition to the search word.
“element output:string” will only return nodes that have “element” in the name or description AND have at least one output of type “string” / “strings”.
This should list nodes like “element.name” for example.
“Input:Double” should list every node with at least one number (double) as input.
And so on…
These are the basics. Of course you could extend this with the many possible input and output types, including those of custom packages perhaps.
E.g. a search for “input:parameter” would only show nodes that have at least one input of type “parameter”. In this case all types of parameter (e.g. also “FamilyParameter”). Of course you could also specify it in the search e.g. enter exactly “Revit.Elements.Parameter” where then also only these types are shown and no others.
I hope this is somehow possible to implement.
Thanks for the work so far.
Element Classes I believe.
Ha thanks, good to know
Hello everyone - The blog post will be out immanently, but suffice it to say that Dynamo Search has been dramatically upgraded in Dynamo 2.19
Sneak peek of functionality:
- It simply works much better
- Spaces or periods don’t matter anymore
- Typo support
- In all instances of Search (Library, in-canvas, Package Manager, Graph Node Manager etc.)
- Hierarchy preferences correct match, name and category above description and lower-tier elements
After Revit 2019 the dynamo version with search is bad, i don’t find nodes anymore.
I am expecting to find any node that contains any word or part of words in the dynamo library: node name, node description, node inputs.
Could be good to search as well in the nodes used in the script but doesn’t matter if working only with python code.
Would be good to be able to search words in python node code as well
Have you tried search inDynamo Core 2.19?
Can we use that dynamo version on revit 2019 to 2022?
Not in a supported way. Nor should you be using 1/2 of the versions listed as they are not supported. Utilization of 2019 and 2020 is a security risk.