When using RenderContent.OpenInEditor() on a material’s child texture (from within the Materials panel), the texture is shown in the Textures panel rather than the Materials panel. This differs from the expected/desired behavior seen when selecting a child texture of a Rhino Custom material, where the texture is shown “in place” in the Materials panel.
If the Textures panel is not open, OpenInEditor() still succeeds, but “nothing” appears to happen (in fact it is still selected in the not-visible Textures panel), so it just seems to the user that your button for selecting the child texture does not work. To edit the child texture “in place” the user must select the texture using the Materials treeview, or the material’s breadcrumb nav.
Anyway, that is how things are working here, so I would like to know if this shows a bug, or if there is perhaps some way I need to set the context for OpenInEditor(). Attached is a minimal example that reproduces the described behavior.
TestEditTexture.cs (5.5 KB)