-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected relative path - document.importimage #244
Comments
The only thing I know will give an error is, that if you don't have the needed credentials in a folder, then will the node for sure fail. So I presume that "static12" is your username and not someone else's username and/or there is some ”reading” restrictions on that folder. My nodes and functions in general do respect credentials set in the overall operating system. |
It is a well-known issue that ACC-driven files don't support relative paths, and paths need to have the characteristics that files have web addresses, as I remember it. PS. why do you use "copyright Waithfor" node? I have a node named "Await" for that. In general, you should not need any other packages, since Orchid is the largest and most comprehensive package... unless it is very special cases!? |
First, please skip the slang term "script" since that is not what we are working with... Next, I can take an ACC license from our pool, but only while no one else is using the licenses. These licenses are quite expensive, so we don't have an ACC license for everyone. We haven't seen any reason for me to start coding for ACC either, but we have started talking about it. This means that within the next year, I will be doing something with ACC-driven nodes. I do know that the major issue is the web-based paths, and that is what I will solve first, when I start doing nodes for ACC. |
Revit: 2022.1
Dynamo: 2.12
I'm trying to import images to the image manager in Revit with dynamo. I use the node Document.ImportImage. I get an error : unexpected relative path or bad .
what I'm doing wrong?
Thanks in advance
The text was updated successfully, but these errors were encountered: