numberOfFastPopups = 2;
}
char *safeSleep = getenv("SAFESLEEPNS");
if (safeSleep != NULL)
{
char *end;
safeSleepTimens = strtol(safeSleep,&end,10);
}
else
{
safeSleepTimens = -1;
}
safeSleepTimens = 0;
XtRealizeWidget(topLevel);
// records = fopen("/tmp/mapStats",&
-urNp fvwm.orig/ChangeLog fvwm.cvs/ChangeLog
--- fvwm.orig/ChangeLog 2010-02-25 05:28:44.0 -0600
+++ fvwm.cvs/ChangeLog 2010-02-25 06:11:19.0 -0600
@@ -1,3 +1,16 @@
+2010-02-25 Rich Coe
+ * fvwm/add_window.c
+ * fvwm/externs.h
+ * fvwm/fvwm.c
+ * fvwm/ic
On Wed, 13 Jan 2010 23:03:14 +
Thomas Adam wrote:
> On Wed, Jan 13, 2010 at 01:41:21PM -0600, Rich Coe wrote:
> > This patch implements a message to modules when an application
> > changes layers. It is one property of a window that isn't broadcast
> > when modif
geLog 2010-02-25 05:28:44.0 -0600
+++ fvwm.cvs/ChangeLog 2010-02-25 06:23:48.0 -0600
@@ -1,3 +1,12 @@
+2010-02-25 Rich Coe
+ * libs/Module.h
+ * fvwm/stack.c
+
+ This patch implements a message to modules when an application
+ changes layers. It is one proper
This patch implements a message to modules when an application
changes layers. It is one property of a window that isn't broadcast
when modified.
Please apply this patch.
(diff from recent cvs checkout)
Thanks,
Rich
diff -urNp fvwm.orig/fvwm/stack.c fvwm.cvs/fvwm/stack.c
--- fvwm.orig/fvwm/sta
This patch fixes a problem with recently unmapped windows.
If fvwm receives a message from a module to modify a window which FVWM
has un-mapped, it does honor the request in the module message.
This only affects window id's which are sent as a request from a module.
Rich
diff -urNp fvwm.orig/fvw
while FvwmSocket is busy.
+
+.SH COPYRIGHTS
+The FvwmSocket program, and the concept for interfacing this
+module to the Window Manager, are all original work by Rich Coe.
+Inspired by a prototype written in perl using named pipes by Alan Buchanan.
+
+Copyright 2005, Rich Coe. No guarantees o
On Sat, 2 Jan 2010 15:50:48 +
Thomas Adam wrote:
> All,
>
> Are there any outstanding bug-fixes which haven't yet been looked into, but
> were at one point reported to this list? I've trawled through my own
> archives and fixed as many of them as I could find recently -- but there may
> well
On Tue, 5 Feb 2008 13:33:37 +0100
Dominik Vogt <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 05, 2008 at 05:50:00AM -0600, Rich Coe wrote:
> > This patch fixes a problem with recently un-mapped windows.
>
> You can't do it this way. There is no guarantee that the stored
This patch implements a message to modules when an application
changes layers. It is one property of a window that isn't broadcast
when modified.
Please apply this patch.
Rich
diff -urNp fvwm-2.5.24/fvwm/stack.c fvwm/fvwm/stack.c
--- fvwm-2.5.24/fvwm/stack.c2007-08-07 15:17:43.0 -05
This patch fixes a problem with recently un-mapped windows. If a program
issues a window request to fvwm and that window has un-mapped itself, fvwm
prompts the user with a 'cross-hairs' mouse icon to select the window target
for the command. In all cases the user will have no idea what is going o
ket will check during writing
+to the listeners that Fvwm is serviced should Fvwm make any more data
+available while FvwmSocket is busy.
+
+.SH COPYRIGHTS
+The FvwmSocket program, and the concept for interfacing this
+module to the Window Manager, are all original work by Rich Coe.
+Inspired by a
new_layer(fw, Scr.DefaultLayer);
}
+ /* layer > BottomLayer layer == BottomLayer
+ * CMD
+* STATE_ADDnew_layer(BOTTOM) do nothing
+* STATE_TOGGLE new_layer(BOTTOM) new_l
13 matches
Mail list logo
