Esenthel Wrote:Aren't you using an older version of the engine (2.0)?
Actually, I am using 1.0, 2.0 and the latest <no version number> version of the engine as I have several projects spread across different versions. My aim is to gradually upgrade projects on to the latest EE code, so that I can eventually do away with the older versions. So to do that I have to keep a close eye on the update changes and investigate anything that may cause an issue, such as this.
For example, I have built a GUI system on top of the EE GUI that uses dynamic (and procedural) styling done in code and with custom shaders. Unfortunately, the new skin system in EE just isn't sophisticated enough to handle what I'm doing, so I will have to disable that and override most things.
Esenthel Wrote:Yes you can override the class
The methods are virtual. You override the combobox and the button at the same time.
Hmm... this just leads to duplicate code. Under the old system, I have all the code for the button in one place and I just tell the combobox to use that type of button. This new system would force code to be duplicated in two places, to override both the normal button and the combobox button. It is that reason why I built my own tabs too, as I couldn't use the Tab control in EE as I couldn't replace the button the tabs use.
Oh and while we're on the subject, why is the Menu in Combobox not a FixedElm<Menu> so it can be replaced?