There are four ways to do this, only the last one of which is really viable
1) revert to an earlier version of mwm and use the mvwm additions
2) revert to Motif 2.0 and use the workspace-manager protocols in that version of mwm
3) use the mwm-like fvwm or the mwm-like gwm
4) use hardware support for virtual screens, in which case mwm doesn`t know that they`re on the same physical screen
Certain hardware/server combinations support multiple screens on a single physical display. I am thinking in particular of a system offered by HP a few years ago, but this feature is probably available more commonly now that spiffy hardware is more widespread (although that doesn`t imply that people have taken the trouble to port the feature to various PC platforms). The rim of the screen is the portal to the next virtual screen; nudge the mouse up against the edge and move to the next screen.
It`s just as effective, though, to use a window manager which can do the mapping and unmapping, though, so solutions such as fvwm will win out in the end.
There are four ways to do this, only the last one of which is really viable
1) revert to an earlier version of mwm and use the mvwm additions
2) revert to Motif 2.0 and use the workspace-manager protocols in that version of mwm
3) use the mwm-like fvwm or the mwm-like gwm
4) use hardware support for virtual screens, in which case mwm doesn`t know that they`re on the same physical screen
can you elaborate a little on option 4? )
Certain hardware/server combinations support multiple screens on a single physical display. I am thinking in particular of a system offered by HP a few years ago, but this feature is probably available more commonly now that spiffy hardware is more widespread (although that doesn`t imply that people have taken the trouble to port the feature to various PC platforms). The rim of the screen is the portal to the next virtual screen; nudge the mouse up against the edge and move to the next screen.
It`s just as effective, though, to use a window manager which can do the mapping and unmapping, though, so solutions such as fvwm will win out in the end.