On Thu, 16 Feb 2006 15:30:53 +0100, Etan Reisner <[EMAIL PROTECTED]>
wrote:
[...]
P.S. My version is attached, if people think is should be in the
repository feel free to tell me to submit it or to submit it
yourselves.
I think it should handle multiple screens better (though I don't
really know since I don't have multiple screens, I also don't know that
it will handle multiple statusbars (or even if that can be handled at
all)
I just tried it, and it doesn't work with multiple statusbars; the same
text is set for all regardless of which screen it's on. It does
somewhat work with multiple screens (in case you only have one
statusbar) but only with %wsname; %wsfull only gives the workspace list
of the screen that was the latest one changed (so it's a bit
misleading).
So in there interests of making my script work better, how should it
work with multiple screens and possibly multiple workspaces?
Definately. :)
I considered making it only ever update based on changes on the same
screen as the statusbar, but then I thought people with only one
statusbar might like it to show what workspace they are on even when it
is on the other screen. And if someone wanted that how would it work for
multiple statusbars?
I'm sort of stuck as to the "correct" way for this to work for the two
screens one statusbar case. One screen one statusbar is obvious, two
screens two statusbars is also rather obvious (unless people think
someone would want the statusbars to show the same information on both
screens). It is two screens one statusbar that complicates things.
With one statusbar and multiple screens, the IMHO most intuitive aproach
is for %wsname show all active workspaces and %wsname_full to merge the
list of workspaces from all screens. Eg, if you have two screens and one
statusbar, %wsname_full could look something like this: "*WS1* *WS2* WS3
WS4".
This needs to be configurable, since you can't really detect what to do in
case of multiple screens (eg. I have 3 screens with statusbars on 2 of
them, and I want the "two statusbars on two screens" effect).
P.S. As I final thought I had while typing this email, I thought that
perhaps I should just make a number of %wsname_X meters where X is a
number correpsonding to the screen it counts for. Does that make sense?
Kind of, but since it should be possible to get the that information at
runtime it would be nice if it could be avoided. (I create my statusbars
in a loop, and this would complicate things a bit.)
PS.
As for updating when a workspace is renamed, the script could export a
nice, simple API for this, which can be used in the bindings. Either a
wrapper function that you call instead, or a utility function that only
updates %wsname.
PPS.
Instead of using a marker symbol, how about coloring the active workspace
name with the activity color? Is that possible to do with a normal
statusbar meter script?
--
Adam Chodorowski <[EMAIL PROTECTED]>
