Custom Explorer and Properties windows (i.e. Jexplorer, Classic Explorer, etc.) are not interoperable with the official counterparts. One reason for this is the inability to use the instance picker, which is triggered when changing a parent via the properties window. The official and upcoming next-gen Properties window can use the instance picker and is internally invoked using plugin:GetPluginComponent("InstancePicker"):PickInstanceAsync(). This API is not accessible to user plugins and this is the only way to use it.
I am suggesting a public API that can facilitate usage of the instance picker. Promoting the instance picker to a public API will benefit both internal plugins and user plugins alike, as they can communicate with each other under a single API similar to how some built-in plugins use the Selection service.
Implementing this can open the door for more powerful plugin APIs within Studio and allow user-made plugins to be as powerful as the built-in plugins.
Examples:
- Custom explorer or property windows can interact with the official versions, creating groundwork for interoperability
- Instance picking initiated by user plugins can use the official cursor which helps establish consistency