CEGUI (Crazy Eddie's GUI) Forums

Bertram: Cool. Are there any plans to package CEED as well? If you are updating to CEGUI 0.8 it should be trivial to package CEED 0.8.0.

That's a good point. I think that would be a nice change to our build system.

So.. who's going to produce the patch?

It actually can be a valid use case. That's why it's not an error.

For users that are initializing the library and passing their own XML parsers or image codecs that they built as part of their project.

They are set automatically but at least one XML parser and Image codec has to be found. Else it's set to "". I think.

cmake does warn you that none is going to be built but it is possible to miss that message.

Either your default image codec is "" or your default xml parser is "". Or both.

I think using the macro is fine. We never supported Ogre 2.1 anyway so if we "break" ABI for Ogre 2.1 it's not really a break.

Your proposed change isn't the solution.

Keep in mind that we generate C++ code for the bindings and commit it so that our users don't have to install pyplusplus. So the generated code needs to work everywhere. Your fix just doesn't accomplish that.

Please make a patch out of this and consider making a pull request. Contributing via code drops is better than not contributing at all but it makes it very painful for me to accept your contribution.

If it doesn't break anything we can merge it to v0-8.

Run


Either the file itself or its dependency is not in PATH. That's why the loader can't find it.

Yes, thanks. I merged it.

Yeah, seems like a typo. Could you submit a pull request please?

We can make those 2 methods virtual but the change has to go to default.

IMO the best way to get fresh and correct property lists with docs is to use CEED. CEED queries the widgets for properties so it gets properties from the C++ classes and LNF WidgetLooks. It even works for custom skins that you created. It would be a pretty cool little project to write a small script...

Please note that you are not forced to use MVC, you can if you want to or you can use the integrated class that has the model and view inside for the old behavior.

Sort of similar to how Qt does it with QTreeView vs QTreeWidget.

Yeah, this change will most likely break API and cannot be done on v0-8. IMO you need to introduce an enum to allow this option, change the API accordingly and apply it to default. If you want it in v0-8 you would then cherry pick that one commit there and keep your own v0-8. The change will most li...

Hi, please rebase against CEGUI default. Your contribution can't be cleanly applied because there were too many changes between 0.7 and 0.8. Rejects from the first diff: unable to find 'cegui/include/CEGUIConfig_xmlHandler.h' for patching 4 out of 4 hunks FAILED -- saving rejects to file cegui/inclu...