FVWM: Window for qwit (or qtwitter) not shown after FVWM is restarted

[Markus Hutmacher]

Hello,

I'm using FVWM-2.6.1 on Slackware64-current. I've installed qwit (and
also qtwitter) as Twitter-clients. Both are shown in stalonetray and
work as expected. But when I restart FVWM before closing qwit, it is
shown in stalonetray, but I cannot manage the window to be shown. When I
use the "show/hide" option at the icon in stalonetray, the desktop is
changed, but still no window. The same is true for qtwitter, both (as
the name says are qt-based. Exiting FVWM and restarting doesn't work either.

But when I start qwit or qtwitter in KDE and afterwards again in FVWM,
both work as expected.

Here my question: what does KDE with the programs what FVWM does not? is
there an option I can use in the configuration? My configuration is

DestroyFunc FvwmQwit
AddToFunc FvwmQwit
+ I Exec exec qwit
FvwmQwit

Thanks in advance

Markus

[Thomas Adam]

Post by Markus Hutmacher
Hello,
I'm using FVWM-2.6.1 on Slackware64-current. I've installed qwit

At least try 2.6.4.

Post by Markus Hutmacher
(and also qtwitter) as Twitter-clients. Both are shown in
stalonetray and work as expected. But when I restart FVWM before
closing qwit, it is shown in stalonetray, but I cannot manage the
window to be shown. When I use the "show/hide" option at the icon in
stalonetray, the desktop is changed, but still no window. The same
is true for qtwitter, both (as the name says are qt-based. Exiting
FVWM and restarting doesn't work either.

Well, I suspect that qwit is doing something like this:

* Click on systray icon -> Focus Window.
* Click again on systray icon -> is window mapped ? Hide : Show

It's entirely possible that through the systray icon, FVWM thinks the window
is in the WithDrawn state, or something, and is never mapped again because
of it.

I took a very quick look at this using qwit, and cannot reproduce your
problem.

Post by Markus Hutmacher
But when I start qwit or qtwitter in KDE and afterwards again in
FVWM, both work as expected.

Don't think that there's any causality here -- the two are completely
different.

Post by Markus Hutmacher
Here my question: what does KDE with the programs what FVWM does
not? is there an option I can use in the configuration? My
configuration is

As I say, it could be how the X11 events are being treated, but I'll
struggle to know for sure until I can reproduce it.

Since it seems to be working fine here for me, I'll try and rule out
anything in your config first, if you'll send that to me?

-- Thomas Adam

[Markus Hutmacher]

Hello Thomas,

thanks for the quick answer, I will build the 2.6.4-version at first and
try out if it works for me.

I forgot to mention, that when the qwit-window doesn't come up and I
kill the qwit-process and then again start the program, it still doesn't
work.

Well, I'll append my whole configuration to this mail, the configuration
for qwit is in "functions" and in "modules".

Markus

Post by Thomas Adam

Post by Markus Hutmacher
Hello,
I'm using FVWM-2.6.1 on Slackware64-current. I've installed qwit

At least try 2.6.4.

Post by Markus Hutmacher
(and also qtwitter) as Twitter-clients. Both are shown in
stalonetray and work as expected. But when I restart FVWM before
closing qwit, it is shown in stalonetray, but I cannot manage the
window to be shown. When I use the "show/hide" option at the icon in
stalonetray, the desktop is changed, but still no window. The same
is true for qtwitter, both (as the name says are qt-based. Exiting
FVWM and restarting doesn't work either.

* Click on systray icon -> Focus Window.
* Click again on systray icon -> is window mapped ? Hide : Show
It's entirely possible that through the systray icon, FVWM thinks the window
is in the WithDrawn state, or something, and is never mapped again because
of it.
I took a very quick look at this using qwit, and cannot reproduce your
problem.

Post by Markus Hutmacher
But when I start qwit or qtwitter in KDE and afterwards again in
FVWM, both work as expected.

Don't think that there's any causality here -- the two are completely
different.

Post by Markus Hutmacher
Here my question: what does KDE with the programs what FVWM does
not? is there an option I can use in the configuration? My
configuration is

As I say, it could be how the X11 events are being treated, but I'll
struggle to know for sure until I can reproduce it.
Since it seems to be working fine here for me, I'll try and rule out
anything in your config first, if you'll send that to me?
-- Thomas Adam

[Thomas Adam]

Post by Markus Hutmacher
Hello Thomas,
thanks for the quick answer, I will build the 2.6.4-version at first
and try out if it works for me.

Can you please make sure you don't top-post?

Post by Markus Hutmacher
I forgot to mention, that when the qwit-window doesn't come up and I
kill the qwit-process and then again start the program, it still
doesn't work.
Well, I'll append my whole configuration to this mail, the
configuration for qwit is in "functions" and in "modules".

Well, I still can't reproduce your problem, so at this point I might hazard
a guess it's a problem with either Qt or qwit. There's nothing I can do
until you can get me a more generic test case.

-- Thomas Adam

[Markus Hutmacher]

Post by Thomas Adam

Post by Markus Hutmacher
Hello Thomas,
thanks for the quick answer, I will build the 2.6.4-version at first
and try out if it works for me.

Can you please make sure you don't top-post?

Well, sorry

Post by Thomas Adam

Post by Markus Hutmacher
I forgot to mention, that when the qwit-window doesn't come up and I
kill the qwit-process and then again start the program, it still
doesn't work.
Well, I'll append my whole configuration to this mail, the
configuration for qwit is in "functions" and in "modules".

Well, I still can't reproduce your problem, so at this point I might hazard
a guess it's a problem with either Qt or qwit. There's nothing I can do
until you can get me a more generic test case.

Now I've built and installed fvwm-2.6.4 and it yet I can't reproduce the
problem as well.

I'll keep an eye on it and hope that that the problem is solved now.

Thanks for pointing me to the newest version.

Markus

Post by Thomas Adam
-- Thomas Adam