It should probably be abstracted further, to just a list of monitor positions in the buffer. I'm working on an xrandr patch to do just this (I took all the recent messages about xrandr as a challenge =)
Anselm: re: method #3, the screen-tagging approach, I think it would be simple to use part of the tag bits as a monitor specifier. ie for 2 monitors reserve the topmost bit for the screen (0 or 1), or for 3 or 4 screens use the top 2 bits. the storage is already there, and the tagmask will easily keep it out of the way other code. Then something like MOD-1 for tag 1 on screen 0, and MOD-F1 for tag 1 on screen 1, where the keybinding simply adds the extra bit? Jeremy On Thu 11 Dec 2008 - 07:56PM, yy wrote: > What about moving XineramaScreenInfo *info = NULL; out of > updategeom()? if you make info a global variable it is easy for people > to have custom tile algorithms which make use of it. If you also > define custom functions to view tags, change layouts, etc you will be > able to have plenty of different xinerama configurations without > messing up with dwm.c. People could easily add their custom dual.c > files. You wouldn't be possible to achieve all of the different > configurations which were mentioned in this thread, but I think you > could get most of them. > Just an idea... > > > -- > > > - yiyus || JGL . >
