Function tips


Writing /Config/ComplexFunctions is not always that easy. Indeed, one of the biggest problems tends to be the sequencing of events – and knowing when it is appropriate to specify any conditional commands.

It has become more and more apparent to me (ThomasAdam) that people are writing functions to do some very clever things, without really thinking their logic through. This has lead to all sorts of interesting situations. Because FVWM can be “scripted”, that doesn’t mean to say that a task ‘‘should’’ be done that way. :)

An Example

Let’s take an example. Let’s suppose we want to write a function that moves a specific window to the top-right corner of the screen as soon as it appears on screen. Sounds simple enough, right? First thing we have to solve is how we’re going to do that. FvwmEvent allows for certain actions to be listened for, and actioned upon where appropriate. It’s a very useful module, and when writing functions that depend on them, can be invaluable.

Thinking it through

In this specific case, we can use the add_window event which will fire off as soon as a window is made to appear (mapped) on the screen. We can tell it to call a function, the name of which we’ll call MoveWindow, hence:

DestroyModuleConfig FE-movewindow:*
*Fe-movewindow: Cmd Function
*FE-movewindow: add_window MoveWindow

Module FvwmEvent FE-movewindow

Sets up the listener that will call the function. Our function might first of all look like this:

DestroyFunc MoveWindow
AddToFunc   MoveWindow
+ I AnimatedMove -0 +0

Try it – open a window. Works fine, doesn’t it? As it should do – the function is being called in an adequate context already. However, there are going to be specific times when this isn’t always going to be the case. And more to the point, how do we further go on to disclude certain windows from having this function operating on them in the first place? Welcome to the use of conditional commands.

Current, ThisWindow, etc.

/Config/FunctionContext is everything when it comes to operating on windows. Indeed, ensuring a functions runs within a window context is tricker than many think. In continuing with our example though, we’ll soon see that we need be specific. What do we do when need to specify a specific window to be moved, and to ignore all others? This is where the /Config/Conditionals command ThisWindow comes in useful.

ThisWindow is a command more or less guaranteed to place a window within a given context. So if you’re ever unsure if the function is going to work without it – but you always want to force a window context, use it. Hence:

DestroyFunc MoveWindow
AddToFunc   MoveWindow
+ I ThisWindow AnimatedMove -0 +0

And indeed, using ThisWindow to help specify a window name (to match against) is also a pretty good bet. One thing ThisWindow as a conditional command is good at, is providing context without any additional constraints (i.e. it will pretty much operate on a window, regardless). Compare of course, the following function instead:

DestroyFunc MoveWindow
AddToFunc   MoveWindow
+ I Current AnimatedMove -0 +0

Looks innocent enough, right? The problem here though is that if one already has a window focused, it’s that window which is moved, and not the window that has just appeared. This is because ‘‘Current’’ has a hidden and assumed prerequisite — it implies the current window that has the focus. Very useful under certain conditions (when you definitely know that you want to operate on the currently focused window), but in our situation, we don’t want or need it, so we’ll discard it. And indeed, it might not always be the case that the operand windows will have focus.

So definitely ThisWindow. Luckily, like all conditional commands, we can make specific requirements as to the windows they operate on. So, let’s expand our function to say that we only want rxvt windows to be moved to the top-right:

DestroyFunc MoveWindow
AddToFunc   MoveWindow
+ I ThisWindow (rxvt) AnimatedMove -0 +0

This function can of course be expanded further.


So, when you’re writing a function, consider: