Re: Nautilus-Fvwm interaction
I read the bug referenced in the URL, and also the bugs that _that_ bug references, etc. It seems pretty clear that the Nautilus guy is a reasonable fellow, and he wants to do the right thing, but it also seems clear that he feels the ICCCM blesses the behavior he's using. As I understand it, he's trying to allow for drag'n'drop without focusing the originating window (that is, if you have a window without focus and you move the mouse over it (click to focus obviously) and click and drag something out of the window somewhere else, he _doesn't_ want that window to get focus in that case. Since no WM will do that normally, he wants to do his own focusing rather than let the WM do it. Personally I think that's a hell of a lot of extra work for a relatively minor feature, but there you go. He believes that the ICCCM allows that if you mark your window as WM_TAKE_FOCUS, then even if it's marked as not accepting input the WM should still send it a focus event. Then the code will assert focus, if appropriate. Here's a relevant passage from [EMAIL PROTECTED] in the response to bug #7823: http://bugzilla.eazel.com/show_bug.cgi?id=7823 My reading of the ICCCM is that if WM_HINTS.input is false, but WM_PROTOCOLS includes WM_TAKE_FOCUS, then the window manager should never focus the window itself - it should just send the window a WM_TAKE_FOCUS message If that's not the right way to interpret this combination (or anyway we don't _think_ it's the right way :), I think it would be good if folks here who understand the issues had a conversation with him explaining our interpretation, etc. If there is no meeting of the minds, so be it: we can add a note to the FAQ and/or some special new BugOpt for Nautilus, if that's reasonable, but at least everyone will understand everyone else's position. -- --- 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 URL: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: Nautilus-Fvwm interaction
On Thu, May 10, 2001 at 12:20:10AM -0400, Paul D. Smith wrote: Here's a relevant passage from [EMAIL PROTECTED] in the response to bug #7823: http://bugzilla.eazel.com/show_bug.cgi?id=7823 My reading of the ICCCM is that if WM_HINTS.input is false, but WM_PROTOCOLS includes WM_TAKE_FOCUS, then the window manager should never focus the window itself - it should just send the window a WM_TAKE_FOCUS message Hmm, my reading of ICCCM2 (finally took the time to find it) 4.1.7 agrees with their assessment. http://tronche.com/gui/x/icccm/sec-4.html#s-4.1.7 He's describing what ICCCM2 defines as Globally Active Input Model. Ick, but if that's what they want... -- [EMAIL PROTECTED]http://www.mikehan.com/ coffee achiever San Francisco, California Why do we still live here in this repulsive town? All our friends are in New York. Stephen Merritt -- Visit the official FVWM web page at URL: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: Patch to FvwmEvent to use hex
[EMAIL PROTECTED] wrote:
On 08 May 2001 14:34:54 +0100, Tim Phipps wrote:
Attached is a patch to make FvwmEvent pass the window-id in hex.
Maybe just pass a heximal id in PassId instead of additional PassHexId?
I think it is safe.
Fine by me, I didn't want to upset anyone. Attached is a patch to do it,
[de]windowshade now returns a window-id too.
Cheers,
Tim.Index: modules/ChangeLog
===
RCS file: /u/phippst/cvsroot/fvwm/modules/ChangeLog,v
retrieving revision 1.7
diff -u -r1.7 ChangeLog
--- modules/ChangeLog 2001/05/09 11:53:55 1.7
+++ modules/ChangeLog 2001/05/10 09:27:18
@@ -1,3 +1,7 @@
+2001-05-10 Hippo
+
+ * FvwmEvent/FvwmEvent.[c1]: PassId returns a hex number
+
2001-05-08 Mikhael Goikhman [EMAIL PROTECTED]
* FvwmCommand/FvwmCommand.c:
Index: modules/FvwmEvent/FvwmEvent.1
===
RCS file: /u/phippst/cvsroot/fvwm/modules/FvwmEvent/FvwmEvent.1,v
retrieving revision 1.1
diff -u -r1.1 FvwmEvent.1
--- modules/FvwmEvent/FvwmEvent.1 2001/05/08 10:48:02 1.1
+++ modules/FvwmEvent/FvwmEvent.1 2001/05/10 08:41:31
@@ -129,8 +129,8 @@
.IP *FvwmEventPassID
Specifies that the event action will have an ID parameter added to the end
of the command line. Most events will have the windowID of the window that the
-event refers to, new_desk will have the new desk number.
-
+event refers to, new_desk will have the new desk number. The windowID is a
+hexadecimal string preceded by 0x, desk numbers are decimal.
.IP *FvwmEvent \fIwindow-manager-event action-or-filename\fP
Binds particular actions to window manager events.
Index: modules/FvwmEvent/FvwmEvent.c
===
RCS file: /u/phippst/cvsroot/fvwm/modules/FvwmEvent/FvwmEvent.c,v
retrieving revision 1.1
diff -u -r1.1 FvwmEvent.c
--- modules/FvwmEvent/FvwmEvent.c 2001/05/08 10:48:02 1.1
+++ modules/FvwmEvent/FvwmEvent.c 2001/05/10 09:24:07
@@ -173,8 +173,8 @@
{ default_icon, -1 },
{ string, -1 },
{ mini_icon, -1 },
- { windowshade, -1 },
- { dewindowshade, -1 },
+ { windowshade, 0 },
+ { dewindowshade, 0 },
{ lockonsend, -1 },
{ sendconfig, -1 },
{ restack, -1 },
@@ -394,8 +394,14 @@
else
{
if(PassID (event_table[event].action_arg != -1))
- sprintf(buf,%s %s %ld, cmd_line, action_table[event],
- body[event_table[event].action_arg]);
+ {
+ if (M_NEW_DESK == (1 event))
+ sprintf(buf,%s %s %ld, cmd_line, action_table[event],
+ body[event_table[event].action_arg]);
+ else
+ sprintf(buf,%s %s 0x%lx, cmd_line, action_table[event],
+ body[event_table[event].action_arg]);
+ }
else
sprintf(buf,%s %s, cmd_line, action_table[event]);
INFO(buf);
Re: Wait in functions is broken
On Wed, May 09, 2001 at 11:12:26PM +, Mikhael Goikhman wrote: On 09 May 2001 01:48:44 +0200, Dominik Vogt wrote: On Tue, May 08, 2001 at 09:58:24PM +, Mikhael Goikhman wrote: I don't know when this started. AddToFunc TestFunction I Wait unexisting window TestFunction Now, click or drag using the mouse anywhere. Woops, mouse is mostly locked. The keyboard works well (did I say something similar before?), so you may quit this mode by pressing Ctrl-Alt-Escape. That's not really new. This was always the case if the function used anything else but 'I'. I don't know what to do about that. The pointer must be grabbed during function execution for the reasons I explained in the thread with Paul's deiconify problem. I think I see this thread and I can't find where is explained why the cursor grabbing is needed. From the ChangeLog: 2001-03-22 Dominik Vogt [EMAIL PROTECTED] * fvwm/functions.c (execute_complex_function): fixed button presses being passed to other applications with functions that only have immediate actions What is the date of the message you mention? I think I messed up the mails. This locked cursor behaviour is not good. Wait is mostly used in I functions. It is used in many places, including fvwm-themes, FVWM FAQ. No, it's not good at all. 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 URL: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: FvwmPager WindowColorsets not updating completely
On Wed, May 09, 2001 at 03:23:52PM -0500, An Thi-Nguyen Le wrote: Version: cvs (May 8th) I ran across something strange recently with FvwmPager. 1. Set up the pager like so, and *without* mini icons: *FvwmPagerWindowColorsets 1 2 *FvwmPagerSmallFont 5x7 2. Set up colorsets 1 and 2: *FvwmThemeColorset 1 fg white, bg lightblue, Pixmap *FvwmThemeColorset 2 fg lightblue, bg navy, Pixmap 3. Start up the pager any way you want. 4. Move around windows, focusing them, unfocusing them, and so on. All the colors should be right. 5. Now, change the colorsets: *FvwmThemeColorset 1 fg red, bg pink, Pixmap *FvwmThemeColorset 2 fg green, bg black, Pixmap 6. Move around the windows, focusing them, unfocusing them, and so on. On the current viewport, everything is obviously okay. 7. Now change the viewport (scroll left or right or up or down by 100%, or change desktops). 8. Now, change back to the original viewport. 9. Now move around the windows, focusing and unfocusing them. Result: The unfocus windows colorset foreground for the pager has fallen back to the previous version (e.g., no longer red, but white). I can confirm this. 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 URL: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: Nautilus-Fvwm interaction
On Wed, May 09, 2001 at 10:43:10PM -0700, Michael Han wrote: On Thu, May 10, 2001 at 12:20:10AM -0400, Paul D. Smith wrote: Here's a relevant passage from [EMAIL PROTECTED] in the response to bug #7823: http://bugzilla.eazel.com/show_bug.cgi?id=7823 My reading of the ICCCM is that if WM_HINTS.input is false, but WM_PROTOCOLS includes WM_TAKE_FOCUS, then the window manager should never focus the window itself - it should just send the window a WM_TAKE_FOCUS message Hmm, my reading of ICCCM2 (finally took the time to find it) 4.1.7 agrees with their assessment. http://tronche.com/gui/x/icccm/sec-4.html#s-4.1.7 He's describing what ICCCM2 defines as Globally Active Input Model. Ick, but if that's what they want... Yes, he's right. Fvwm does not handle the Globally Active input model correctly. 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 URL: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 domivogt: * Fixed Globally Active input model (untested).
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt01/05/10 05:46:54 Modified files: . : ChangeLog fvwm : focus.c Log message: * Fixed Globally Active input model (untested). -- Visit the official FVWM web page at URL: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: Nautilus-Fvwm interaction
On Wed, May 09, 2001 at 06:41:11PM +0200, Tomas Ogren wrote: Hello. If you use fvwm2 and run Nautilus, bad focus stuff happens.. You won't get any keyboard focus in the Nautilus window for instance. The Nautilus people says it's an fvwm bug.. If anyone with knowledge of WM hints and focus stuff could look at http://bugzilla.eazel.com/show_bug.cgi?id=8273 it would be great.. I made a patch, but I can't test this. If the patch works you may report this to the Nautilus people so that they can add a hint to their bug database. 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 URL: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: FvwmPager WindowColorsets not updating completely
On Thu, May 10, 2001 at 12:37:26PM +0200, fvwm-workers wrote: On Wed, May 09, 2001 at 03:23:52PM -0500, An Thi-Nguyen Le wrote: Version: cvs (May 8th) I ran across something strange recently with FvwmPager. 1. Set up the pager like so, and *without* mini icons: *FvwmPagerWindowColorsets 1 2 *FvwmPagerSmallFont 5x7 2. Set up colorsets 1 and 2: *FvwmThemeColorset 1 fg white, bg lightblue, Pixmap *FvwmThemeColorset 2 fg lightblue, bg navy, Pixmap 3. Start up the pager any way you want. 4. Move around windows, focusing them, unfocusing them, and so on. All the colors should be right. 5. Now, change the colorsets: *FvwmThemeColorset 1 fg red, bg pink, Pixmap *FvwmThemeColorset 2 fg green, bg black, Pixmap 6. Move around the windows, focusing them, unfocusing them, and so on. On the current viewport, everything is obviously okay. 7. Now change the viewport (scroll left or right or up or down by 100%, or change desktops). 8. Now, change back to the original viewport. 9. Now move around the windows, focusing and unfocusing them. Result: The unfocus windows colorset foreground for the pager has fallen back to the previous version (e.g., no longer red, but white). I can confirm this. Fixed. 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 URL: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 domivogt: * Fixed active icon change when window was not iconified.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt01/05/10 06:48:42 Modified files: . : ChangeLog fvwm : events.c fvwm.h icons.c window_flags.h modules: ChangeLog modules/FvwmPager: FvwmPager.c x_pager.c Log message: * Fixed active icon change when window was not iconified. -- Visit the official FVWM web page at URL: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 migo: * FAQ: added cvs info to the patch questions, as Andr� Dahlqvist suggested
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: migo01/05/10 09:00:33 Modified files: . : ChangeLog docs : ChangeLog FAQ fvwm : session.c modules: ChangeLog modules/FvwmPager: FvwmPager.c Log message: * FAQ: added cvs info to the patch questions, as André Dahlqvist suggested * session.c: increment state file version since window_flags was changed * FvwmPager.c: remove forgotten XSynchronize -- Visit the official FVWM web page at URL: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 migo fvwm-web: regenerated FAQ and NEWS
CVSROOT:/home/cvs/fvwm Module name:fvwm-web Changes by: migo01/05/10 09:12:29 Modified files: . : ChangeLog generated : FAQ.html NEWS.html Log message: regenerated FAQ and NEWS -- Visit the official FVWM web page at URL: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]
SetEnv not expanding environmental variables itself
Version: cvs (as of May 10 09:35:30 CDT 2001)
Maybe this is documented somewhere. Set up some environment stuff, like
so:
SetEnv fvwmdir ${HOME}/.fvwm
SetEnv bindir $fvwmdir/bin
'Exec echo blah' should fully expand these variables, then. However,
this happens:
Exec echo $fvwmdir
=== ${HOME}/.fvwm
Exec echo $bindir
=== $fvwmdir/bin
The second one should be something like maybe '${HOME}/.fvwm/bin'. Unless,
of course, SetEnv's not supposed to expand environment variables.
--
An Thi-Nguyen Le
|Beauty seldom recommends one woman to another.
--
Visit the official FVWM web page at URL: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: SetEnv not expanding environmental variables itself
[An Thi-Nguyen Le - Thu, 10 May 2001 09:50:34 AM CDT]
Version: cvs (as of May 10 09:35:30 CDT 2001)
Maybe this is documented somewhere. Set up some environment stuff, like
so:
SetEnv fvwmdir ${HOME}/.fvwm
SetEnv bindir $fvwmdir/bin
'Exec echo blah' should fully expand these variables, then. However,
this happens:
Exec echo $fvwmdir
=== ${HOME}/.fvwm
Exec echo $bindir
=== $fvwmdir/bin
The second one should be something like maybe '${HOME}/.fvwm/bin'. Unless,
of course, SetEnv's not supposed to expand environment variables.
Some more possibly strange things:
SetEnv fvwmdir ${HOME}/.fvwm
ImagePath /usr/share/icons
ImagePath +:$fvwmdir/pixmaps
doesn't work either. However, using
SetEnv fvwmdir /home/viper/.fvwm
*does* work.
--
An Thi-Nguyen Le
|It may be better to be a live jackal than a dead lion, but it is better
|still to be a live lion. And usually easier.
| -- Lazarus Long
--
Visit the official FVWM web page at URL: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: SetEnv not expanding environmental variables itself
An Thi-Nguyen Le [EMAIL PROTECTED] writes:
Version: cvs (as of May 10 09:35:30 CDT 2001)
Maybe this is documented somewhere. Set up some environment stuff, like
so:
SetEnv fvwmdir ${HOME}/.fvwm
SetEnv bindir $fvwmdir/bin
'Exec echo blah' should fully expand these variables, then. However,
this happens:
Exec echo $fvwmdir
=== ${HOME}/.fvwm
Exec echo $bindir
=== $fvwmdir/bin
The second one should be something like maybe '${HOME}/.fvwm/bin'. Unless,
of course, SetEnv's not supposed to expand environment variables.
Use the notation:
Exec echo $[bindir]
--
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 URL: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: SetEnv not expanding environmental variables itself
[Dan Espen - Thu, 10 May 2001 10:14:34 AM CDT] Use the notation: Exec echo $[bindir] Ah. Okay. Never mind... Embarassed... -- An Thi-Nguyen Le -- Visit the official FVWM web page at URL: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: SetEnv not expanding environmental variables itself
On 10 May 2001 09:49:41 -0500, An Thi-Nguyen Le wrote:
Maybe this is documented somewhere.
Yes, in the man page. Enter /environment and press 'n' several times.
You will find everything you wanted to know, including the fact that only
3 commands ImagePath, ModulePath and Restart expand environment variables
$var and ${var} themselves, and for other commands $[var] should be used.
Regards,
Mikhael.
--
Visit the official FVWM web page at URL: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]
