Please correct me if I am wrong, but it appears that
thsi UI crashing (as you have identified it) is in
fact a known bug, one that crept into the RC1
release, but had not been present in the earlier
Beta. It apparently can be triggered by a number of
things, including changing resolution and activating
Unity, and caused/exacerbated by enabling 3D
accelleration.
Yes, although I'm not sure about the 3D part - the duiIconConverter.m:221 bug should have nothing to do with 3D. I could believe that 3D and Unity don't play well together, but I'm not actually aware of someone pinning this down (the references in the thread I linked aren't specific enough).
According to team member bghertzfield, this issue is
being worked on; but according to Pat Lee, not to the
point where Unity will be supported on dual monitors.
One can only hope and presume that it will work as it
did in an earlier release, i.e. guest windows under
Unity will be transferred to the primary display, and
won't be movable to the secondary display.
You're confusing several bugs:
\- duiIconConverter.m:221 (causes the UI to crash - this is what Ben was talking about)
\- multiple monitors don't work with Unity (contents smear on other monitors - this is what Pat was talking about)
\- something about 3D and Unity (don't know about this)
Are you sure about the prior behavior of Unity windows? I don't really use Unity, so may have overlooked it, but I don't think it ever prevented you from moving windows to other displays.
