You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a metanode that does this. But it is hard to access the databases shipped with our plugin across different machines and plugin names.
A separate node that reads all the databases at runtime and shows the user a javascript interactive table with possible selections would be nice (also would have access to the shipped dbs). Maybe directly export it to a variable that can be used in our nodes.
Would unify the usage of mods across a workflow and solves the runtime display of modifications in our nodes. Is only portable in the sense that you can save the output of that node in the executed workflow. If another user does not have the same unimod, it will complain at runtime of the tool. If he resets the nodes, this selection will not be displayed anymore.
The text was updated successfully, but these errors were encountered:
I have a metanode that does this. But it is hard to access the databases shipped with our plugin across different machines and plugin names.
A separate node that reads all the databases at runtime and shows the user a javascript interactive table with possible selections would be nice (also would have access to the shipped dbs). Maybe directly export it to a variable that can be used in our nodes.
Would unify the usage of mods across a workflow and solves the runtime display of modifications in our nodes. Is only portable in the sense that you can save the output of that node in the executed workflow. If another user does not have the same unimod, it will complain at runtime of the tool. If he resets the nodes, this selection will not be displayed anymore.
The text was updated successfully, but these errors were encountered: