Quoth Tethys . at 17:28:52 +0100:
That restriction turned inconvenient enough that since the advent of
"humongously big" (>1920x1440)
Your definition of "humongously big" is "barely usable" in my world :-)
Well, unless you started quite late, I'd guess suppose you have used
smaller screens for a long time. I did not mean it to imply "excessive"
(as mentioned, it's a real usability and productivity matter in my work,
which is why I have a 2560x1600 screen on my desk), but rather compared
to the 1280x1024 and 1600x1200 that have been the standard on graphical
workstations for a long time (or even the 1024x768 on common X
terminals), which made multiple screens a great way to supplement the
space.
Lack of QXGA support has kept me away from LCDs for a long time.
That's starting to change, but they're still hideously expensive.
Expensive, compared to QXGA CRTs before?
I recall good 1280x1024 CRTs cost more ten years ago than good 2560x1440
LCDs cost now. (sane 4x3 or 5x4 aspect ratios are becoming really hard
to find though -- everybody now does the "widescreen" fad). And
nowadays new CRTs seem rare and more expensive than similarly sized
LCDs.
FVWM already supports a distinction between logical and physical screens.
For example, I have EdgeMoveResistance set to allow easy window alignment
with the edge of my physical monitors, even though that may be in the
middle of my single logical screen. I'm not sure what you want to do
with paging, though. If I'm understanding you correctly, you want to
be able to have a separate pager for each physical screen?
Right. I'd like to change page or workspace on one screen without
affecting the other(s).
Ideally the set of workspaces would be shared between all screens, but
I'd be better already with just a per-screen set, and some way (that
doesn't need to be as transparent as dragging with the points) to move a
window between screens.
But if so, I suspect you haven't thought it through. What do you do
when a window straddles two physical screens and you change page on
one of them, for example?
This being quite hypothetical as I mentioned I wouldn't want windows
straddling two physical screens anyway (I'd find it hard to read with a
gap of some centimetres between neighbouring pixel columns), I'd say
since window positions are defined by their top-left corner, it should
be associated with the page that corner is in.
Tet
Cheers,
-- Tom
-- "Java is a DSL for taking large XML files and converting them to
stack traces" -- Bulat Shakirzyanov
Love that quote, BTW.
