@stevebaer@dale@Gijs@brian I see that this item get’s pushed each sprint, is there any way we could get some priority on this issue? Without the API to interact with the UI, any plugins producing a non-Rhino like UI are essentially broken requiring users to manually hide/close UI on a new install.
Perhaps you can make a smaller work item, that is just giving us the ability to close panels, rather than fix the whole disconnected UI API for Rhino 8. That would at least let us move forward without too much work on your part (hopefully).
according to John Morse this should be the way to do it:
This is what I believe you need to do for your skin:
Start Rhino on your developer box
Configure the UI the way you want it to appear
Run the WindowLayout command or go to the “Windows/Window Layouts/Manage Window Layouts…” menu option
Click on the + in the top left corner of the dialog and then click “Yes” to save the current layout
Give the layout a name like “My Product Default”
Right click on the new window layout
Export the window layout to the folder containing your skin DLL and use the same name
Close Rhino
Delete your %APPDATA%\McNeel\Rhinoceros\8.0\settings directory (This will simulate starting for the first time)
Restart your skinned Rhino
You should now see your custom layout applied as the default UI layout and if you display the “Windows/Windows Layouts” menu you should see your custom layout as the default layout. The built in Rhino layouts have been removed and replaced with yours. You can add additional RHW files to your DLL directory and they will appear as system layouts. Adding these RHW files to your installer and extracting them to the same directory as your skin DLL will provide this user experience for your users.
I’ll give that another try. The last time I attempted a default layout, I didn’t have any luck. Do you know the minimum Rhino SR for this functionality to work in?
@Gijs@JohnM I’ve confirmed this is not working, this is the same behavior I observed when I first tried the layouts feature a few months back.
I followed the steps to create a layout, I’ve applied the layout to verify it works. Then I’ve exported the layout and included it in our build process, so that it ends up in the same folder as our plugin, named as specified.
If I clear the settings folder: %APPDATA%\McNeel\Rhinoceros\8.0\settings
And then build our plugin, you can see here the *.rhw file is present.
We start Rhino with our own custom scheme, and the layout is still the Rhino Default. It does not appear to find the related Window Layout. Is this related to our Scheme?
hi @jstevenson, thanks for testing this, I am sorry to hear it is not working. I made this a high priority bug to get fixed: RH-80372 Can’t load a customized Window Layout correctly
I just retested this, after re-reading your message, and trying a different name for the rhw file.
I had been naming the rhw file the same as our PLUGIN, but it seems it needs to be named the same as the SKIN dll file. I’ve confirmed this appears to work in that scenario.