Hi Thomas,
> (I have no doubt if we get this right,
> FvwmIconMan might follow, since this has an applicable use for balloons also.)
I got the impression from Olivier's post a while back that there is already
such a patch for FvwmIconMan.
http://thread.gmane.org/gmane.comp.window-managers.fvwm.d
> ThisWindow (thomas_adam) Wait godo :)
Ah, that was supposed to be "godot".
Scott. :)
Hi Thomas,
> I noticed earlier that there is a discrepency in the FVWM manpage (2.5.X
> series is the only one to be fixed) for the Wait command description. The
> description says initially that the command waits of "windowname". This is
> parly true -- the code in builtins.c apparently also c
Hi all,
Help please.
addtofunc fn
+ i echo executing $[0-]
+ i $[0-]
fn echo hello
How come fn doesn't print out "hello"?
Scott. :)
> > I think there is a bug in FVWM's parameter expansion.
> > FVWM crashes with a simple command such as:
> >
> > Echo $[0]
>
> Is this supposed to be fixed? FVWM still crashes on my system
> when I type "Echo $[0]" in FvwmConsole.
__eae_parse_range() is screwy:
sscanf(input, "%u-%n", ...
ret
> I think there is a bug in FVWM's parameter expansion.
> FVWM crashes with a simple command such as:
>
> Echo $[0]
Is this supposed to be fixed? FVWM still crashes on my system
when I type "Echo $[0]" in FvwmConsole.
I am using current version of CVS.
Scott.
Damn this list is busy!
http://gmane.org/plot-rate.php?group=gmane.comp.window-managers.fvwm.devel&width=1000&height=400&color=red,orange,%234000&title=fvwm-workers&smooth=exp
Not that I'm complaining.
Scott. :)
Hi David,
> > > I'm trying to find out how to have multiple windows sharing the same
> > > frame.
> > > I'm playing with FvwmTabs but I also want to experiment with a simpler
> > > implementation on my own.
> >
> > Simpler? H.
> >
> I just want to get four functions working - add, next, clo
Hi all,
I think there is a bug in FVWM's parameter expansion.
FVWM crashes with a simple command such as:
Echo $[0]
I am looking at this problem in GDB. The variable 'm', suddenly has a
huge value when I reach line 918 of fvwm/expand.c:
if (input[m] == ']')
Then I get a SEGV because this is an
Hi Serge,
> In question 7.17 of the FVWM FAQ "Autohiding FvwmButtons or other
> windows" module FvwmAuto launched like this:
>
> + I Module FvwmAuto FvwmAutohide -menter enter_handler
>
> But from reading manpage & source code of this module I figured out that
> it doesn't accept aliases, right?
Hi David,
> I'm trying to find out how to have multiple windows sharing the same frame.
> I'm playing with FvwmTabs but I also want to experiment with a simpler
> implementation on my own.
Simpler? H.
> I wrote something like the following in the main
> fvwm code.
>
> Add tab: (client is th
Hi Dominik,
> Some hints for using the parsing functions
Thanks.
I think they are useful, so I added them as comments to the source code.
(slightly modified)
By the way, I notice that entries in ChangeLog appear not to be in
chronological order. I always use the local date - I assume that's ok?
Hi Renato,
> >The attached patch fixes the broken KillModule command.
> >Can someone please apply it?
> >
> Done. How long was it broken?
Not long. Since 2006/06/24.
By the way, I've long wanted to know the significance of
"seventh guardian" ... ?
SCoTT. :)
Hi Dominik,
> Can you have multiple peridic commands or just one?
Multiple.
> I suggest to replace the command "Periodic" with some option to the Schedule
> command
The current specification for Schedule is:
Schedule delay_ms [command_id] command
So, would something like the following do?
Sc
Hi all,
Here is a proposed patch to add a new builtin function, Periodic.
http://members.optusnet.com.au/scottsmedley/fvwm/periodic.patch
Apply with: patch -p0 < periodic.patch
It is similar to the Schedule builtin except the function is invoked
every N milliseconds - even if a grab fails, or t
Hi Mikhael,
> Well, years ago I suggested to make "I" specifier optional in functions,
> because 90% of functions are immediate and there is no confusion if "I"
> is omitted. But there was no agreement.
You would have had my vote! :)
Do you have a URL so I could read up on the discussion?
> I
Hi Oliver,
> - Try to grab just 2 times (this is really fast). If the grab succeed
> everything is ok. If it fails execute the function any way.
If you're happy to execute a function even if a grab fails, why go
to the trouble of grabbing in the first place? Why not just mark
your function "NoGra
Hi Dominik,
> Well, it has all been discussed in that old thread.
Many of the issues surrounding how _FVWM_ might detect if a function
needs to grab or not have been discussed, & I agree with you - it's
going to be very, very difficult ... at best.
However, I feel that Dan's idea (to allow the
Just to clarify ...
> In my opinion, it's not Schedule that is broken/unreliable. _Any_
> function may fail to execute if the pointer is grabbed for ~1 second
> at the time of execution.
It doesn't matter if a function is invoked by Schedule or not - it
can still fail to execute in either case.
Hi Mikhael,
> > DefineFunc would behave much like AddToFunc except for 3 differences:
> > 1. It would generate a warning message if the function already existed.
>
> This is bad. Configs should usually be re-read-able. Instead, it should
> silently apply DestroyFunc. In fact, DefineFunc (combinin
Hi Dominik et al,
This post follows on from the previous "ModuleListenOnly command"
which was getting a bit off-topic.
> > As a hack/compromise, maybe we could modify AddToFunc to keep track
> > of whether or not it uses a "mouse modifier" & only then grab the
> > X server, in execute_complex_fu
Hi Dominik,
> That's just one purpose of the command. I was always fond of the
> idea to prototype or even implement modules as shell scripts.
Yes, that would be cool. IMHO, I think it would be prudent to create
"bashlib" (akin to perllib), instead of adding ModuleListenOnly command.
But I sup
Hi Dominik,
Are you enjoying the World Cup?
> Two reasons: (1) "Schedule" is an unreliable hack and (2) this
> starts a shell every 15 seconds and my goal was to waste as little
> cpu as possible (as it interferes with certain time-critical
> applications - okay - games).
Hehe. :)
Re: (2)
>Fr
> + I PipeRead 'str=$(/bin/ps -A --format "%C %P %c" | sort -n -r | tail -n1)
Sorry, that should be 'head', of course. (or drop the '-r' flag on 'sort'.)
SCoTT. :)
Hi Dominik & Mikhael,
> We may write a module FvwmButtonsUpdater that gets an FvwmButtons module
> name (alias) and a list of entries, each is: a button id, its update
> frequency and a shell command to invoke for title updates (for example,
> 'date +%T' or 'ps -A --format "%C %P %c" | sort -n -r
Hi all,
An updated version of my if-syntax patch that applies cleanly against
current CVS is available at:
http://members.optusnet.com.au/scottsmedley/fvwm/if.20060609.patch
Example usage:
http://members.optusnet.com.au/scottsmedley/fvwm/if.example
All feedback welcome.
SCoTT. :)
Hi David,
> I've created a patchset[1] to try to improve the way fvwm looks.
Who wrote each of these patches?
I just created an updated version of the RoundedCorners patch that applies
cleanly against current CVS, for anyone who wishes to try it (without
requiring all the other patches on your s
> But running a quick make distcheck yields...
>
> Making all in FvwmTabs
> make[4]: Entering directory
> `/home/awol/cvs/fvwm/fvwm-2.5.15/_build/modules/FvwmTabs'
> make[4]: *** No rule to make target `FvwmTabs.pod', needed by
> `FvwmTabs.1'. Stop.
Thanks, fixed.
> Now make dist works fine b
Hi Lars,
As described on your website http://www.gmane.org/import.php I'd like
to update 2 FVWM mailing lists hosted on Gmane with the FULL archive.
The 2 Gmane FVWM mailing lists are:
http://news.gmane.org/gmane.comp.window-managers.fvwm.devel
http://news.gmane.org/gmane.comp.window-managers.fv
It would be very useful to have a decent mailing list archive for FVWM.
The FVWM homepage has a "Workers Mailing List Archive" link which
points to:
http://www.mail-archive.com/fvwm-workers@fvwm.org/
Which appears to have a VERY SMALL subset of posts.
This link:
http://www.mail-archive.com/f
> i find that it's a pity that there isn't a simple and
> useful behavior of FvwmTabs like in Fluxbox.
> Indeed, in Fluxbox you just have to move the title bar of a window to
> another one and the two titlebar are one.
I've never used Fluxbox but from what you say it sounds like the
drag-&-drop
> "As you can see by the weather report, there are some baloons over the
> usa/canada and the north of europe. One guy caught some wind and ended
> up on australia though.." LOL
Yeah, it's a bit lonely in my solitary balloon over here. :)
> I hope I can join you soon in my baloon
> :) I'll be ov
Hi all,
Before the end of this month my personal website which hosts
the FvwmTabs module & associated documentation will be shutdown.
A while back there was some talk about including the FvwmTabs
module as part of the Fvwm distribution. Are people still happy
for this to happen?
If not, I can up
Hi Evgeny,
> PS. Is there a working archive of this mailing list? The one pointed to
> from the FVWM home lags months behind.
Some of us use gmane:
http://news.gmane.org/gmane.comp.window-managers.fvwm.devel
http://news.gmane.org/gmane.comp.window-managers.fvwm
SCoTT. :)
Is there anything we can do about the amount of SPAM in the
FVWM bug tracking system?
Every few months I end up moving hundreds of SPAM from "incoming"
to "trash". The volume is increasing significantly.
SCoTT. :)
Hi Mikhael, :)
> But then we had another similar "If" patch by Scott, IIRC.
Yes, see:
http://article.gmane.org/gmane.comp.window-managers.fvwm.devel/1026
The plan was to wait until 2.6 - I didn't think it would be such a
long wait however! :)
What's the current status of the 2.6 release anyway
Hi all,
Is anyone running a recent version of FVWM on Fedora Core 3?
I compiled 2.5.12 & CVS versions from source last night on a
fresh FC3 install & it hung consistently (using default config).
Didn't have much chance to investigate other than a few stack traces:
(gdb) where
#0 0x008dc7a2 in
Hi Uwe, :)
> I would mostly use it for statemente like
>
> AddToMenu my_menu
> if ! ShellCmd /opt/myprogram
> + "My Program menu" Menu my_program_menu
> endif
>
> This should be possible.?
Yup, it works no problem.
SCoTT. :)
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To uns
Hi all,
Someone recently asked me about the status of if-syntax in Fvwm. This
inspired me to readdress an earlier patch I wrote (which was somewhat
limited in scope & a bit buggy) to identify the issues & hack up a robust
implementation.
This new patch:
- ensures there are no race conditions b/w
Does anyone happen to know the status of the work that was proposed
in this thread?
http://www.hpc.uh.edu/fvwm/archive/0409/msg00094.html
SCoTT. :)
--
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
Hi Dominik, :)
After revision 1.61 of libs/Parse.c, DoPeekToken() is behaving very
oddly. Best illustrated with an example:
If I pass a string, say, "2.5.13" to DoPeekToken() with delimiters ".",
I get back the token "2" (correct) but the pointer to the rest of the
string (the actual return value
Hi Dominik,
> I'd like to remove the current implementation of FvwmCommand
> because its signal and pipe handling is fundamentally flawed. Too
> often, a lock file of the FvwmCommand executable is left in
> /var/tmp although it's already dead.
Can we use atexit(close_fifos)? (Lemme guess, not po
> > o I am writing a fvwm perl module and anticipate wanting to parse the
> > o window_flags data upon receiving each M_ADD_WINDOW event
> The proper solution is to serialize the flags without dumping C
> structures. Here is a discussion:
> http://www.hpc.uh.edu/fvwm/archive/0407/msg00186.html
L
Hi all,
The current version of FVWM in CVS seg faults on my Xinerama system:
Program received signal SIGSEGV, Segmentation fault.
0x080b6804 in FScreenInit (dpy=0x2b8300) at FScreen.c:444
444 memcpy(screens_xi + 1, info,
(gdb) p info
$1 = (XineramaScreenInfo *) 0x0
It works f
> The very last line of all the
> man pages (with the notable exception of fvwm.1) appears to have an arbitary
> date (hardcoded from the source man page).
I just commited a patch to parse all man pages through config.status.
This involved renaming most *.1 files to *.1.in. Several man pages
app
> > Create FvwmButtons.1.in, a Makefile entry & run it through config.status?
> > (like the fvwm.1 man page)
I'm having trouble determining the configuration (in fvwm/Makefile.am?)
that creates this target in fvwm/Makefile.in:
fvwm.1: $(top_builddir)/config.status fvwm.1.in
cd $(top_builddir
Hi Dominik, :)
> I don't think the event is wrong. When a complex function is
> executed, fvwm grabs the pointer.
Ah! I see.
> FvwmButtons handles LeaveNotify events only, so the final
> LeaveNotify unhilights the button. I've committed a fix.
>
> Also, drawing of panel buttons was wrong duri
Hi Dominik, :)
> It seems to happen only if a function is called, not with plain
> commands. Try
>
> DestroyFunc foo
> AddToFunc foo I nop
> DestroyModuleConfig FvwmButtons*
> *FvwmButtons: ActiveColorset 2
> *FvwmButtons(Title foo, Action foo)
> Module FvwmButtons
This is a bizarre
Hi Dominik, :)
> You misunderstood me. In short, when I said "click" I meant press
> + release. Try this:
>
> - Use an ActiveColorset. It does not matter whether you use the
> PressedColorset too.
> - Move the mouse over a pressable button to hilight it. Don't
> move any more duri
Hi Dominik, :)
> > When I click on any button, it ends up using the
> > standard colour set until the mous is moved. That has nothing to
> > do with the PressedColorset.
I can't reproduce this.
I'm using an ActiveColorset, doing a buttonpress on a button which gets
displayed using the standard
Hi Dominik,
> When I click on any button, it ends up using the
> standard colour set until the mous is moved. That has nothing to
> do with the PressedColorset.
Ok, this must be a bug - I will check/fix tonight.
> Another problem that is going to become worse in the future is
> code that is cor
Hi Dominik,
> > > Currently, the Active{Colorset,Title,Icon} are used. If none are
> > > specified then Colorset, Title & Icon are used. The effect you
> > > describe is achievable by setting PressColorset to the same colorset
> > > as your ActiveColorset (formerly HoverColorset). I'm undecided if
> > > 1 When you click a button, it is drawn in the original colours as
> > >long as the mouse button is held. Shouldn't it also use the
> > >HoverColorset?
>
> Currently, the Active{Colorset,Title,Icon} are used. If none are
> specified then Colorset, Title & Icon are used. The effect y
> But the option "Pixmap none" don't work properly, ie it doesn't have
> a transparent background as expected.
Still TODO.
The way transparency is implemented with "Pixmap none" is a bit hacky (IMO),
especially when we're moving toward Colorsets. But I s'pose it should
be backwards-compatible ...
Hi all,
> > 1 When you click a button, it is drawn in the original colours as
> >long as the mouse button is held. Shouldn't it also use the
> >HoverColorset?
Currently, the Active{Colorset,Title,Icon} are used. If none are
specified then Colorset, Title & Icon are used. The effect you
Hi Mikhael, :)
> Ok, I have implemented the generic looped args support, so M_RESTACK
> is now fully supported.
Thank-you muchly!
One problem: I'm running a simple module & get this error:
Internal error, event type 1 (11 names, 7 values)
Also FVWM::Window::dump in WindowList.pm looks
> * fvwm.1: always use commas between conditions
I checked this. It doesn't appear to be mandatory.
ie.
All ("xterm", Iconic) Echo w is $[w.name]
All ("xterm" Iconic) Echo w is $[w.name]
both of the above appear to give the same results.
Is that a bug?
SCoTT.
--
Visit the official FVWM web pa
> > Committed patch by Norman Yarvin (with a few minor mods) to extend
> > conditionals to handle multiple window names.
>
> Hm, I did not expect this to be committed with the option naming
> issue unresolved
I was not aware of this issue. This is the first post I've seen
discussing it. I saw Mik
I just got confused by the FVWM man pages. The very last line of all the
man pages (with the notable exception of fvwm.1) appears to have an arbitary
date (hardcoded from the source man page).
For example, the FvwmButtons man page from the 2.5.10 release has this line:
3rd Berkeley Distribution
> > * Please put single statements in loops or if clauses in curly
> >braces, i.e.
> >
> > if (1)
> > {
> >foo;
> > }
> >
> >not
> >
> > if (1)
> >foo;
>
> What's the rationale behind this? I must confess I'm not particularly fond
> of this restricti
Hi Dominik, :)
> To avoid problems with comiling / reading the fvwm sources, please
>
> * adhere to the ANSI-C 88 standard, not the new one.
>Specifically,
>
> - Don't use C++-like comments with //
> - Declare variables only at the beginning of a block.
>
> * limit your lines to 7
Hi Norman,
> About a month ago, I sent in a patch to allow multiple window names in
> conditions.
I think being able to specify multiple windows in conditions is very
useful.
It's 2:30am ... let me see if I understand your patch correctly:
If you have:
Next (mozilla dillo netscape) Function ..
> > automake creates a bunch of system-dependent soft-links:
> >
> > depcomp -> /usr/share/automake-1.7/depcomp*
> > install-sh -> /usr/share/automake-1.7/install-sh*
> > missing -> /usr/share/automake-1.7/missing*
> > mkinstalldirs -> /usr/share/automake-1.7/mkinstalldirs*
> >
> > When I ./confi
Hi Mikhael, :)
> Out of tree builds should work. If not, then it is a bug.
>
> For example, this should work:
>
> cd /nfs/cvs/fvwm
> aclocal
> autoheader
> automake -a
> autoconf
>
> cd /build/mysystem
> /nfs/cvs/fvwm/configure [params]
> make
> make install
>
> Just tried th
Is it possible to build FVWM in separate directories?
ie. a bit like how GCC is built.
I'd like to have a NFS-mounted directory with CVS source code
& then build it for several systems.
SCoTT. :)
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list, send "un
Hi Piotr,
> Piotr> use FakeClick to intercept clicks in some windows, and pass the
> Piotr> click to the others ...
>
> Scott> The correct way to do this now is with a window-specific binding. ie.
>
> Scott> Mouse (rxvt) 1 A N Echo "mouse1-in-rxvt"
> Scott> Mouse (xterm) 1 A N Echo "mouse1-in-xt
Hmmm, I thought specifying fvwm-workers@fvwm.org in the notification
list (of the fvwm-bug website) would ensure this note got sent to the
list - obviously not:
> use FakeClick to intercept clicks in
> some windows, and pass the click to
> the others ...
The correct way to do this now is with a
> > > You may go to http://www.fvwm.org/cgi-bin/fvwm-bug.private (password
> > > needed) and manage bugs.
> >
> > Username 'scott' & my CVS password don't appear to work.
> >
> > Who should I see about this? Jason?
>
> You don't appear in the pull down list of people with access.
> I think you n
> You may go to http://www.fvwm.org/cgi-bin/fvwm-bug.private (password
> needed) and manage bugs.
Username 'scott' & my CVS password don't appear to work.
Who should I see about this? Jason?
SCoTT. :)
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list, se
Hi Mikhael,
What needs to be done for items E.11, E.12 & E.15 in docs/todo-2.6?
Oh! I just noticed item F.1! :)
SCoTT. :)
--
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 r
Hi Mikhael & Dominik, :)
Dominik says:
: > The default config for FVWM is (IMO) yuk!
: You obviously never took a look at sample.fvwmrc/system.fvwm2rc
Perhaps my definition of "default config" is wrong. To me, this is
an example .fvwm2rc file that users have to explicitly copy to
~/.fvwm/config
Hi all,
The default config for FVWM is (IMO) yuk!
I propose we update it to actually make it usable & also to make it a
little more aesthetically pleasing.
As an initial step, find attached a .fvwm2rc file. This syntax could
be added to ConfigFvwmDefaults (& SetRCDefaults() in fvwm.c potentially
Hi Liu,
: Stroke behave strangely, the latest stroke sequence overrides
: all previous stroke sequences.
Ok, fixed.
Please email future bug reports to the fvwm-workers list, not the
fvwm list. Most subscribers to the fvwm list aren't interested in
bug reports.
Thanks for testing. :)
SCoTT. :)
> : - Key binding in the Root context won't work, for example
> : Key F1 RMExec exec rxvt
> : it won't start rxvt but pop up the default menu instead.
> : - StrokeFunc in the Root crashes X, for example:
> : Mouse 1 RNStrokeFunc DrawMotion FeedBack StrokeWid
: > So the question is: what's changed?
: >
: > The binding list used to use the _earliest_ matching binding. The
: > current implementation uses the _latest_ matching binding. It would be
: > trivial to make it utilise the _earliest_ binding, however I am undecided
: > if this is really the behav
Note: this thread moved to fvwm-workers list.
: - Key binding in the Root context won't work, for example
: Key F1 RMExec exec rxvt
: it won't start rxvt but pop up the default menu instead.
: - StrokeFunc in the Root crashes X, for example:
: Mouse 1 RNSt
Hi Dominik,
: I think we should give CVS write access to Scott. Anybody to
: second that opinion?
Can I vote? :)
: (To Scott: I know I promised to look more closely at the window
: specific key bindings patch, but I just don't find the time to do
: it since I became a freelancer. I think the
/cvs/fvwm/fvwm/modules/ChangeLog,v
retrieving revision 1.1110
diff -u -r1.1110 ChangeLog
--- modules/ChangeLog 1 Jun 2004 11:46:54 - 1.1110
+++ modules/ChangeLog 2 Jun 2004 11:28:48 -
@@ -1,3 +1,10 @@
+2004-06-01 Scott Smedley <[EMAIL PROTECTED]>
+
+ * Fvwm
Hi all,
FvwmCommand currently misbehaves if it receives a sigPIPE. Of
particular annoyance, it leaves a FIFO hanging around which means that
subsequent invocations of FvwmCommand fail.
This patch makes FvwmCommand behave much more nicely.
SCoTT. :)
Index: FvwmCommand.c
==
> > Some apps (for example GVim) appear to have their own icons built in &
> > I'm wondering if there's a way to access them somehow? (through the
> > perllib interface of course)
> >
> > Using the WindowList tracker, M_MINI_ICON events have the value
> > "ewmh_mini_icon" for the name/mini_icon_na
Hi Mikhael,
A question for you:
Some apps (for example GVim) appear to have their own icons built in &
I'm wondering if there's a way to access them somehow? (through the
perllib interface of course)
Using the WindowList tracker, M_MINI_ICON events have the value
"ewmh_mini_icon" for the name/mi
WindowList.pm
--- WindowList.pm 25 Oct 2003 03:00:01 - 1.4
+++ WindowList.pm 19 May 2004 14:56:32 -
@@ -1,4 +1,4 @@
-# Copyright (c) 2003 Mikhael Goikhman
+# Copyright (c) 2004 Mikhael Goikhman, Scott Smedley
#
# This program is free software; you can redistribute it and/or
Hi Mikhael,
: Is not this the last (name) field of M_MINI_ICON event?
Ah, of course.
: Of course you clomber all names in your WindowList patch as far as I
: understand it.
: I had some idea about how to fix this.
Do tell.
Would you like me to fix it?
SCoTT. :)
--
Visit the official FVWM web
> Is there a way to find out the mini icon associated with a window
> via the perllib interface?
I suppose I could issue the following command from within FvwmTabs:
WindowId $winId SendToModule FvwmTabs fn setMiniIcon $winId $[w.miniiconfile]
but that seems a bit cumbersome ... is there a better
Hi Mikhael,
Is there a way to find out the mini icon associated with a window
via the perllib interface?
SCoTT. :)
--
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 pr
Hi all,
I had a go at attempting to implement if-elsif-else-endif syntax for
FVWM so I can do things like this in my .fvwm2rc file:
(Much more intuitive/maintainable than using PipeRead.)
if xdpyinfo | /bin/grep -q XINERAMA
Echo "dual head system!"
Xinerama on
XineramaPr
Mikhael,
Here's a simple test program I was using to test the WindowList tracker.
SCoTT. :)
#!/usr/bin/perl -w
# $Id$
use strict;
use lib `fvwm-perllib dir`;
use FVWM::Module;
my $fvwm = new FVWM::Module(Name => 'Scottie', Debug => 2);
# my $tracker = new FVWM::Tracker::WindowList($fvwm);
my $
Dominik,
What's the status of my window-specific bindings patch with you?
SCoTT.
--
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 PROTEC
"window stack updated",
+ "window icon updated",
=head1 SYNOPSYS
Using B $module object (preferably):
-my $windowsTracker = $module->track("ModuleConfig");
+my $windowsTracker = $module->track("WindowList", $options);
my $windows = $windowsTracker->data;
my $windowSizeX = $windows->{$winId}->{'x'};
or:
-my $windowsTracker = $module->track("WindowList");
+my $windowsTracker = $module->track("WindowList", $options);
my $windowSizeX = $windowsTracker->data($winId)->{'x'};
+Default $options string is: "!stack !icons names winfo"
+
=head1 OVERRIDDEN METHODS
=over 4
@@ -200,7 +266,7 @@
=head1 AUTHOR
-Mikhael Goikhman <[EMAIL PROTECTED]>.
+Mikhael Goikhman <[EMAIL PROTECTED]>, Scott Smedley.
=head1 SEE ALSO
Hi Mikhael,
I'm working on the FVWM::Tracker::WindowList code & I've discovered a
serious bug. In short calls to deleteHandlers() don't work. (handlers
still exist)
This becomes evident by checking the return value from the call to
FVWM::Module::deleteHandler().
=
Hi Dominik,
This post:
http://www.hpc.uh.edu/fvwm/archive/0403/msg00054.html
contains my modified patch for window-specific key/mouse bindings.
I hadn't planned to make any further modifications, but if there's
something you'd like me to change just say so ...
The initial patch (with an exampl
Hi Dominik,
: I have applied the patch with some minor reformatting and
: renaming - nothing serious. Works like a charm, at least for some
: applications (namely, FvwmConsole ignores it).
H, it doesn't appear to work with xterms ...
Module FvwmConsole -terminal rxvt
will make FakeKeypress
Hi all,
Find attached a patch to allow sending of arbitrary key events to
windows. It introduces a new command to FVWM: FakeKeypress
Examples of use:
# save all GVim sessions: Esc:w\n
FvwmCommand 'All (gvim) FakeKeypress press Escape press colon press w press
Return'
# save & exit all GVim sess
Hi all,
Find attached my final patch to bind key &/or mouse events to
individual windows.
SCoTT. :)
? fvwm/.fvwm.1.in.swo
? fvwm/.fvwm.1.in.swp
? modules/FvwmScript/.FvwmScript.c.swp
? modules/FvwmScript/.Instructions.c.swp
Index: fvwm/add_window.c
Hi all,
Find attached a patch to bind key &/or mouse events to individual windows.
Syntax is:
Key Tab (FvwmTabs)A C Function NextTab
Now, Ctrl-Tab in an FvwmTabs window invokes the NextTab function whereas
in any other window the key event is passed through to the window with
the focus.
Other
In HandleKeyPress() [file: fvwm/events.c] why is FVWM messing with
2 windows?
I'm guessing 1 window is the last focused window & the other is the
window that _should_ be focussed (may or may not be the same) - is that
right?
I'm confused as to why it's not possible to decide on _which_ window
t
Hi Dominik,
> > I'm not sure what you mean. If the modifier mask changes that implies
> > another event is generated. Are you just saying that the associated
> > KeyRelease event never gets sent to the application?
>
> Yes, and in addition, when the event is received, the modifier
> mask may diff
Hi Dominik,
Thanks for the feedback, muchly appreciated.
>In your example, you hold down
>Ctrl and tap tha Tab key. The modifier mask has the bit for
>the Ctrl key set.
Yep.
>Now the event is passed on, but when it is
>processed by fvwm or the receiving application, the rea
Hi all,
Find attached a patch to FVWM to define key-bindings on individual
windows. (Previously, a key binding had to be defined for ALL windows
or NONE.)
Example .fvwm2rc syntax:
=== BEGIN ===
AddToFunc CtrlTab
+ I Current (FvwmTabs) Function NextTab
+ I Current (!FvwmTabs) SendKeyEvent curren
: Sorry, I must have missed this one. I am going to add some
: of your shot soon. Could you please provide a configuration
: for the menus as well?
Done - see the bottom of the page:
http://users.tpg.com.au/users/scottie7/fvwmmenus.html
SCoTT. :)
--
Visit the official FVWM web page at http://www
1 - 100 of 126 matches
Mail list logo
