Cách sửa lỗi dynamo core component could not be found năm 2024
This blog is Part 2/3 of a three part blog series covering the Dynamo Core 2.13 release: Please read Part 1/3 first. Show
TL:DR
Phew… a monster list! As usual, there is a whole bunch more so please do check out the release notes! So, what other cool stuff can I do with Dynamo 2.13?A modernized Package ExperienceWe have modernized both the Package Consumption, and the Package Authoring experiences, bringing their aesthetics up to our new standard and adding more clarity and information into both. We have also added in more granular control to the Package Management features, allowing you to control what loads, when and from where with much more regulation than before. AllTheBellsAndWhistlesPackage ConsumptionDownloading a package is now a quick-hit experience, surfacing at your fingertips all salient information, with a new extension that brings deeper package information, and authoring a dynamo package is visually restyled, has more information around the optional fields, and automatically now attributes license and author data. Let’s orient ourselves with the newly restyled and reimagined package use experience:
Restyled package consumption workflow Package AuthoringCreating a package is now a more comprehensive experience, enabling all the good things that it did before and a few new things. Beyond a funky restyle of the entire experience, that brings you more clarity, cleaner ways to interact and a more modern theme, you can now also add a directory of contents rather than only being able to manually add files and add accompanying markdown documentation for nodes inside your package. All the existing license fields now properly attribute defaults into the pkg.json file (The manifest file that ships with your package ChecksAndBalances), giving you and your package legal weight. Please note that Packages can still only be published from a host environment that contains authentication, such as Revit or Civil 3D.So, let’s explore the modernized package creation experience:
Package Creation workflow modernization Package ManagementWe have also expanded your ability to manage your packages, enabling more granular control of what is loaded, and when, and introducing package states that paint a clearer picture of what that package is up to via the Preferences Panel. Uninstall in Dynamo is complex. Package assemblies: files whose contents must be interpreted by a program, in our case Dynamo, can only be unloaded or deleted from your computer when Dynamo and any host (If Dynamo is in-process, such as Revit or Civil 3d) is closed, releasing them from memory. Until that point, they are “in use” inside of the Dynamo memory space… and Dynamo doesn’t want to let go. So we introduced package states that indicate what each particular package is up to, and hover help text indicates what those states mean, enabling you to have more granular control over your Dynamo experience. A particular package causing you trouble? Then simply unload it for your next session. Can’t see why nodes are not showing up in the Library? Then your package may be in an Error state. Dynamo will now help you resolve package conflicts, alerting you if there are conflicts loading packages from different locations: i.e. you have two different versions of the MeshToolkit package loading, one from a custom path and one from the default package location, and give you the option to install top level package even though it’s dependencies are the wrong version; while previously possible, technically, this was really hard to discover and users were most often blocked, so we also improved our messaging around this. Please note that this doesn’t guarantee a package will work, as Dynamo still needs correct dependencies to run a package. We also enabled toggles to en-masse disable loading of Built-In or Custom packages, enabling you to swiftly debug problematic packages, or turn off entire ways in which Dynamo will load them. Disabling the Custom Packages toggle will stop you from being able to download packages from the Package Manager, greying out the install button and providing a warning message how to resolve. This is a less heavy-handed way of managing packages, where in the past you would have had to get creative with Package Search Paths, or literally move your packages into a new location temporarily. Let’s jump into the additional package management features:
New package features to help you manage your package experience Introducing Interactive GuidesWe are incredibly excited to introduce Interactive Guides, a new approach to allowing you to explore aspects of Dynamo, interactively, and contextually inside the application. Knowledge is power and all that! We have two interactive guides to date, the Get Started guide; a succinct exploration of the Dynamo user interface and its components, and the Packages guide; A walkthrough of what Packages are and how to get them, walking you through step by step on how to install your first package. Note: Please have your Library open for this guide if you tend to close it as we have a known issue that prevents us from automatically opening it up for you. Working on it! These are the first two interactive guides we have implemented in product, with the intention to deliver more and cover all salient aspects of the Dynamo experience to empower you, our awesome user base, with all the knowledge you need to succeed. The guides are short by design, targeting ten or less dialogs to orient you, while providing links out to external resources for deeper reading, such as the Dynamo Primer. Let’s explore their general make-up together:
Dynamo Interactive Guides Expanding the information in Workspace ReferencesOn the back of the hugely popular first phase of the Workspace References extension, we have also beefed up what it can do by expanding the functionality of the Workspace References extension to include local definitions and external files. Not only do you get to see what Packages are missing from your workspace, but you can now see all other references that are required to run your graph. The second phase of the Workspace References extension is informational, showing to you what other things need to ship with your graph to have it work the same way you have it working, be in Revit content, images, Excel workbooks or local definitions. Local Definitions captures any dynamo specific files that are local to your machine; think local Custom Nodes or local Packages, and External Files are external documents, not Dynamo specific files, that are referenced inside your graph space: Such as text files, images or Excel documents. So let’s explore this extended functionality to see what’s fresh:
Workspace References Extension now expanded Other epic things in the Release…This blog is Part 2/3 of a three part blog series covering the Dynamo Core 2.13 release, focused on Lowering the Barrier to Entry, putting Information at your Fingertips and Honing the Rough Edges. Read Part 1/3 here and Part 3/3 here! Ok, more blogs are cool, but I want to explore Dynamo 2.13 now!Dynamo 2.13 will be made available in our host integrations at a future date and can be explored right now through the dynamobuilds.com website or the Github build page – available in the Sandbox version of Dynamo. |