[Fluxbox-users] [Feature] App maximalization on 2 monitor desktops

[Luescher Claude]

Hello,

First of all I love fluxbox, this is my window manager of choice since
10 years and I am not looking to use any of the monstrosities like
Gnome/Kde ever.
I only have a small feature request to the next version what the other
WMs can do is that when you maximalize an app like firefox (what I like
to do often when the webpage requires it then go back because I also
like to see the underlying terminals in the background) then it
maximizes it to both monitor and doesn't do that correctly either
because the top of the browser slips into an invisible area and then the
only way to get it back is to resize it with the bottom right corner and
pull the top part down.

My nvidia config is basic screen extension to 2 monitors.

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Stereo" "0"
Option "metamodes" "DVI-I-2: nvidia-auto-select +0+0,
DVI-I-3: nvidia-auto-select +1920+30"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection

Also I know this was not sent to the feature-requests list that is
because I couldn't find a subscribe button for it on sourceforge, please
add that feature ;)

Thank you!

[Thomas Lübking]

Post by Luescher Claude
like to see the underlying terminals in the background) then it
maximizes it to both monitor and doesn't do that correctly either

We maximize across outputs?
Can you
a) please provide teh output of "xrandr -q" and
b) try the git master

Cheers,
Thomas

PS:
https://sourceforge.net/projects/fluxbox/

There's a "Join" link in the top right corner.

[Luescher Claude]

Hello,

Screen 0: minimum 8 x 8, current 3600 x 1080, maximum 8192 x 8192
DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
TV-0 disconnected (normal left inverted right x axis y axis)
DVI-I-2 connected 1920x1080+0+0 (normal left inverted right x axis y
axis) 510mm x 287mm
1920x1080 60.00*+
1680x1050 59.95
1280x1024 60.02
1280x960 60.00
1280x720 60.00
1024x768 60.00
800x600 60.32
640x480 59.94
DVI-I-3 connected 1680x1050+1920+30 (normal left inverted right x axis y
axis) 474mm x 296mm
1680x1050 59.88*+ 59.95
1600x1200 60.00
1440x900 74.98 59.89
1280x1024 75.02 60.02
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
640x480 75.00 72.81 59.94

Version:
Fluxbox 1.3.7 : (c) 2001-2015 Fluxbox Team

Latest stable, why are there so many developments happening lately that
I have to get the git?

Also It would be nice to be able to have 1 TASKBAR per monitor not a
long overlapping one. Gnome/KDE/Xfce can do this.

Post by Thomas Lübking

Post by Luescher Claude
like to see the underlying terminals in the background) then it
maximizes it to both monitor and doesn't do that correctly either

We maximize across outputs?
Can you
a) please provide teh output of "xrandr -q" and
b) try the git master
Cheers,
Thomas
https://sourceforge.net/projects/fluxbox/
There's a "Join" link in the top right corner.

[Thomas Lübking]

Post by Luescher Claude
DVI-I-2 connected 1920x1080+0+0 (normal left inverted right x axis y
axis) 510mm x 287mm
1920x1080 60.00*+
DVI-I-3 connected 1680x1050+1920+30 (normal left inverted right x axis
y axis) 474mm x 296mm
1680x1050 59.88*+ 59.95

Ok, that's an actual multiscreen setup - even with different screen.
I do not see how fluxbox could maximize across both screens and
cannot recall this ever happened to me.

Does this affect all clients or only specific ones?
What dimensions does the maximized window take (notably the height)
Can you dump xprop and xwininfo of such window?
And please also attach your ~/.fluxbox/init

Post by Luescher Claude
Why are there so many developments happening lately
that I have to get the git?

Tremendously long list of open bugs and feature requests that needed to
be shrinked. But actually the code is lingering around there for a year.

Post by Luescher Claude
Also It would be nice to be able to have 1 TASKBAR per monitor not a
long overlapping one. Gnome/KDE/Xfce can do this.

https://sourceforge.net/p/fluxbox/feature-requests/267/

This probably isn't implemented because the original code design is
tailored around a single toolbar and changing this will require code
modifications all over the place.

Cheers,
Thomas

[Luescher Claude]

I am now even using the latest GIT version.

Init:

