Rick Blommers

@drydh Yep it sure looks like it's related. Thanks for your comment!

Good question. I think the default colors for QtAwesome should be retrieved from the system. ```c++ QApplication::palette() ``` At the moment they are hardcoded!

Thanks for your response.. In issue #16, I explained the reason why I didn't create a singletonclass: > I’ve been thinking about singleton when I created the library. > I...

Maybe you can just use your own singleton function in your application? ```c++ QtAwesome *qtAwesome() { static QtAwesome* qtAwesome = nullptr; if( !qtAwesome ) { qtAwesome = new QtAwesome(); qtAwesome->initFontAwesome();...

I'm seriously considering to merge this. I don't know cmake, so I haven't test it. But I've seen several forks trying to implement this, so it looks like people want...

@Drapegnik There's one issue why I still haven't merged the code. You've changed the QtAwesomeSample/main.cpp file and changed the include to "../QtAwesome/QtAwesome.h". The example should also be buildable from another...

Same problem here: (Running on a FreeBSD 10 environment) ``` linking shared-object sassc/libsass.so /usr/bin/ld: unrecognized option '-plugin' /usr/bin/ld: use the --help option for usage information c++: error: linker command failed...

This is not yet available, but would be very nice to have!

This is not yet completely fixed. At the moment it allows you to add carets from the top to the bottom. (You cannot add ranges before the last one) To...

I also agree that c++ is the way to go. Because it can be integrated in other project that way... @brupelo I agree some items are complexer (and more abstracted)...