Dynamo: Crash report from Dynamo 2.3.0.5885

Created on 21 Jul 2020 · 4Comments · Source: DynamoDS/Dynamo

Issue Description

Please fill in the following information to help us reproduce the issue:

What did you do?

I was creating a new custom node

What did you expect to see?

I expected it to work normally

What did you see instead?

Right after filling in the name data and adding on category the Dynamo crash ... I imagine from the beginning of this description of error that may have to do with Dyna standart, is my guess correct?

What packages or external references (if any) were used?

Clockwork v.2.3.0
Chynamo v.0.8.5
Orchid
v. 203.1.2.7323
Rhythm v.2020.2.13
GeniusLoci v.2019.9.4
Zebra v.2016.7.2
MEPover v.2018.1.1
archilab v.2020.23.10
Crumple v.0.0.1
Modelical v.2.2.15

Stack Trace

Object reference not set to an instance of an object.

   at DynaStandard.DynaStandardEvents.NewDynamoRunTypeChange(Object sender, PropertyChangedEventArgs e)
   at System.ComponentModel.PropertyChangedEventHandler.Invoke(Object sender, PropertyChangedEventArgs e)
   at Microsoft.Practices.Prism.ViewModel.NotificationObject.RaisePropertyChanged(String propertyName)
   at Dynamo.ViewModels.DynamoViewModel.set_ShowStartPage(Boolean value)
   at Dynamo.ViewModels.DynamoViewModel.ShowNewFunctionDialogAndMakeFunction(Object parameter)
   at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
   at System.Windows.Controls.MenuItem.InvokeClickAfterRender(Object arg)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

OS: Microsoft Windows NT 10.0.18363.0
CLR: 4.0.30319.42000
Dynamo: 2.3.0.5885

Source

LuisaCPBR

All 4 comments

Ps. Apparently is indeed a crash caused by DynaStandard ... I moved it away from my package folder and now it works perfectly

LuisaCPBR on 21 Jul 2020

Hello @LuisaCPBR - Good spot. Please do try uninstall "DynaStandard" first, and see if the same issue exists. It most likely is DynaStandard and if so, pleas let Brendan Cassidy know (The author)! https://twitter.com/brencass86 - He's super nice.

Amoursol on 21 Jul 2020

👍1

Hello @Amoursol I believe that just remove it from the folder it is enough to uninstall it (I don't find it when go to manage packages since it is an extension). Cool, thanks a lot Sol!

LuisaCPBR on 21 Jul 2020

👍1

Sorry I have only just seen this issue and the link to the project github page.

This was a little oversight by me, i forgot to add in a check for "CustonNodeModel" then not to run the runtype setting change.

This will be fixed in the next release of DynaStandard in the next 24-48 hours(V1.1.0), this update will be on the Github project page and on the Dynamo package website. Of course information will be on the forum topic i have here(https://forum.dynamobim.com/t/dynastandard/42315)