>
> My three outstanding ctwm nits:
>
> 1) I have my 4 workspaces mapped to the F1/F2/F3/F4 keys, and
> I toggle back and forth between them constantly.
>
> I've occasionally noticed that glitchy things can happen when
> switching quickly. The usual symptom is that just after switching, a
> window will "follow" me and appear on the appear on the workspace I
> just switched to. It then appears on any workspace switched to until
> its "home" workspace is visited, after which it behaves properly.
> This usually happens when my boss walks into my office, and the window
> that follows me usually contains something that I shouldn't have been
> doing at work. :-)
This is a very old ctwm bug. I had tried to find it several times in
the past without success. But the due to the extremely serious reasons
you give, I tried once more to put the hand on this bug. And you won't
believe me, but it is fixed.
>
> 2) I wish that the workspace manager windows could have the highlight
> pixmap set on a per-workspace basis. I have the background pixmap in
> each small representation set to be the same pixmap as the real
> workspace it represets. If I could set the highlight on a per tiny
> workspace basis, then I would set the highlight pixmap to be the same
> as the unhighlighted pixmap, and just use the border color to show
> which workspace I'm on.
It is not clear in the manual but in the command :
MapWindowCurrentWorkSpace { border_color background foreground bitmap }
The values for background, foreground and bitmap are optionnal.
If you don't give the bitmap, ctwm just paint the small window in
plain background. Unfortunately, if you don't give background and
foreground, ctwm have a default value and still paint the small
window with these values. I'll change this so that if you dont give
a background, it is not painted.
>
> 3) The line numbers of errors don't seem to have any correlation
> whatsoever to the actual raw .ctwmrc file. I've been unable to
> track down the cause of these two errors forever. You know its
> a bad sign when you -delete- the line in question, and it just
> moves the error line number up or down by one.
>
> /tmp/twmrca00515:8: m4: Warning: Excess arguments to built-in
> `define' ignored
> ctwm: line 202: error in input file: parse error
The problems is with m4. Since the startup file is preprocessed
with m4 the line numbers are changed during this process. You can
use the -k option to have an idea of the offset. Or, if you don't
use m4 use the -n flag, the line numbers will be good.
>
> The fact that these are the worst complaints I have indicates that
> ctwm is a great program! Thanks!
>
> -Roger
>
Claude.
This archive was generated by hypermail 2.1.2 : Sat Jun 22 2002 - 06:45:02 CEST