Audacious Qt

[psijic]

Hello. I installed Audacious (3.8.2-2.1) via YaST from Packman repository and it installed next dependencies:
|libaudqt1 - QT GUI implementation of Audacious
|
[TABLE]
[TR]
[TD]libaudgui4 - GTK GUI implementation of Audacious
|

[/TD]
[/TR]
[/TABLE]

So, Audacious has GTK UI by default but I’d like to use it with Qt. How can I switch to it without rebuilding sources?
The official website sayed:

Audacious uses GTK+ by default but can be configured to use Qt. When running ./configure, use the --enable-qt and --disable-gtk options as desired. Any combination is possible: GTK+ only, Qt only, both, or neither (for a headless music player “daemon”).

But I’d like to use it from repository. because configure sayed:

“No package ‘glib-2.0’ found” Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GLIB_CFLAGS
and GLIB_LIBS to avoid the need to call pkg-config.

And I have libglib-2_0-0 and don’t know are they the same libs with different names or something else bla-bla-bla.

[I_A]

you need the devel packages to compile against
open yast and search for glib devel

[wolfi323]

@psijic

So, Audacious has GTK UI by default but I’d like to use it with Qt. How can I switch to it without rebuilding sources?

Run it like this:

audacious --qt

[psijic]

@wolfi323

Run it like this:

audacious --qt

hm, I thought about something like this, don’t know why forget to try. Thanks.
My bug with unresponsible tray icon dissapears too.

[wolfi323]

@psijic

My bug with unresponsible tray icon dissapears too.

JFYI, this should finally be fixed in Plasma 5.10.1, and I plan to submit an update to 42.2 with the fix too.

See 1026999 – Plasma System Tray Icons show no menu and 362941 – Java Process Is Unresponsive In System Tray - Jitsi .

But there may of course be other reasons to prefer the Qt5 version…

[psijic]

@wolfi323

JFYI, this should finally be fixed in Plasma 5.10.1, and I plan to submit an update to 42.2 with the fix too.

See 1026999 – Plasma System Tray Icons show no menu and 362941 – Java Process Is Unresponsive In System Tray - Jitsi .

But there may of course be other reasons to prefer the Qt5 version…

Nice. My “gnome global hotkeys” plugin after QT disables too but I think I should to configure global KDE hotkeys or buy a media keyboard

[psijic]

Hm. Not a necropost and sorry to bother you again but there is another question. Qt version don’t have a songs search dialog (Ctrl+F)?

[wolfi323]

@psijic

Qt version don’t have a songs search dialog (Ctrl+F)?

I have no idea, and I never used it.

But there may be reasons why you can’t select the Qt GUI in the settings (yet?).
AIUI, it’s still “experimental”.

[psijic]

@wolfi323

I have no idea, and I never used it.

But there may be reasons why you can’t select the Qt GUI in the settings (yet?).
AIUI, it’s still “experimental”.

I think no one optimised application can switch between Qt/GTK in run mode. But many apps are moving from GTK to Qt

[wolfi323]

@psijic

I think no one optimised application can switch between Qt/GTK in run mode.

No, but audacious could store it in its settings and then choose to start in “Qt mode” the next time you run it.

After all, there is this command line option, so I think that should be possible…

But many apps are moving from GTK to Qt

Right, and that’s a good thing IMHO (I’d prefer Qt over GTK any day… ).

The main reason for this is probably that GTK’s developers chose to become the GNOME ToolKit, instead of the GIMP ToolKit as it originally was with GTK1 and 2.

And one reason why GTK was preferred over Qt in the past is that Qt was (supposed to be) not completely free. But that has changed meanwhile…