FVWM: Canceling window placement via user-defined key
Is it possible to cancel a Move operation via a user-specified key binding? The built-in bindings to Space and Return work fine for that, but I'd like to define a key other than (or in addition to) those, if possible. >From the doc, I thought 'CancelPlacement' might be a general function for that purpose, but seems like it is available for use only with the Mouse command. Version info: fvwm 2.6.8 compiled on Jun 14 2018 at 12:44:24 with support for: ReadLine, Stroke, XPM, SVG, Shape, XShm, SM, Bidi text, Xinerama, XRender, XCursor, XFT, NLS Thanks!
Re: FVWM: Canceling window placement via user-defined key
Hi Elliot, Thanks for your suggestions. (Replying to list since my original post may have been confusing.) elliot s [2018-12-29 14:00:27 -0800]: > > I use Esc to kill moves in progress. > > If key bindings can work while move in progress, maybe you can hit a > key to remember old position and then hit it again to move window back. > Actually, what I meant by 'cancel placement' is to terminate the placement operation, not to return the moved window to its original position. It was my mistake to use the word 'cancel' rather than 'terminate' in my post, because now that I read the fvwm man page more carefully, the way you have interpreted 'cancel' -- returning the window to it's pre-moved position -- seems to be what the man page means too. I didn't appreciate that when I first read about CancelPlacement. Anyway, the idiom I'm seeking to implement is this: 1. Tap Control_R with pointer inside a window to begin 'Move' operation 2. Use arrow keys to reposition the window 3. Tap Control_R to terminate the 'Move' operation So Step 3 just leaves the window where it was when Control_R is tapped the second time. It's easy to implement the above with a trivial function and key binding, but Step 3 is the problem: DestroyFunc MoveOrTerminateMove AddToFunc MoveOrTerminateMove + I ThisWindow (!State 6) Move + I ThisWindow ( State 6) <> + I State 6 toggle Key Control_R W N MoveOrTerminateMove The 'Return' and 'Spacebar' keys have built-in bindings that terminate a Move operation, and they work fine. But I'm lazy and would like to be able to use Control_R instead, because on my keyboard, Control_R happens to be located right next to the group of arrow keys. So this would allow a handy and compact way to do small detailed repositionings mouselessly.
Re: FVWM: Canceling window placement via user-defined key
On Sat, Dec 29, 2018 at 04:29:00PM -0700, Glenn Golden wrote: > Anyway, the idiom I'm seeking to implement is this: > > 1. Tap Control_R with pointer inside a window to begin 'Move' operation > 2. Use arrow keys to reposition the window > 3. Tap Control_R to terminate the 'Move' operation All the keyboard shortcuts for moving and resizing windows, dragging the viewport and execution of complex functions are hard coded in libs/Target.c. I.e. this won't work without changing the sources. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
Re: FVWM: Possible bug: Jumping pointer in Darktable
Stefan Klinger writes: > Hi Dan, > > sorry to bother you again: In November I had asked you [1] to look after a > bug I was observing with FVWM and darktable. At that time you were > testing with darktable-2.4.4, and you did not observe the bug. > > I don't know whether you have tried any newer version, but a couple of > days ago darktable 2.6.0 was released, and it shows the bug. I'd > really like to know whether you can reproduce the that... > > Steps to reproduce the bug are here [2]. > > Thank you! > > Stefan > > > [1] https://www.mail-archive.com/fvwm@fvwm.org/msg03403.html > [2] https://redmine.darktable.org/issues/12387 I got 2.6.0 installed. I want to be sure I remember how to test for this. I start darktable and import an image and click on it. I then open the "mask manager" triangle to use the tools there. If I select the circle tool, a circle appears on the image. I can then move the circle around but when I click to drop it it jumps somewhere else? The edit tool has similar issues. I don't remember it failing when I tested it last. I'm using a newer video card than the last time we did this. -- Dan Espen
