1 Dec
2012
1 Dec
'12
7:49 p.m.
Many thanks everyone for your help--it appears Unity is to blame here...
-----Original Message-----
From: linux-audio-user-bounces(a)lists.linuxaudio.org [mailto:linux-audio-
user-bounces(a)lists.linuxaudio.org] On Behalf Of Adam Sampson
Sent: Friday, November 30, 2012 11:17 AM
To: Ivica Ico Bukvic
Cc: A list for linux audio users; An open mailing list for a world-wide
network
of aspiring L2Orkists, L2Ork developers, contributors,
and supporters.
Subject: Re: [LAU] question about qjackctl explicitly setting the wm class
name
Ivica Ico Bukvic <ico(a)vt.edu> writes:
have
is there a way to explicitly set the window class
name in qt [...] and
if so, would it be possible to add this to the future releases of
qjackctl?
Qt sets the class name to argv[0] by default -- so qjackctl should already its class set sensibly (or semi-sensibly -- it's
called qjackctl.real on
Debian
because there's a wrapper script that runs
qjackctl; Ubuntu may have the
same thing).
You can use xprop to see what the class has been set to: run xprop, click
on
the qjackctl window, and look for WM_CLASS in the
output.
I'd be a bit surprised if it's not getting set at all, but maybe it's set
to
something unusual, or Unity's doing something more
magical than you
think...
--
Adam Sampson <ats(a)offog.org> <http://offog.org/>
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user