nilix/fluxbox
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

unrevert 1fdef35e51

Browse source 
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.
This commit is contained in:
Mark Tiefenbruck 2008-10-15 16:20:30 -07:00
parent 6642792f68
commit f92fd6ca05
1 changed files with 0 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
src/Window.cc
View file

@ -2851,20 +2851,6 @@ void FluxboxWindow::stopMoving(bool interrupted) {
fluxbox->maskWindowEvents(0, 0); 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()) { if (! screen().doOpaqueMove()) {
parent().drawRectangle(screen().rootTheme()->opGC(), parent().drawRectangle(screen().rootTheme()->opGC(),
m_last_move_x, m_last_move_y, m_last_move_x, m_last_move_y,