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
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 (combining
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.
On 6/28/06, Scott Smedley [EMAIL PROTECTED] wrote:
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
Scott Smedley a écrit :
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
On Thu, Jun 29, 2006 at 12:12:21AM +1000, Scott Smedley wrote:
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
Olivier Chapuis spake unto us the following wisdom:
- Executing the function without trying to grab at all. You suggest to
add such possibility.
- 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. This is
maybe
On 29 Jun 2006 00:44:22 +0200, Dominik Vogt wrote:
I agree that a failed grab can cause lots of problems. Hopefully
it's clear that many immediate functions may need the grab too.
But I have no idea how to decide if a certain function needs it or
not. The only way would be to write a
On 29 Jun 2006 00:24:50 +1000, Scott Smedley wrote:
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
On 26 Jun 2006 13:52:23 +1000, Scott Smedley wrote:
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.
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_function().
15 matches
Mail list logo
