Closed richnetdesign closed 10 years ago
Elv13
commented
11 years ago hello,
it currently doesn't work very well. i have a patch that make things better but it wont be enough. it will take some more work to get right
UPDATE: I pushed the commit, it should work better now
richnetdesign
commented
11 years ago Is the clone feature unique to tyrannical, or has it been implemented using other libraries in awesome before? I was just wondering so I could have a reference.
Elv13
commented
11 years ago I don't think so. What I really think is that it should be done in a much deeper level (in the C code), but some others disagree. This implementation will always be limited by some design choices in the tag themselves. I am not saying that a few bad bugs like the duplication one cannot be fixed, they can, but some other, like preventing clients from being added to the clone then disappear are much deeper than that.
Elv13
commented
10 years ago Closing this, see https://github.com/Elv13/tyrannical/issues/40
System
I've created a tag { name = "WWW", init = true, exclusive = true, screen = 1, clone_on = 2, layout = awful.layout.suit.max, -- Use the max layout class = { "Opera" , "Firefox" , "Rekonq" , "Dillo" , "Arora", "Chromium" , "nightly" , "minefield", "chromium-browser" } } ,
A new tag is listed on both monitors.
I open firefox on WWW Screen 1 and it's all good.
I switch monitor 1 to a diff tag. Switch monitor 2 to WWW expecting to to match what I just saw on monitor 1, however either nothing is display, or the windows flickers away really fast.
Now monitor 2 has glitched out and created a second WWW tag. It is now the only tag which displays firefox. Switching to WWW on monitor does not display firefox.
I will test this on a different machine, I wonder if it has to do with Nvidia TwinView or something. Cloning sounds like a killer feature I just haven't got it to work yet.