Great job!
I would like to know, do you plan to implement treeviews?

I might do that some time, but I'm can't say that for sure now.

But I will most propably make an update some time, which will include editboxes with multiple lines, maybe window menus (like File, Edit,...), and some bugfixes. But I can't promise that it will include treeviews.

Thank you Lukas. We appreciate it.

was working on a new theme for lbgui, but then accidentaly saved wrong files over them. Going to remake them though.

Sounds interesting. If it looks good, I might include it to the update, together with the old theme, to show how easily you can mix two themes.

Because there was some criticism of LBGUI in the german podcast (thanks to my game), I want to speak out here to stress that LBGUI was extremly helpful for me and saved me a lot of work.

I really didn't find to hard to learn it. The long functions and many parameters are the price you pay for its functionality. The manual gives you all the information you need. I have to admit that I was afraid to use it when it first came out because even the small example file was so huge. Working through and understanding the small example took ~30 minutes, after that I knew everything I needed.

My advice: Split the small example into two files: on "skin.c" file where all the bitmap and struct definitions are. make sure you create LBG_*_BMAPS for all the components, so you don't have to create temporary structs in the function calls, bloating them up. Then you have one small file left where the function calls are in and everyone can see how easy it really is.

Just note somewhere that temporary LBG_*_BMAPS structs exist and that you don't need to have a single skin but can mix then as you like.

And JustSid is partly right with the flag names. why not share some? on the other hand, its easy to derive the name of the flag for each component.

What you could also implement is an easy interface. I saw this in other c-libraries. If you don't need the full functionality of the library you can use the easy interface: It has functions with less parameters and functionality but are shorter and easier to use.

I saw such an easy interface wrapper in the lite-c contributions, but it could also be implemented by default.

The perfect LBGUI would have 2 modes. One is the pure API. And the other one is a flexible GUI editor. Would love to click together my menus, export the code and graphics and afterwards just include them in the project.

Sure, that`s a lot of work. Maybe you could work together with the other guys from AckStudio

I really like the LBGUI - even if I didn't worked a lot with it YET and it get some critics... Implement some of the suggestions like making it more structural/user friendly and implement the most important features like multiline text field, text selection and copy/past - would be awesome

Thanks anyway for that good stuff!
(who knows when ever conitec would have released their GUI DLL -> but I remember it had a "high priority" until it was removed - guessing cause of Lukas' GUI )

Thanks for the kind words.

The skin.c is a good idea. I can make it be usable as a header script that is included at the beginning of the main script for all who want to use the default skin.

Before I'd make an editor, I think it would be useful to make an XML-like syntax for defining GUI elements. Then I could make an editor that creates those XML files. Those files would then be easier to be reopened by the editor.
But if I can ever do that it will be in the far future...

An improved API and multiline text fields will certainly be part of an update some time.