Yep
args.data is a wrapper for the actual data being stored, which you then need to extract by format using getData and the format type (that big ol’ string in the case of a dotnetmxsvalue). That gets you the dotnetmxsvalue… which in turn is a wrapper for actual max data (the material), so gotta get that through .value.
wrappers within wrappers within event arguments within drag&drop events within abstracted dotnet objects within maxscript within max. whee!
not in 2010, eh? ;
Another script developer basically just created his own sphere and called ‘render selected’ on that… seemed to work okay; it’s more-or-less what medit does under the hood as well anyway.
Yup, that’s pretty much what I’m doing right now. But it’s not pretty… and it can be messy. One of these days I’ll learn some C and write a mxs extension. I think the Helium extension allowed that so it should be possible.