session.screen0.slit.alpha: 255
session.screen0.slit.maxOver: false
session.screen0.slit.onhead: 0
session.screen0.slit.placement: RightBottom
session.screen0.slit.autoHide: false
session.screen0.slit.acceptKdeDockapps: true
session.screen0.slit.layer: Dock
session.screen0.clientMenu.usePixmap: true
session.screen0.tabs.usePixmap: true
session.screen0.tabs.maxOver: false
session.screen0.tabs.intitlebar: true
session.screen0.menu.alpha: 203
session.screen0.tab.placement: TopLeft
session.screen0.tab.width: 64
session.screen0.toolbar.maxOver: false
session.screen0.toolbar.onhead: 1
session.screen0.toolbar.tools: prevworkspace, workspacename,
nextworkspace, iconbar, systemtray, clock
session.screen0.toolbar.layer: Dock
session.screen0.toolbar.visible: true
session.screen0.toolbar.alpha: 255
session.screen0.toolbar.widthPercent: 100
session.screen0.toolbar.height: 0
session.screen0.toolbar.placement: BottomCenter
session.screen0.toolbar.autoHide: false
session.screen0.window.focus.alpha: 255
session.screen0.window.unfocus.alpha: 255
session.screen0.titlebar.left: Stick
session.screen0.titlebar.right: Minimize Maximize Close
session.screen0.iconbar.alignment: Relative
session.screen0.iconbar.iconTextPadding: 10
session.screen0.iconbar.usePixmap: true
session.screen0.iconbar.iconWidth: 128
session.screen0.iconbar.mode: {static groups} (workspace)
session.screen0.focusModel: ClickFocus
session.screen0.demandsAttentionTimeout: 500
session.screen0.clickRaises: true
session.screen0.edgeSnapThreshold: 10
session.screen0.menuDelay: 200
session.screen0.focusNewWindows: true
session.screen0.autoRaise: true
session.screen0.tabFocusModel: ClickToTabFocus
session.screen0.allowRemoteActions: false
session.screen0.colPlacementDirection: TopToBottom
session.screen0.opaqueMove: true
session.screen0.showwindowposition: false
session.screen0.tooltipDelay: 500
session.screen0.workspacewarping: true
session.screen0.noFocusWhileTypingDelay: 0
session.screen0.maxDisableMove: false
session.screen0.windowPlacement: RowMinOverlapPlacement
session.screen0.strftimeFormat: %k:%M
session.screen0.maxIgnoreIncrement: true
session.screen0.workspaceNames: Workspace 1,Workspace 2,Workspace
3,Workspace 4,
session.screen0.rowPlacementDirection: LeftToRight
session.screen0.maxDisableResize: false
session.screen0.focusSameHead: false
session.screen0.fullMaximization: false
session.screen0.workspaces: 4
session.screen0.defaultDeco: NORMAL
session.screen0.windowMenu: /home/qx/.fluxbox/windowmenu
session.tabsAttachArea: Window
session.tabPadding: 0
session.forcePseudoTransparency: false
session.menuSearch: itemstart
session.styleOverlay: /home/qx/.fluxbox/overlay
session.menuFile: ~/.fluxbox/menu
session.doubleClickInterval: 250
session.ignoreBorder: false
session.slitlistFile: /home/qx/.fluxbox/slitlist
session.styleFile: /home/qx/.fluxbox/styles/nucuze
session.keyFile: ~/.fluxbox/keys
session.appsFile: /home/qx/.fluxbox/apps
session.cacheLife: 5
session.colorsPerChannel: 4
session.cacheMax: 200
session.configVersion: 13
session.autoRaiseDelay: 250


Believe me it can:

_NET_WM_STATE(ATOM) = _NET_WM_STATE_MAXIMIZED_HORZ,
_NET_WM_STATE_MAXIMIZED_VERT
_NET_WM_USER_TIME(CARDINAL) = 13473908
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_CHANGE_DESKTOP,
_NET_WM_ACTION_SHADE, _NET_WM_ACTION_STICK, _NET_WM_ACTION_RESIZE,
_NET_WM_ACTION_MOVE, _NET_WM_ACTION_CLOSE, _NET_WM_ACTION_MINIMIZE,
_NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_MAXIMIZE_VERT,
_NET_WM_ACTION_FULLSCREEN
_NET_FRAME_EXTENTS(CARDINAL) = 0, 0, 0, 0
_NET_WM_DESKTOP(CARDINAL) = 0
_FLUXBOX_GROUP_LEFT(WINDOW): window id # 0x0
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
bitmap id # to use for icon: 0x1400016
bitmap id # of mask for icon: 0x140001e
window id # of group leader: 0x1400001
XdndAware(ATOM) = BITMAP
_NET_WM_ICON(CARDINAL) = Icon (22 x 22):
░░░░░░░░░░░░░

