On Wed, 6 Mar 2002 18:59:10 -0800
Marc Wilson [EMAIL PROTECTED] wrote:
On Wed, Mar 06, 2002 at 12:55:04PM -0800, Sean 'Shaleh' Perry wrote:
for instance. The next thing to consider is whether to honour the
availableArea of the screen and thereby not cover things like the slit or the
IIRC, this is correct. The current method of placement doesn't maintain a
list of free areas.
in cvs I keep a single rectangle which knows the actual available size of the
screen versus the real screen's size. The availableArea is reduced by windows
which declare a 'strut' as per the
Heya,
I've been usin enlightnement for a little bit, and got used to the raise window
behavior. Regardless of focus mode, you can click anywhere in the window to raise it.
After doin a bit of my own work, I found an older patch on
blackbox.thelinuxcommunity.org, so I just updated that one to
On Wed, Mar 06, 2002 at 02:29:16PM -0600, Mike wrote:
I've been usin enlightnement for a little bit, and got used to the raise
window behavior. Regardless of focus mode, you can click anywhere in the
window to raise it.
Don't forget that you can alt-click (or whatever you have the modifier
Heya,
I've been usin enlightnement for a little bit, and got used to the raise
window behavior. Regardless of focus mode, you can click anywhere in the
window to raise it.
Don't forget that you can alt-click (or whatever you have the modifier set
to) the window to raise it.
Yeah, I know
But I'm trying to modify it to do what you describe, and I don't see where
bb calculates the available area. Got a pointer to the appropriate code?
In reading through the maximize_over_slit patch, it seems that bb has to
calculate it on the fly each time.
It is in the CVS code. look
Is CVS currently buildable?
yep.
Making all in src
make[2]: Entering directory `/usr/local/src/blackbox/src'
c++ -DHAVE_CONFIG_H -I. -I. -I.. -DSHAPE -DSLIT -DINTERLACE-DNLS
-DTIMEDCACHE -DLOCALEPATH=\/usr/local/share/blackbox/nls\
-DDEFAULTMENU=\/usr/local/share/blackbox/menu\
