thanks

nice one jed - where are you getting that wallpaper?

got i3 and some multimedia set up; need to figure out a glitch in the fonts (not shown in this shot)

yad is a fork of zenity for those that haven't heard of it - I think zenity went a while without a maintainer so someone forked it.

The default SlackBuild installs yad to /usr/bin so a simple -

sudo ln -s /usr/bin/yad /usr/bin/zenity

does the trick.

As far as I know, the two are nearly 100% compatable.

Just used this to burn the latest vsido iso; just confirming that the script works with yad (on slackware) installed. Just had to make a symlink zenity to yad.

that sort of ram usage something new for chromium?

replaced graphics card and did some distro hopping - we'll see how long this lasts (don't realize how much you like apt until you no longer have it):

That syntax is wrong. You can have -

Mod4 d :Lower
Mod4 Shift d :MacroCmd {Raise} {Focus}

Something like you have will need to be written as a key chain like emacs -

modifiers-1 key-1 modifiers-2 key-2 :'command' [arguments ...]

Fluxbox work in progress -       and  i3

   

Add these (or similar) key bindings to ~/fluxbox/keys -:

Mod1 Shift F6 :Lower
Mod1 Shift F7 :MacroCmd {Raise} {Focus}

You will perform the action on the active - in this case maximized or full screen - window to lower it below lxpanel or raise it above lxpanel. In fluxbox, lxpanel doesn't grab focus so the bindings will not effect it. The MacroCmd runs the two commands in sequence so the window will grab focus after it is raised.

You can change the keys to whatever fits your scheme.

If you prefer a mouse -

OnWindow Mod4 Mouse3 :Lower
OnWindow Mod4 Mouse2 :MacroCmd {Raise} {Focus}[/code]

Always verify that you're not making double entries in the ~/fluxbox/keys file after you make custom edits; fluxbox will still run but key bindings may get a bit wonky.

Your other option would be to use the native fluxbox toolbar with the "autohide" and "maximize over" configurations. You could configure lxpanel with a menu and launcher (+ systray, clock if those are not part of the fluxbox toolbar) if you still want those items available.

@vastone -

You're welcome

This in the rc.xml - toward the end where the per-app settings are written -

  <application class="lxpanel">
    <desktop>all</desktop>
    <layer>below</layer>
  </application>

should give the same behavior in openbox; I still need to test it on my other computer that has openbox installed. Openbox layers are - above, normal, or below. A setting of normal or below will allow maximized windows to cover lxpanel. Setting also makes lxpanel sticky across all desktops.

May need/want to uncheck the dock and reserved space boxes in the lxpanel configuration; let openbox control the strut policy for the panels.

Edit - This works for openbox; assign per-app settings to lxpanel then un-check the dock and reserved space settings to allow maximized windows to cover lxpanel. The Margins settings in obconf can be used if you want the panel visible - control the strut policy from openbox.

Golfing in the rain

That is how I interpret it - lxpanel is set either above or below other windows.

Have you checked lxpanel behavior with openbox?
edit - tried with openbox, same behavior.

Tinkering with it last night (see edited post above) it appears that lxpanel resides in Layer 6 or higher with fluxbox and that fluxbox is controlling the strut policy. I actually ran into something similar relating to how fluxbox deals with window assignments (a conky with compton issue). Setting the layer for lxpanel in the apps file appears to get you where you want to go.

lxpanel version 0.6.1 - compiled from source.

actually using debian testing on my laptop as we type; seriously borked my vsido install the other day and haven't reinstalled.

edit - off to bed; best of luck amigo.

I have both -

make window managers treat the panel as a dock
reserve space and not covered by maximized windows

check and it works - max windows don't cover the panel.

Unchecking just reserve space results in a maximized window going behind the panel; unchecking just the dock option and space is still reserved.

I suspect that the reserved space option is a strut policy only - I have no idea what the difference between strut policy, dock - and apparently dockable - could be.

edit -

This is the goal -

Quotewould give me the behavior I want, which is to allow any window to cover the panel/dock.

one solution - apparently, lxpanel is coded to open in a window manager's (fluxbox anyway) top layer. You can edit the ~/.fluxbox/apps file (in your editor of choice since lxpanel does not have the window menu) and add something like -

[app] (name=panel) (class=lxpanel)
  [Layer]  {8}
[end]

the name and class I got from xprop; fluxbox layers are:

   2 - Above Dock

    4 - Dock

    6 - Top

    8 - Normal

    10 - Bottom

    12 - Desktop

put lxpanel on layer 8, 10, 12 to have it covered by maximized windows.

In a terminal -

xprop

the mouse cursor will become a cross; click on the window you want the properties, the output will be in the original terminal.

I don't think the ~/.fluxbox/slitlist is autogenerated like the ~/.fluxbox/apps file.

Use xprop to get the window class for lxpanel and edit the slitlist accordingly.

edit - nope, didn't work. I guess that the lxpanel configuration to be "treated as a dock" is different than being a dockable app.