░░ ░ ░ ░ ░ ░ ░ ░░
░ ▒ ▒ ▒ ▒ ▒ ▒ ▒ ▒ ▒▒▒
░ ░▒░▒░▒░▒░▒░▒░▒░░▒░░░
░ ░░░░░░
░ ░░░░░▒
░ ░░ ░░░
░ ░░ ░░░░
░ ░░ ░░▒░
░ ░░ ░░░ ░
░ ░░ ░░▒ ░
░ ░░ ░░▒ ▒
░ ░░ ░░▒ ▒
░ ░ ░░▒ ▒
▒ ░ ▒░ ▒
▒ ▓░░░░ ▒
▒ ░▒░ ▒
▒ ▒
▒ ▒
▒ ▒
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓

Icon (16 x 16):
░░░░░░░
░ ░░▒▒░
░ ░ ░ ░ ░ ░░░░░▒
░ ░▒▒▒▒▒▒▒░░ ░░▒
░ ░░░░░░
░ ░░ ░░░░
░ ░░░ ░░ ░░░░
░ ░░ ░░░░
░ ░░ ░░░ ▒
░ ░ ░░░ ▒
░ ░ ▒░ ▒
▒ ▒ ░░░ ▒
▒ ▒▓░░ ▒
▒ ▒
▒░ ░▒
▓▓▓▓▓▓▓▓▓▓▓▓▓

Icon (24 x 24):

░░░░░░░░░░░░░

░░ ░ ░ ░ ░ ░ ░ ░░
░ ▒ ▒ ▒ ▒ ▒ ▒ ▒ ▒ ░▒▒
░ ░▒▒▒▒▒▒▒▒▒▒▒▒▒░░▒░░░
░ ░░░░░░
░ ░░░░░▒
░ ░ ░░░░ ░░░ ░░ ░░░░
░ ░░ ░░░░
░ ░░░░ ░ ░ ░░ ░░░░
░ ░░ ░░░ ░
░ ░░ ░░░ ░
░ ░░ ░░░ ▒
░ ░░ ░░▒ ▒
░ ░ ░░░ ▒
▒ ░ ▒░ ▒
▒ ▓░░░░ ▒
▒ ░▓░ ▒
▒ ▒
▒ ▒
▒ ▒
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓


Icon (32 x 32):




░ ░ ░ ░ ░ ░

░░░ ░░ ░░ ░░ ░░ ░░ ░░░
░ ░ ░░ ░░ ░░ ░░ ░░ ░ ░
░ ░▒░░▒░░▒░░▒░▒▒▒░▒░ ░ ░▒▒░
░ ░░░░░▒
░ ░░ ░░▒
░ ░░░░░░
░ ░░ ░░░░
░ ░░ ░░░░
░ ░░ ░░▒
░ ░░ ░░▒
░ ░░ ░░▒░
░░ ░░▒ ░
░ ░░ ░░░
░ ░ ░░░ ░
░ ░ ░▒░░░ ░
░ ▒ ░░ ░
░ ▒▓░░ ░
▒ ▒
▒ ▒
▒ ▒
▒ ▒
▓ ▓
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓





_GTK_WINDOW_OBJECT_PATH(UTF8_STRING) = "/org/gnome/gedit/window/1"
_GTK_APPLICATION_OBJECT_PATH(UTF8_STRING) = "/org/gnome/gedit"
_GTK_UNIQUE_BUS_NAME(UTF8_STRING) = ":1.3"
_GTK_APPLICATION_ID(UTF8_STRING) = "org.gnome.gedit"
_NET_WM_OPAQUE_REGION(CARDINAL) = 0, 0, 3600, 1061
_GTK_FRAME_EXTENTS(CARDINAL) = 0, 0, 0, 0
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x0, 0x0, 0x0
WM_WINDOW_ROLE(STRING) = "gedit-window-1499151234-608493-0-sheep"
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 20971532, 20971533
_NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x140000b
WM_CLIENT_LEADER(WINDOW): window id # 0x1400001
_NET_WM_PID(CARDINAL) = 3049
WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
WM_CLIENT_MACHINE(STRING) = "sheep"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified minimum size: 553 by 163
program specified base size: 0 by 0
window gravity: NorthWest
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS,
_NET_WM_PING, _NET_WM_SYNC_REQUEST
WM_CLASS(STRING) = "gedit", "Gedit"
WM_ICON_NAME(STRING) = "Unsaved Document 1 - gedit"
_NET_WM_ICON_NAME(UTF8_STRING) = "Unsaved Document 1 - gedit"
WM_NAME(STRING) = "Unsaved Document 1 - gedit"
_NET_WM_NAME(UTF8_STRING) = "Unsaved Document 1 - gedit"

