OrkestraOnline / Orkestra_Online

Orkestra Online is a cloud based platform for deploying, documenting and securing DynamoBIM and Grasshopper content.
https://www.orkestra.online
40 stars 2 forks source link

Selecting some graphs won't show the correct information #74

Closed Dre-Tas closed 3 years ago

Dre-Tas commented 3 years ago

This happens when I'm using the desktop app, or when I click on the settings button from Revit and Dynamo: Some of the graphs won't update the information panel on the right. Probably easier to visualise. Check the screengrab below: MiL4AyS2yh

As you can see when I select the graphs named _ElementsSortByCurve and _UnitsTranslate the panel on the right that shows name, version, description, etc doesn't update to the new graphs. If I then select one of the other graphs, then it will update.

It looks like something breaks in the background while retrieving the data and so Orkestra is unable to display the correct info.

I'm also noticing that those graphs are among the ones that break Dynamo when you try to save and the give the "Element not set to an instance of an object" exception when trying to save to Orkestra with the Save button.

MostafaElAyoubi commented 3 years ago

Thank you very much for reporting @Dre-Tas ! This relates to part of what is described in issue #72 . It has been identified and fixed. A hotfix fixing this will be released this week. The part that is new though is the "Element not set to an instance of an object" exception when trying to save to Orkestra with the Save button. Will investigate and hopefully include this fix as well! Will update this thread soon.

Dre-Tas commented 3 years ago

I managed to record a video of the error: alI2Q8yWlU_1

As you can see if I then try to close the file in Dynamo I get an error and Dynamo itself shuts down (but this might be related to another package)

MostafaElAyoubi commented 3 years ago

This is solved in v.1.1.1

Dre-Tas commented 3 years ago

So what was the issue? I'd be just curious ;)

MostafaElAyoubi commented 3 years ago

It was due to some legacy conditions where some of the metadata didn't exist. Those cases needed to be handled.