In Grasshopper, since the projectId is set by canvas node/compute method, it is possible that other canvas nodes/methods would compute before the projectID method creates the projectIDEvent. Users are reporting that they still get the popup even though the setprojectID canvas node/method was set in previous sessions.
Revit/Excel retrieve the projectId value from queryable internal data fields and do not require a compute of a projectIDEvent to set the projectId, so I do not expect this to be an issue in these toolkits.
We've not yet set up any method of pre-setting the projectId in Dynamo, but were we to do so, I would expect this to occur in Dynamo as well.
Steps to reproduce:
open GH file that has multiple compute methods on the canvas
Expected behaviour:
I would expect that the projectID could be set/compute before all others, however we did not program this to act in this way.
Description:
In Grasshopper, since the projectId is set by canvas node/compute method, it is possible that other canvas nodes/methods would compute before the projectID method creates the projectIDEvent. Users are reporting that they still get the popup even though the setprojectID canvas node/method was set in previous sessions.
Revit/Excel retrieve the projectId value from queryable internal data fields and do not require a compute of a projectIDEvent to set the projectId, so I do not expect this to be an issue in these toolkits.
We've not yet set up any method of pre-setting the projectId in Dynamo, but were we to do so, I would expect this to occur in Dynamo as well.
Steps to reproduce:
open GH file that has multiple compute methods on the canvas
Expected behaviour:
I would expect that the projectID could be set/compute before all others, however we did not program this to act in this way.
Test file(s):