Post by Thomas Lübking

Post by Luescher Claude
DVI-I-2 connected 1920x1080+0+0 (normal left inverted right x axis y
axis) 510mm x 287mm
1920x1080 60.00*+
DVI-I-3 connected 1680x1050+1920+30 (normal left inverted right x axis
y axis) 474mm x 296mm
1680x1050 59.88*+ 59.95

Ok, that's an actual multiscreen setup - even with different screen.
I do not see how fluxbox could maximize across both screens and
cannot recall this ever happened to me.
Does this affect all clients or only specific ones?
What dimensions does the maximized window take (notably the height)
Can you dump xprop and xwininfo of such window?
And please also attach your ~/.fluxbox/init

Post by Luescher Claude
Why are there so many developments happening lately that I have to get
the git?

Tremendously long list of open bugs and feature requests that needed to
be shrinked. But actually the code is lingering around there for a year.

Post by Luescher Claude
Also It would be nice to be able to have 1 TASKBAR per monitor not a
long overlapping one. Gnome/KDE/Xfce can do this.

https://sourceforge.net/p/fluxbox/feature-requests/267/
This probably isn't implemented because the original code design is
tailored around a single toolbar and changing this will require code
modifications all over the place.
Cheers,
Thomas

[Thomas Lübking]

Surprise. Gtk3-CSD ...

I cannot reproduce this here but in case, it's a gtk3 issue. (The props
suggests it's one of the windows where the toolbar is merged with the
titlebar, ie. the maximization button is provided by the client rather
than the WM, right?)

Cross test:
a) does this also happen with xterm (and I mean "xterm", not terminator
etc.)?
b) does it happen when you maximize gedit via the fluxbox taskbar entry?

Cheers,
Thomas

[Raphaël]

[...] the top of the browser slips into an invisible area

slightly off-topic, but where are the upstream bugs (Xorg,
intel/amd/nvidia, fluxbox) which keep dual-head from working pleasantly
when monitor resolutions differ?

I mean the part of the window which overlap the low-res monitor being
dynamically downscaled so that there is no more "invisible area"?

[Thomas Lübking]

Post by Raphaël

[...] the top of the browser slips into an invisible area

slightly off-topic, but where are the upstream bugs (Xorg,
intel/amd/nvidia, fluxbox) which keep dual-head from working pleasantly
when monitor resolutions differ?

"quite" off-topic ;-)
See xrandr --help, the scale feature.

[Jj]

I run two independent X sessions per monitor. The drawback being that I
could not drag windows between screens. but in 10+ years with this setup it
has never been an issue.
The benefits:
* Different resolutions no problem
* Independent workspace swithing per monitor

Caveats:
* Configs are independent (maybe a benefit), double toolbar, double clock,
and can configure behaviof for each
* No fancy moving apps between screens, but again never really had to
other than when people see dual monitor setup and want to see that piece of
magic. No such showing off.
* No xinerama, so maximization is per monitor, also full screen, which
hasn't been a problem for me
* Focus has works fine between both screens as mouse can jump over
perfectly, but if you have full screen on one monitor and click something
on the other, then it exits full screen (can vary on app)

Post by Raphaël

[...] the top of the browser slips into an invisible area

slightly off-topic, but where are the upstream bugs (Xorg,
intel/amd/nvidia, fluxbox) which keep dual-head from working pleasantly
when monitor resolutions differ?
I mean the part of the window which overlap the low-res monitor being
dynamically downscaled so that there is no more "invisible area"?
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Fluxbox-users mailing list
https://lists.sourceforge.net/lists/listinfo/fluxbox-users