Age | Commit message (Collapse) | Author | Files | Lines |
|
decoration/handler hints
|
|
toolbar-borderwidth
further more windows do snap at screen-edges, no matter if maxover
is enabled or not
|
|
only when using "imlib_load_image_with_error_return" as the loading
function imlib2 seems to avoid trouble when an image with <filename>
doesnt exist. all other loadroutines lead to heavy problems when
fluxbox shuts down and tries to restart (memleak(?), distorted xressources
etc)
i ll analyze this further. another open issue with imlib2 is that it
doesnt work when xserver/fluxbox is running in dualscreen-mode (not
xinerama), no valid pixmaps are visible on the second head. dunno why
(yet).
|
|
- added a guard so no invalid(0)-handler is deleted at shutdown
- "if (s_image_map[extension] == 0)" -> creates an entry for sure, we
dont want this.
|
|
|
|
|
|
|
|
besides xpm. to get imlib2 support in fluxbox one has to
./configure --enable-imblib2
default is disabled. a fluxbox-binary that supports imlib2 will have
IMLIB2 in "fluxbox -info"-output
explanation to the changed files:
* xft.m4 -> acinclude.m4 + added ac_path_generic.m4
(from http://ac-archive.sourceforge.net/Miscellaneous/ac_path_generic.html)
* configure.in, Makefile.am, src/FbTk/Makefile.am changed to handle
imlib2-support
* Font.cc/hh Image.cc/hh App.cc fluxbox.cc consistent way of init for global
stuff for fonts and imagehandlers.
* rest of changes just add the imlib2-code, pretty straightforward
|
|
* 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)
|
|
|
|
sethead <int>
which sets the current window to head<int>
* added remembering of the head to apps-file:
[Head] {<int>}
|
|
|
|
m_start_pos has to be 0 before calculating anything else.
|
|
file and directory - helproutines.
* created the FileUtil-namespace which contains file-related functions, moved
those functions out of Directory - code
* changes to the rest of the files to follow those changes
|
|
|
|
|
|
FbTk::Menu::update(Subject*) and FbTk::Menu::update(int index)
to avoid this, we rename FbTk::Menu::update(int index)
-> FbTk::Menu::updateMenu(int index)
this is mostly cosmetic, but if it makes the life of a compiler happy, well ..
be happy icc :)
|
|
fixes dragNdrop ordering of tabs so next/prevtab are not
confused -> modification of m_clientlist
|
|
|
|
|
|
it.
closed #1082671
|
|
causes a reconfigure .. which causes a loop over all toolbaritems and call
updateSizing() .. where we should check, if a new timeformat makes the clock
bigger or smaller...
closes #1026096
|
|
|
|
|
|
|
|
|
|
in the slit
|
|
* wheel up/down move the slitclient up/down
* visual cosmetic for the slitclient-menu
* added "Save SlitList" - menuentry in slitclient-menu
|
|
|
|
was introduced)
|
|
and all related bugreports elsewhere. "fixes" because i think the real problem
is in xft somewhere somehow, but i dont have any prove (yet).
thanx to Rob Stevens for informing us about that problem.
|
|
furthermore, and this is really interesting, this seems to fix also the bug
widely known as g.o.d - the grab of death. the g.o.d seems to freeze fluxbox
but let the mouse still be moving and no high-cpuload can be seen. the
(un)lucky can force the g.o.d by clicking like a weirdo and pressing keys like
crazy and then maybe it will happen. we are not quite sure WHY exactly this
happens but as it seems: XSync(true) caused the trouble.
we still keep watching this issue but hopefully noone experiences bad
"freezes" anymore. (/me crosses fingers)
|
|
closes #1075142
|
|
|
|
the raisAndFocus after the sendToWorkspace makes problems, dunno why exactly
so this is still an open issue imho.
|
|
|
|
disable title of the windowmenu when called from titlebar
|
|
|
|
|
|
|
|
|
|
|
|
fix possible memleak with XineramaQueryScreens:
"Returned array should be free with XFree()" (from Xinerama.h)
|
|
|
|
Paradise Poker client
|
|
#1052534, close #1048000
|
|
|
|
at startup of fluxbox
should close #1067582, #1067580, #1060912
|
|
|
|
primary problem was to use utf8 when in fact the FontSet wasnt
utf8.
|