all repos — fluxbox @ f92fd6ca0562c7a91facbab4ec1ffa87ffc0d517

custom fork of the fluxbox windowmanager

unrevert 1fdef35e51
										x
Mathias should listen to me when I say "by the way, I know you liked the code I
just removed; you should change your keys file to use
:MacroCmd {Focus} {Raise} {StartMoving}". Behavior in 1.0.0 and previous was
that alt+click would focus and raise, regardless of whether the window was moved
or not. If mathias really wants his alt+drag to preserve stacking order, he
should add Mouse<N>Move events to the keys file to distinguish moving from
clicking. I've been planning on doing it anyway.
Mark Tiefenbruck mark@fluxbox.org
commit

f92fd6ca0562c7a91facbab4ec1ffa87ffc0d517

parent

6642792f68ae42ba8d2bcbe2033284f7e8e61167

1 files changed, 0 insertions(+), 14 deletions(-)

jump to
M src/Window.ccsrc/Window.cc

@@ -2851,20 +2851,6 @@ Fluxbox *fluxbox = Fluxbox::instance();

fluxbox->maskWindowEvents(0, 0); - // if user has no clickraise he moves windows without - // changing the stacking order. by not moving the mouse - // but clicking (and holding the modifier for moving) - // the window raises without having to aim for the titlebar/border - // this is a mixture between "mouse raise" and "click raise" - // TODO: state this in the official documentation - if (m_last_move_x - frame().x() == 0 && - m_last_move_y - frame().y() == 0 && - !screen().clickRaises()) { - - raise(); - } - - if (! screen().doOpaqueMove()) { parent().drawRectangle(screen().rootTheme()->opGC(), m_last_move_x, m_last_move_y,