On Fri, Aug 22, 2008 at 07:22:52AM -0500 I heard the voice of
Matthew D. Fuller, and lo! it spake thus:
>
> Give this a try if you can; if it works right for you (no reason it
> shouldn't), and nobody has objections, I'll commit it in a few days.
Well, OK. A few days, 2 months, it's about the same thing, right?
Anyway, it's committed now.
This should be revisited to add either a flag or a special Threshold
value to avoid the issue entirely and always OpaqueResize, especially
since I suspect that's the very common case anyway. What's the
feeling on the matter? I think adding a new keyword for Always would
be an unnecessarily verbose way around it. 3 options present
themselves for special Threshold values.
1) 0. It's possible that there's some side effect of setting
OpaqueResize that some people desire, without wanting windows to
actually ResizeOpaque'ly, though I can't think of what it could be.
2) 100. Assume 100% really means 100%. This could cause issues in
the case of resizing bigger than the presumptive screen size, when
somebody really does want to wireframe past that.
3) 1000. This is what ctwm initializes it to if there's no setting
sitting around in a config file. We can assume that it's infinity.
3a) >= 1000. Just in case somebody gets the idea that
$REALLYBIGNUM should be used.
I find myself leaning toward (3).
--
Matthew Fuller (MF4839) | [EMAIL PROTECTED]
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
