Please close this issue -- it was caused by a null parameter being passed to SetToolTip.

Was this crashing (restarting) Unity? If affirmative then we need to solve that.

Yes -- it crashes Unity. Seems to be two separate behaviors. 1) Sending in null to SetToolTip causes a crash. and 2) FindName for a listboxitem seems to always returns null.

encl. crash .dmp for above issue.

@sfernandez, this is the native code crashing (obj is null)

void ToolTipService::SetToolTip(DependencyObject obj, BaseComponent toolTip)

{

NS_ASSERT(obj);

obj->SetValue<Ptr<BaseComponent> >(ToolTipProperty, toolTip);

}

By the way, the check against NULL must be done at C#, not in C++, where asserts are being used.

Sure thing, no problem. Just curious -- why does it crash instead of throw an exception?

It was crashing because the native code wasn't checking if the input parameter was null, so an unhandled exception was generated closing Unity.
We added checks for all the attached properties functions so proper exceptions are thrown in C# code.