Age | Commit message (Collapse) | Author | Files | Lines |
|
when changing the active window via NextWindow/PrevWindow and then
not beeing able to set the focus of the window underneath the mouse
with a simple click again (in MouseFocus - mode). Suggestion via
mail to devel-ml from Eike von Seggern
|
|
|
|
<krzysiek.pawlik__AT__people.pl>)
New init options added:
session.screenN.windowScrollAction: Shade|NextTab
- set the action that happens when scrolling on the titlebar
session.screenN.windowScrollReverse: true|false
- reverse the action direction
|
|
when mod1 + leftmouse are clicked on a window and the mouse is not
moved, the window is raised at leftmouserelease. i dont think we
need an extra option for that since its very unobtrusive but neat
to have.
|
|
wrong code in Container.cc
|
|
the "Sloppy" was always a bit .. unprecise.
removed SloppyFocus, SemiSloppyFocus and ClickToFocus options
added MouseFocus, ClickFocus, MouseTabFocus, ClickTabFocus
- MouseFocus - change the focus to the window under the mouse
(almost similar to the 'old' SloppyFocus)
- ClickFocus - change the focus to the window the user clicks
- MouseTabFocus - change active tabclient to the one under the
mouse in titlebar, does NOT change the focus
- ClickTabFocus - change active tabclient when clicked onto a
tabbutton
to achieve former SemiSloppyFocus behavior one needs MouseFocus and
ClickTabFocus
|
|
area to drop a tab button to detach the client from the group. solution is to
detach the client if the tab button is dropped onto the client area of the
same group.
|
|
|
|
|
|
|
|
|
|
|
|
shaded icons behaved badly on restart, they went into a real stupid state:
somehow shaded, but at the same time iconic, so you werent able to unshade,
resize them properly.
i fixed that by applying NormalState on shutdowntime (see
FluxboxWindow::restore(), unshading a shaded frame to get good
window dimensions and on init() i mark the window initialized and connect it
to Fluxbox::attachSignals() a bit later.
|
|
- Shade - just like the "Stick"-button
Styleresources:
window.shade.pixmap, window.shade.unfocus.pixmap, window.shade.pressed.pixmap
window.unshade.pixmap, window.unshade.unfocus.pixmap, window.unshade.pressed.pixmap
etc.
- MenuIcon - click on it provides the windowmenu, if the app
contains a pixmap (gvim, konqueror etc etc) the pixmap is displayed, a
little menu otherwise.
Styleresources:
windowmenu.pixmap, windowmenu.unfocus.pixmap windowmenu.pressed.pixmap
etc.
Example ~/.fluxbox/init - entry:
session.titlebar.left: MenuIcon Stick
session.titlebar.right: Shade Minimize Maximize Close
hint: if the app HAS a pixmap i use window.title.focus.pixmap (look
WinButtonTheme for reference)in pixmap-based-styles. this looks excellent and dont need
much extra-code to pipe that info into WinButtons.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
background pixmap. Same for textbuttons.
|
|
Window is not maximized any longer per definition imho. maybe we need to apply
the same policy to the fullscreen-State
|
|
such windows dont have DECORM_ENABLED and hence no borderwidth was
added to the calculation. thats fixed now
|
|
|
|
Consequently rearrange lots of rendering ops, and strip calls to
updateTransparent
|
|
Stevens <stever3 at nycap dot rr dot com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
decoration/handler hints
|
|
toolbar-borderwidth
further more windows do snap at screen-edges, no matter if maxover
is enabled or not
|
|
|
|
* synchronize _NET_WM_STATE in Ewmh.cc
* added FluxboxWindow::setFullscreen(bool) to Window.cc
furthermore, if a window is in fullscreenmode any existing shape is
disabled (looks pretty annoying in mplayer for example)
|
|
fixes dragNdrop ordering of tabs so next/prevtab are not
confused -> modification of m_clientlist
|
|
it.
closed #1082671
|
|
closes #1075142
|
|
disable title of the windowmenu when called from titlebar
|
|
Paradise Poker client
|
|
|
|
decorationless windows have a borderWidth of 0 and thus the
snapping was calculated wrong.
|
|
attached or dragged around)
|
|
|
|
|
|
|
|
|