i'll remove the iconification when launching bbkeys and see how cvs behaves.  that 
100ish off is the placement for any new window with no other windows / xapps running.

dan

* Sean 'Shaleh' Perry ([EMAIL PROTECTED]) wrote:
> >> 
> >> another happy customer (-:  If you have an iconified window open during
> >> blackbox init it will crash.  Code that used to be safe is now not due to
> >> our
> >> reorganization of XGrabServer (we call it a LOT less).
> > 
> > 
> > So you're saying bbkeys -i in .xinitrc caused the cvs version to crash?  I
> > would think the masses would want the ability to launch apps iconified.
> > 
> > 
> 
> and fixing this is why alpha2 is not out yet ......
> 
> >> 
> >> As for your new window and maximization issues this is causes by the strut
> >> code.  New windows and maximization of windows will not touch the slit or
> >> the
> >> toolbar.  Imagine the visible screen as a window.  Now resize that window to
> >> be
> >> constrained by the toolbar and slit.  This window is what blackbox uses to
> >> decide on valid placement.  If you do not like this, choose 'full
> >> maximization'
> >> from the config menu.
> > 
> > 
> > The 10ish pixels on the maximization I can certainly live with, but the
> > 100ish pixel off right placement of new windows would grow old quickly.  As
> > far as being "another happy customer" I am completely happy with blackbox. 
> > So happy in fact that I decided it's time I should give back what I can, and
> > that consists of testing development versions.  Everyone's work on blackbox
> > is much appraciated.  I couldn't imagine using another wm...except
> > fvwm-themes perhaps, but we won't go there :)
> > 
> > dan
> 
> ok the '100ish off right placement' will change depending on the window you
> open.  What happens is during window placement the new window asks "will I fit
> in this space?" and the wm does screen_width - (current_x + window_width) and
> looks if the result is > 0.  So if your new window would just fit on the screen
> normally it is now too big and gets moved down a row to start over.  This issue
> is the same with maximized windows.  term windows tend to behave a little worse
> because they want to have sizes that a based on a ration.
> 
> The CVS code takes this one step further and makes it so edge snap works on the
> available area, not the physical screen, just like placement and maximization. 
> This behaviour is consistent with other wms that support strut (via the netwm).

Reply via email to