TGUI: a c++ GUI for SFML (with Form Builder)

[TechRogue]

Ah, okay. I'm a little unclear on the intricacies of const-correctness, so I wasn't sure if there was any reason to do it that way.

[basic_prog]

I can't get your example code to work. It compiles fine but i get linking errors ... I added all the libs... (system,window,graphics,and libtgui.a)
I'm using Code::Blocks , gcc 4.6
C:\TGUI\lib\32-bit\libtgui.a(Panel.o):Panel.cpp|| undefined reference to `_imp___ZN2sf4FontaSERKS0_'|
C:\TGUI\lib\32-bit\libtgui.a(Panel.o):Panel.cpp|| undefined reference to `__gxx_personality_sj0'|
C:\TGUI\lib\32-bit\libtgui.a(Panel.o):Panel.cpp|| undefined reference to `_Unwind_SjLj_Register'|
C:\TGUI\lib\32-bit\libtgui.a(Panel.o):Panel.cpp|| undefined reference to `_imp___ZTVN2sf4TextE'|
C:\TGUI\lib\32-bit\libtgui.a(Panel.o):Panel.cpp|| undefined reference to `_imp___ZTVN2sf11VertexArrayE'|
 
Downloaded last version of TGUI

[texus]

I don't have much time right now to search the problem.
I just checked and the library was build with gcc 4.4.1, maybe that's causing the problem.

For now, until I get the time to test my 32-bit lib, you will have to build it yourself.
If you don't want to build it then you can always just add the source files directly to your project.

To build it yourself:
- Make an empty project and add all my cpp files.
- Make sure the include directory is set.
- Don't link to any library.
- Set the build type to "Static library" (Project>Properties>Build targets>Type)
- You might need to compile with -fPic.

I will try to test my 32-bit lib as soon as possible (which means hopefully this weekend).

[Laurent]

This kind of error happens when you mix two incompatible versions of gcc. Sadly, on Windows there are two versions that are equally maintained and used: the DW2 version and the SJLJ version.

[Silvah]

This kind of error happens when you mix two incompatible versions of gcc. Sadly, on Windows there are two versions that are equally maintained and used: the DW2 version and the SJLJ version.

If only it were this simple. Exception handling method is probably the least annoying issue, as it causes linking errors when something is wrong. At least sometimes.
As an aside, this distinction applies to every platform on which GCC supports zero-cost exceptions (on these it doesn't, setjmp/longjmp is the only choice). It just happens that on Windows there's no consensus on which unwinding to use.

There are some more possible differences between GCC builds (these affect Windows only):

• runtime library: mingw-rt + w32api vs MinGW-w64
• GCC threading model: win32 vs posix
• GCC version: 4.7+ vs older versions - GCC 4.7 for Windows on IA-32 starts to use different calling convention for non-static member functions by default (thiscall, as most other compilers on Windows do), which is incompatible with the one used by older versions (cdecl).

Hence, if you don't want to take chances, it's best to have compiled everything with the very same compiler.

[Laurent]

This is even worse that what I thought. I have no idea which precompiled versions of SFML 2.0 for gcc on Windows I should provide

[Silvah]

This is even worse that what I thought.

Yup. And I didn't even say anything about third-party patches which also can make the thing incompatible with everything else. Therefore...

I have no idea which precompiled versions of SFML 2.0 for gcc on Windows I should provide

...I think the best way is to provide no precompiled versions at all. Just provide clear building instructions, then even inexperienced users should be able to build it themselves.

[MorleyDev]

I guess you could set it up for gcc so all they have to do is CD to the folder in the command prompt and run make? The most complex part of that is ensuring that make is in your path.

[Laurent]

The problem is that CMake create build files with absolute paths inside. To distribute something as simple as "set PATH ... & make & make install" I would have to create specific makefiles.

I think I'll provide a release for the version of gcc shipped with Code::Blocks, since many people are using it (especially beginners). Don't know about other versions.

[basic_prog]

This kind of error happens when you mix two incompatible versions of gcc. Sadly, on Windows there are two versions that are equally maintained and used: the DW2 version and the SJLJ version.

Thx, i didn't know that 

I just checked and the library was build with gcc 4.4.1, maybe that's causing the problem.

For now, until I get the time to test my 32-bit lib, you will have to build it yourself.
If you don't want to build it then you can always just add the source files directly to your project.

I'll build it and see what happens. thx

[texus]

Good news: the first version of the Form Builder is ready!




I have also made some changes to TGUI. The most important are:
- Mac OS X support
- Label has a callback on click
- All object have a getSize function
- Some bug fixes

And now the bad news: the form builder is far from being finished.
- You can already drag objects around, but for scaling you will still have to change the property manually.
- A lot could be improved if my gui would be able to create child windows, which won't happen anywhere soon.
- There is no load function yet. You can only save a file.
- Negative positions don't work.
- I just noticed that you can't remove an object.
- There are no binaries for Linux yet.

EDIT: I just fixed the most important problem: you couldn't remove objects.
I also made it possible to set an object to a negative position and I provided linux binaries.
The other problems will have to wait until I release TGUI v0.4.

[edge87]

Has anybody tried to use this with the latest SFML 2.0 RC ? It compiles correctly but after the init function it seg faults.

[texus]

I wish I could try if it works with the rc version, but I can't even get it to compile and I don't have the time to find out what I am doing wrong.

There were hardly any modifications in sfml2 since the version that can be found on my site. Does it work with this version?
If so then you can use that version until I have the time to compile a new lib.

If you really can't get it to work then without segfaults then you should temporary use the tgui source code directly in your project instead of using the library.

[texus]

The Form Builder didn't work correctly, so I couldn't delay my release till July.
TGUI v0.4 is not finished, but you can already download the latest revision (which is just as stable as v0.3.6 was).

Changes:
- The Panel struct has been rewritten and has been tested.
- Objects can be moved to the back or to the front.
- In the Form Builder v0.2, save and delete buttons now work correctly and a load button was added.
- You can also easily scale the objects in the new Form Builder.
- In the new TGUI Object Files v0.2, you can add panels and use multiline comments.

Because most of my library files didn't work, I now have a complete new way of distributing.

The latest version can now be downloaded on GitHub.
You will have to build it yourself with CMake. I have already started with writing tutorials.

If you are using Mac OS X then you will have to wait a little bit for the libraries.
Until I finish my CMake script you will have to use the source code directly.

The Form Builder is only provided for Windows, but the source code is also provided, so you can use it on Linux or Mac too.

[argoneus]

Hi, I've got a question. I'm a newbie to SFML and I want clarification on one thing. TGUI includes everything SFML has, correct? E.g. if I create a TGUI window, I can use it in the same way I would use a SFML one? What if I want to use stuff such as SFML/Network.hpp, or even OpenGL?

And one more thing: Is it possible to change the textures/colors if I don't like the default ones?

Thanks a lot.