Welcome to awesome bug tracking system.

FS#846 - Adding Screen Changes Tag Focus

Attached to Project: awesome
Opened by saucerful (saucerful) - Wednesday, 17 November 2010, 23:27 GMT
Last edited by Uli Schlachter (psychon) - Thursday, 18 November 2010, 21:03 GMT
Task Type Feature Request
Category Core
Status Unconfirmed   Reopened
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version 3.4.8
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


I am using one screen and on any tag, then I add a second screen (using xrandr) and the new screen gets recognized and managed by awesome but I get switched to the last tag on the first screen. It seems like awesome is "refreshing" itself with the addition of the new screen and it goes tag-by-tag and ends up on the last one. This means I have to manually return to the tag I was on. Minor issue but I see it every time I dock my laptop at my desk with a second screen.
This task depends upon

Comment by saucerful (saucerful) - Thursday, 18 November 2010, 20:37 GMT
I see. Would it not be simple to just save the focused tag (or tags if there are multiple screens) and client(s) before a restart and switch to them after? I understand that you probably have better things to work on, though...
Comment by Uli Schlachter (psychon) - Thursday, 18 November 2010, 21:03 GMT
In theory, we could save the focused tag index in some property. The currently focused client should already be available to awesome after a restart.

However, the problem are user config files. What happens if you use dynamic tagging and the number of tags changes across the restart?
Saving the currently focused client isn't completely easy either, because when awesome starts managing a client, at first it doesnt have any tags assigned which means the client isn't visible. This causes it to lose the input focus.

I'll reopen this as I don't think we have anything else tracking this idea yet.