Black rectangle, if using awesomewm

[zervanko]

Hello. As audacity is built on wxwidgets platform, so I think, you can help.
The problem is explained here ​https://github.com/awesomeWM/awesome/issues/2292 and here ​https://github.com/awesomeWM/awesome/issues/2382
Code of splashscreen for audacity is here: ​https://github.com/audacity/audacity/blob/master/src/AudacityApp.cpp

[vadz]

This could be a wxWidgets problem, but I'm really not sure about it. The simplest way to test this is to compile and run the "splash" sample present in wxWidgets distribution. If it doesn't show the problem, then this is clearly not a bug in wxWidgets. If it does show it, it might still not be a bug in it (but a bug in WM for example), but this would at least prove that it's not a bug in Audacity.

Please check if you do see the problem in the splash sample.

[zervanko]

g++ splash.cpp `wx-config-gtk3 --cxxflags --libs` -o test

I tried this, but:

splash.cpp:64:25: error: expected ';' at end of member declaration
     virtual bool OnInit() wxOVERRIDE;
                         ^
                          ;
splash.cpp:64:27: error: 'wxOVERRIDE' does not name a type; did you mean 'wxEVT_IDLE'?
     virtual bool OnInit() wxOVERRIDE;
                           ^~~~~~~~~~
                           wxEVT_IDLE

[vadz]

You need to use the version WX_3_0_BRANCH if your wx-config is from this version.

Alternatively -- and even better -- you could download and build wxWidgets 3.1 from Git master and then you could compile this sample using it.

[zervanko]

Sorry, I can't build it. I tried 3.0.4, 3.1.1 but splash example fails to build with different errors, and I don't know why.

[vadz]

Sorry to hear it, but the sample really should build with both 3.0 and 3.1. The only way to have problems with it is if you mix the different versions as you've somehow seem to do.

If you follow these simple steps:

1. git clone https://github.com/wxWidgets/wxWidgets.git
2. cd wxWidgets; mkdir build-gtk-debug; cd $_; ../configure; make -s
3. cd samples/splash; make -s; ./splash

it should work without any problems.

[zervanko]

Replying to vadz:

Sorry to hear it, but the sample really should build with both 3.0 and 3.1. The only way to have problems with it is if you mix the different versions as you've somehow seem to do.

If you follow these simple steps:

1. git clone https://github.com/wxWidgets/wxWidgets.git
2. cd wxWidgets; mkdir build-gtk-debug; cd $_; ../configure; make -s
3. cd samples/splash; make -s; ./splash

it should work without any problems.

Noob question, but will it break my current wxgtk installed by package manager?

[vadz]

No. Just don't run make install.

Also, after finishing with this, you can just rm -rf build-gtk-debug to clean up (you could also rm -rf the entire wxWidgets directory, but unless you don't have much disk space, I recommend keeping it, as it's a big download and it might be useful to have it for the future, as updating an existing git clone is much faster than recreating it).

[oneeyeman]

Vadim, let me correct you.

Replying to zervanko:

Replying to vadz:

Sorry to hear it, but the sample really should build with both 3.0 and 3.1. The only way to have problems with it is if you mix the different versions as you've somehow seem to do.

If you follow these simple steps:

1. git clone https://github.com/wxWidgets/wxWidgets.git
2. cd wxWidgets; mkdir build-gtk-debug; cd $_; ../configure; make -s
3. cd samples/splash; make -s; ./splash

it should work without any problems.

Noob question, but will it break my current wxgtk installed by package manager?

The first step should be

git clone ​https://github.com/wxWidgets/wxWidgets.git --recurse-submodules

[zervanko]

Replying to vadz:

No. Just don't run make install.

Also, after finishing with this, you can just rm -rf build-gtk-debug to clean up (you could also rm -rf the entire wxWidgets directory, but unless you don't have much disk space, I recommend keeping it, as it's a big download and it might be useful to have it for the future, as updating an existing git clone is much faster than recreating it).

Well, thanks. Splash example seems working on awesome, but audacity's splash screen still not.

[vadz]

Then it could be fixed in 3.1 branch -- or it could be due to something specific that Audacity does.

To check the former, you can do

• git checkout v3.0.4
• mkdir build-3.0.4; cd $_; ../configure; make -s
• cd samples/splash; make -s; ../splash

(you can do git checkout master to return to the master afterwards).

But if it really only affects Audacity, the task of fixing the bug belongs to Audacity developers.

[zervanko]

Replying to vadz:

Then it could be fixed in 3.1 branch -- or it could be due to something specific that Audacity does.

To check the former, you can do

• git checkout v3.0.4
• mkdir build-3.0.4; cd $_; ../configure; make -s
• cd samples/splash; make -s; ../splash

(you can do git checkout master to return to the master afterwards).

But if it really only affects Audacity, the task of fixing the bug belongs to Audacity developers.

I just don't understand architecture of splash screens. The problem at least affects audacity and probably lmms. LMMS is using QtSplashScreen and on awesome it shows grey window instead of it's logo. It looks, like in some cases awesome can not get in time. Maybe it opens splash screen window too fast, I don't know. Thank you for helping, anyway.