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 NoGrab?
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
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 would
On 29 Jun 2006 18:57:55 +1000, Scott Smedley wrote:
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
Without commenting on all particular statement in this discussion,
I want to make clear why I think it's a bad idea to leave the
decision about grab/nograb to the user:
1) The user has *no* idea of the implications and can not make
a proper decision. Hell, even something as simple as this
