On Thu, Jan 05, 2012 at 12:10:14PM +0100, Michael Großer wrote:
> Does anyone know about this behaviour of FvwmIdent?
> Is the reason known why FvwmIdent is that much damageable?
It's designed to work this way.
Look at the code:
case KeyRelease:
if (is_key_pressed)
{
exit(0);
}
break;
If you press a key, and FvwmIdent is focused, we exit.
case ButtonRelease:
if (is_button_pressed)
{
if (is_button_pressed == 2 &&
Event.xbutton.button == 2)
{
/* select a new window when
* button 2 is pressed */
SetMessageMask(
fd, M_CONFIGURE_WINDOW |
M_WINDOW_NAME |
M_ICON_NAME |
M_RES_CLASS |
M_RES_NAME |
M_END_WINDOWLIST |
M_CONFIG_INFO |
M_END_CONFIG_INFO|
M_SENDCONFIG);
SendText(fd, "Send_WindowList", 0);
XDestroyWindow(dpy, main_win);
If button two is pressed, we destroy the top-level window, and prompt for a new
window to select.
DestroyList();
fvwmlib_get_target_window(
dpy, screen, module->name,
&(module->window), True);
found = 0;
return 1;
}
else
{
exit(0);
Otherwise, all other button processes close FvwmIdent.
-- Thomas Adam
