-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pr/autograb #393
base: 3.6.x
Are you sure you want to change the base?
Pr/autograb #393
Conversation
compiler warning:
|
should be:
|
Not working:
-> window title still says "... (input lock)" but the actual lock is gone.
|
IRC backlog regarding this PR:
TL;DR; the prev variable in setWinNameSuffix() requires more work (make it global, manage it in setWinNameSuffix() and free it properly at session end / abortion. Plus comments above. The new autograb functionality is so great, I believe we should make it the default (if not now, then at least very very soon!). |
Things that need to be improved:
|
@uli42: any news on this one? What's its status? |
On Mon, Apr 3, 2017 at 9:20 PM, Mike Gabriel ***@***.***> wrote:
@uli42: any news on this one? What's its status?
Being a bit distracted currently, but: I cannot seem to get the
fullscreen stuff fixed. Also, I am unsure how to implement the
activation. Command line switch, options file, keep previous state a
reconnect or not?
|
Hi Uli,
On Mo 03 Apr 2017 21:26:05 CEST, Ulrich Sibiller wrote:
On Mon, Apr 3, 2017 at 9:20 PM, Mike Gabriel
***@***.***> wrote:
>
> @uli42: any news on this one? What's its status?
Being a bit distracted currently, but: I cannot seem to get the
fullscreen stuff fixed.
I may not be of help with this...
Also, I am unsure how to implement the
activation.
Oh, that's easy...
Command line switch
Yes.
options file
Yes.
keep previous state a
reconnect or not?
Yes.
Mike
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: [email protected], http://das-netzwerkteam.de
|
On Mon, Apr 3, 2017 at 9:47 PM, Mike Gabriel ***@***.***> wrote:
> Command line switch
Yes.
> options file
Yes.
Really both? Why?
|
Hi Uli,
On Mo 03 Apr 2017 21:57:31 CEST, Ulrich Sibiller wrote:
On Mon, Apr 3, 2017 at 9:47 PM, Mike Gabriel
***@***.***> wrote:
> > Command line switch
>
> Yes.
>
> > options file
>
> Yes.
Really both? Why?
Yes. I can help with both or either, once the core code is in.
Mike
…--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: [email protected], http://das-netzwerkteam.de
|
051708f
to
025ba6e
Compare
@uli42: this is not working yet... As you know I use a tiling window manager (i3). I can easily escape the input lock if auto-grab is off, for example. Also, I wonder, if we shouldn't rather introduce "flags" as opposed to the "autograb on|off" and "input lock on|off" strings in the title. E.g. "nxagent [GIX]" (grab, input lock, xinerama on) vs. "nxagent [giX]" (grab and input off, Xinerama on). That makes the agent not seem soooo English. Furthermore, the autograb mode standalone seems to work. So I wonder, if we should separate those two features for now and get the autograb code in as is. The input lock, I can e.g. escape from when I disable the autograb mode and then manipulate the window (e.g. minize or some fancy tiling command in i3). The window moves by keyboard event to "somewhere" else, the mouse is left outside nxagent and nxagent still shows input lock. Not true. So for input lock we maybe need to capture mouse-in and mouse-out events (seen from nxagent's perspective). If the user manages to escape from the nxagent windows, then a new mouse-in event should trigger the input lock once more and capture the pointer. I can take a closer look tomorrow, but maybe the above gives you a clue and things are fixed by tomorrow morning. Hehehe... |
Changing display of the state in the window title can be adjusted after this patch works in all situations... You write "the autograb mode standalone seems to work". Well, have you tried switch to fullscreen and then switching back? This is not working properly for me. Also, I have not understood yet how to synthetically insert events into the queue as you suggest for the mouse stuff. I'd appreciate any help to get this going. |
Fixes ArcticaProject#384 You can now toggle between autograb mode by pressing CTRL-ALT-G (default, can be adjusted in keystrokes.cfg). You can toogle inputlock mode (pointer stays in the nxagent window) by pressing CTRL-ALT-C.
This also make re-autograbbing after switch back from AllScreens work.
Update: autograb code is merged and working, but we have left out the window title handling stuff and the inputlock code. |
second version, added inputlock (force-grab) via ctrl-alt-c. Please test. Enable autograb via ctrl-alt-g.
Code definitely needs cleanup, this is just w-i-p with a lot of testing/debug code.