moe wrote: > On Sun, Apr 01, 2007 at 01:50:03PM +0100, Nick Murdoch wrote: >> moe wrote: >>> hi list and tuomov, >> <snip> >>> maybe we can get away with a bit of cheating here? >> I think being hacky and horrible was the main reason Xinerama support >> was dropped ;) > > well, i read tuomovs rants as "it was dropped because the > horror creeped into many areas of the code" but i may be > mistaken. > > i hope that the hack i proposed would be much less intrusive > and could get the job done at a minimum cost (both in terms of > lines of code and in terms of uglyness). > > i imagine that the only changes needed would be to add > a "create workspace hook" and to make the placement of > floating windows "virtual screen aware". ideally this > could all be done in lua but i haven't looked for the > necessary hooks, yet.
The main advantage of dual monitor support for me is the fact that the workspaces are independent (so I can switch workspace on monitor 1 and monitor 2 remains the same), and that fullscreening a window makes it fullscreen, rather than stretching across two monitors. Without those two things, I might as well just tile such that no tile crosses between monitors. >> Just for the record, I was also using ion3 until Xinerama support was >> dropped. I have a TV card and like to run tvtime on the second monitor. >> I've switched back to ion2 for now. >> >> To be fair, Xinerama does tend to have awful support elsewhere too. The >> Gimp really hates dual-monitor set-ups (Every time I want to use my >> graphics tablet I have to start a new display that only uses one of my >> monitors), and qiv also breaks in fullscreen mode. I'm sure there are >> other examples. > > agree'd. i have given up on using the gimp under ion a > long time ago, tho (prefer shotophop under vmware anyways). Photoshop actually runs quite well under Wine these days, if that's handy at all for you :)
