Re: FVWM: About swallowing asfsm
On 27 May 2001 20:15:08 +0200, Fabio Stumbo wrote: > > > I have no problems to swallow asfsm, works like with any other window. > > I used a usual (Swallow "asfsm" `Exec exec asfsm`). > > > > Please post your FvwmButtons config if you still have problems. > > Here is my config. Eventually I got it swallowed using the option > "UseOld", but I can't understand why: I just tried randomly... :-( [skipped] > *FvwmButtons: (2x2, Frame 4, Swallow(UseOld) "asfsm" `Exec asfsm \ > -bp None -bg rgb:4/6/4 -fg rgb:9/9/0 \ > -pbg rgb:4/6/4 -pfg rgb:f/f/0 -pbp None -i 60`) I see that in your example, without UseOld asfsm is not swallowed. This seems a problem of asfsm after all. :) The man page of asfsm suggests "-i sec" to change a scanning interval. But in fact, asfsm with -i starts iconic and immediately deiconifies itself. This confuses FvwmButtons. So either don't use -i or use UseOld or bother asfsm developers to conform to the man page or bother fvwm developers to fix swalowing. A note, if I don't use UseOld and then iconify/deiconify asfsm it is swallowed after this action. > > I can't get raise_window/lower_window events in FvwmEvent at all. > > Not using a module (FvwmTaskBar, FvwmConsole) not in any other way. > > > > It seems that lower_window event is not sent at all anywhere in the code. > > Probably someone else knows more about this. > > That's very strange: with 2.2.4 I had raise/lower working fine in any > case. Now (2.3.32) just the taskbar. Together with what you have, it > doesn't seem very deterministic, like a copmuter program should be... Don't underestimate a complexity of conditions in large programs. I can only add that I do get raise_window events when I enter gnome panel's subpanel, it asks (version 1.4) to raise itself when entered. I also sometimes enter a mode when usual RaiseLower or Raise generate raise_window. But right now they don't generate it while panel does. And lower_window is simply not sent as I already mentioned. I used for testing: *FvwmEvent-Test: Cmd "Exec xmessage" # "Echo" *FvwmEvent-Test: raise_window "raise window" Module FvwmEvent FvwmEvent-Test #KillModule FvwmEvent FvwmEvent-Test (I also currently have FvwmEvent-Sound with raise_window defined.) I don't consider any of the problems in this message critical for 2.4.0. They may be fixed later. Regards, Mikhael. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Notification: incoming/715
On 27 May 2001 22:03:16 +0200, Dominik Vogt wrote: > > On Sun, May 27, 2001 at 01:34:28PM -0500, An Thi-Nguyen Le wrote: > > [An Thi-Nguyen Le - Sun, 27 May 2001 01:32:43 PM CDT] > > > *FvwmColorset 8 fg blue, bg black, Pixmap > > > > > *FvwmColorset 8 fg red, bg white, Pixmap > > > > This even happens when I get the commands correct. :) > > > > *FvwmThemeColorset 8 fg blue, bg black, Pixmap > > *FvwmThemeColorset 8 fg red, bg white, Pixmap > > Neither command is correct ;-) FvwmTheme does not use new > > *FvwmTheme... > > config lines after it has already started. The correct syntax is > > SendToModule FvwmTheme Colorset ... Actually both syntaxes (module configuration and sending a message) work the same, i.e. fvwm and FvwmTheme are synchronized until FvwmTheme reevaluates the new colorset value. (Propogation of the new value to modules is not synchronized I guess.) And the first syntax is even preferable in most of situations, because after restarting (killing/starting) of FvwmTheme the current value is used. Regards, Mikhael. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: LDFLAGS or LD_OPTIONS or LDOPTS
%% Dan Espen <[EMAIL PROTECTED]> writes: de> Our INSTALL.fvwm file suggests that the user should export LDFLAGS de> on Solaris (for example). The Solaris man pages for Solaris 2.6 and de> 2.8 identify LD_OPTIONS as the right variable. de> HPUX11.11 uses LDOPTS. AIX 4.3 doesn't seem to have anything. de> Anyone know where LDFLAGS works? LDFLAGS is the variable used by the Makefile when invoking the linker. -- --- Paul D. Smith <[EMAIL PROTECTED]>HASMAT--HA Software Methods & Tools "Please remain calm...I may be mad, but I am a professional." --Mad Scientist --- These are my opinions---Nortel Networks takes no responsibility for them. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Notification: incoming/714
[Dominik Vogt - Mon, 28 May 2001 04:09:37 AM CDT] > > Message summary for PR#714 > > From: [EMAIL PROTECTED] > > Subject: Java 1.2/1.3 problems with initial window size > > Date: Tue, 22 May 2001 10:13:14 -0500 > > 0 replies 0 followups > > > > I noticed a problem that probably has its roots in bug report #664, > > and is demonstratable through Sun's beans development kit. This bug > > does not appear in any other window manager I've tried, ranging from > > the simple (flwm) to the complex (enlightenment), so it's odd that it > > pops up in fvwm. > > > > Instructions for reproducing: > > > > 1. Download the BDK from Sun. I can send you the original zip archive > >or a tar/gzipped archive. > > Whatever you mean with "BDK" (I could not find this name on the > Sun web page) I downloaded the Netbeans 3.2 executable > distribution. It has not makefile anywhere and dumps core when I > try to run it. All attempts to download the source distribution > ended in netscape crashes until now. I'm still trying. (Please > do *not* email the sources to me). I meant the 'Beans Development Kit', from www.java.com. For easy access, I am temporarily providing it at http://srh1171.urh.uiuc.edu/~anle/misc/bdk1_1.zip You need unzip. -- An Thi-Nguyen Le |FORTRAN is for pipe stress freaks and crystallography weenies. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: LDFLAGS or LD_OPTIONS or LDOPTS
"Dmitry Yu. Bolkhovityanov" <[EMAIL PROTECTED]> writes: > On 27 May 01 at 9:21, [EMAIL PROTECTED] wrote: > > Our INSTALL.fvwm file suggests that the user should export LDFLAGS > > on Solaris (for example). The Solaris man pages for Solaris 2.6 and > > 2.8 identify LD_OPTIONS as the right variable. > > HPUX11.11 uses LDOPTS. AIX 4.3 doesn't seem to have anything. > > > > Anyone know where LDFLAGS works? > > All the following supposes that you refer to Make I feel dumb. I was looking at ld options. LDFLAGS seems to be a standard part of make. Thanks, -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: [EMAIL PROTECTED] Piscataway, NJ 08854 Phone: (732) 699-5570 -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS dane: * INSTALL.fvwm: Identify LDFLAGS as a Makefile variable.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: dane01/05/28 07:26:54 Modified files: . : ChangeLog INSTALL.fvwm Log message: * INSTALL.fvwm: Identify LDFLAGS as a Makefile variable. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Focus and override redirect window
On Mon, May 28, 2001 at 11:11:44AM +0200, Olivier Chapuis wrote: > On Sunday 27 May 2001 20:37, you wrote: > > On Mon, May 07, 2001 at 11:37:09AM +0200, Olivier Chapuis wrote: > > > Hello, > > > I do not know if we have to take care of that now. > > > Moreover, this problem is maybe a bug of the applications > > > and not a FVWM bug (I do not know). > > > Here the problem. > > > Say that we have a NeverFocus window A and a window B with the > > > focus (say SloppyFocus and ClickToFocusClickRaise). > > > Now if I pop up (and pop down) a menu of the window A (override > > > redirect), then some times: > > >(i) window B lost the keyboard input (always happen if A is a qt app) > > >(ii) I cannot raise window B by clicking inside it (tested with > > > Xemacs) > > > > I tried this out and can reproduce (ii) (fixed) but not (i). I > > tried with kedit, kfm, kmag and xterm for window A and FvwmConsole > > and xemacs for window B. I opened various menus of A, but I never > > saw any problem with the focus. I started testing this thoroughly > > only after I wrote the fix for (ii), so the problem may have gone > > away in the wake of the patch, but I don't believe it. Can you > > give more details? > > I can confirm that (ii) is fixed. (i) is still here. I will try to give more > explaination on > (i) (however, I really do not think that this is a critical bug): > > Reproduction: - Style "kedit" NeverFocus > - start kedit and an xterm > - give the focus to the xterm (say the xterm is > SloppyFocus ) > - go to the kedit window (the xterm have still the focus) > - Popup the file menu and cancel it by a click somewhere > (on the > root window or on kedit or on the xterm). > - Then, the xterm is still decorated as a window with > the focus, but > the xterm has no more the keyborad focus. No, I have no problem at all, even with your instructions. > So that the xterm get again the keyboard focus I need to give the focus to an > other window > and come back to the xterm. In fact, kedit (or the kedit menu?) take the > keyboard focus > when I popup the file menu so that the arrows key can be used for menu > navigation. > > Maybe an important point is that I used KDE version 2 (2.1.1) with QT 2.3.0. - Qt version 2.2.3 - Kde 2.0.1 Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Focus and override redirect window
On Sunday 27 May 2001 20:37, you wrote: > On Mon, May 07, 2001 at 11:37:09AM +0200, Olivier Chapuis wrote: > > Hello, > > I do not know if we have to take care of that now. > > Moreover, this problem is maybe a bug of the applications > > and not a FVWM bug (I do not know). > > Here the problem. > > Say that we have a NeverFocus window A and a window B with the > > focus (say SloppyFocus and ClickToFocusClickRaise). > > Now if I pop up (and pop down) a menu of the window A (override > > redirect), then some times: > >(i) window B lost the keyboard input (always happen if A is a qt app) > >(ii) I cannot raise window B by clicking inside it (tested with > > Xemacs) > > I tried this out and can reproduce (ii) (fixed) but not (i). I > tried with kedit, kfm, kmag and xterm for window A and FvwmConsole > and xemacs for window B. I opened various menus of A, but I never > saw any problem with the focus. I started testing this thoroughly > only after I wrote the fix for (ii), so the problem may have gone > away in the wake of the patch, but I don't believe it. Can you > give more details? > I can confirm that (ii) is fixed. (i) is still here. I will try to give more explaination on (i) (however, I really do not think that this is a critical bug): Reproduction: - Style "kedit" NeverFocus - start kedit and an xterm - give the focus to the xterm (say the xterm is SloppyFocus ) - go to the kedit window (the xterm have still the focus) - Popup the file menu and cancel it by a click somewhere (on the root window or on kedit or on the xterm). - Then, the xterm is still decorated as a window with the focus, but the xterm has no more the keyborad focus. So that the xterm get again the keyboard focus I need to give the focus to an other window and come back to the xterm. In fact, kedit (or the kedit menu?) take the keyboard focus when I popup the file menu so that the arrows key can be used for menu navigation. Maybe an important point is that I used KDE version 2 (2.1.1) with QT 2.3.0. Also there is a QT option --nograb (say to do not grab the keyboard and the mouse), but this change nothing to the problem. Really, I think this is not a critical bug at all: who want to use kedit with a NeverFocus style? The only K apps which may need a NeverFocus policy are apps as kicker (kpanel KDE version 2 analogue) or kpager which do not work with FVWM. So this is a fvwm-ewmh problem and not a FVWM problem and if you do not see an obvious solution I think you do not have to lost your time with this. When I will have some time I will take a look on this problem, but I think we can safelly release 2.4.0 whithout a fix to this. Olivier -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Notification: incoming/714
On Tue, May 22, 2001 at 10:13:21AM -0500, fvwm-bug wrote: > FVWM Bug Tracking notification > > new message incoming/714 > > Message summary for PR#714 > From: [EMAIL PROTECTED] > Subject: Java 1.2/1.3 problems with initial window size > Date: Tue, 22 May 2001 10:13:14 -0500 > 0 replies 0 followups > > I noticed a problem that probably has its roots in bug report #664, > and is demonstratable through Sun's beans development kit. This bug > does not appear in any other window manager I've tried, ranging from > the simple (flwm) to the complex (enlightenment), so it's odd that it > pops up in fvwm. > > Instructions for reproducing: > > 1. Download the BDK from Sun. I can send you the original zip archive >or a tar/gzipped archive. Whatever you mean with "BDK" (I could not find this name on the Sun web page) I downloaded the Netbeans 3.2 executable distribution. It has not makefile anywhere and dumps core when I try to run it. All attempts to download the source distribution ended in netscape crashes until now. I'm still trying. (Please do *not* email the sources to me). Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
