2015-02-10, 12:01
(2015-02-10, 11:58)jurialmunkey Wrote: It was my understanding that the overrides.xml file was *not* shared - that only menu groups were. I thought that was the point of the overrides file - to provide skin specific functions like widgets and background etc. Either way, the overrides will solve a big part of the issue - my problem was that users had menu items that pointed to variables that only existed in Titan. If the overrides are shared then it doesn't matter because at least they point to something so that they work when clicked on from another skin. I can see what you are saying though - for instance, what If I want to use a custom window for something (e.g. hubs in Eminence use custom windows).
I had assumed there was a way to *not* share the menus, but like you, after digging through the documentation I really can't see any possible way. It seems a little irrelevant to be able to set defaults on a per skin basis if we decide on a set of standards - it would be basically the same thing as simply forcing a standard default menu on all skins and we start losing that individual flavour. It would be best if we could just set a flag that indicates whether the menu is to be shared or is skin specific.
No, the overrides get written to the xml of the shortcuts so will also be shared across skins.
If anyone knows about a way to NOT share the menus I can consider to use that with Titan.
In the meanwhile I'll start digging around with the overrides for actions and see if that's not going to hit too hard on performance