Two very different systems, there is no "replication" possible.It would be nice to replicate the functionality of the panel in XFCE.
MX-Fluxbox 2.0 beta testing thread
Re: MX-Fluxbox 2.0 beta testing thread
It is always visible (icon in upper left corner) unless you removed it.
Production: MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-Fluxbox 2.0 beta testing thread
Hello Jerry3904 and Everyone
hi David P , mx-fluxbox is the same sports car as xfce, with just a different shifting pattern. Key F6 is a new habit?
Bring your panel. Or by all means call the fully loaded panel from xfce with Run xfce4-panel to participate with fluxboxwm; hide xfce panel for fluxbox session and we will never know. Other docks available to create to user preference. Launchers in mx-fluxbox are in development.
hi David P , mx-fluxbox is the same sports car as xfce, with just a different shifting pattern. Key F6 is a new habit?
Bring your panel. Or by all means call the fully loaded panel from xfce with Run xfce4-panel to participate with fluxboxwm; hide xfce panel for fluxbox session and we will never know. Other docks available to create to user preference. Launchers in mx-fluxbox are in development.
Re: MX-Fluxbox 2.0 beta testing thread
Hello Jerry,
I have managed to achieve what I wanted. There is a setting in the init file that controls whether or not a window will obscure the slit when it is maximized. On my system it was set to true. Setting it to false means that the slit "holds its territory and is always visible", as it says in the wiki. Changing this setting now means that I am able to open frequently used applications with a single click, regardless of whether I already have an application window maximized, as the dock (or launcher) resides in the slit. This is what I was trying to achieve.
The setting in question in the init file and its current setting on my machine is:
session.screen0.slit.maxOver: false
I have managed to achieve what I wanted. There is a setting in the init file that controls whether or not a window will obscure the slit when it is maximized. On my system it was set to true. Setting it to false means that the slit "holds its territory and is always visible", as it says in the wiki. Changing this setting now means that I am able to open frequently used applications with a single click, regardless of whether I already have an application window maximized, as the dock (or launcher) resides in the slit. This is what I was trying to achieve.
The setting in question in the init file and its current setting on my machine is:
session.screen0.slit.maxOver: false
Re: MX-Fluxbox 2.0 beta testing thread
Oh, DOCK! I thought you said "Doc". Now I get it.
MX21-64 XFCE & W11 on Lenovo 330S LT. MX21-KDE & MX21-XFCE on Live USB.
MX18-64 & W7, Fedora on HP Core2 DT
MX21-32 XFCE w/ MX-Fluxbox on P4HT DT w/ antiX21, SUSE Tumbleweed, Q4OS, WXP
antiX21 on Compaq PIII 1 Ghz DT, w/ Debian, MX18FB, W2K
MX18-64 & W7, Fedora on HP Core2 DT
MX21-32 XFCE w/ MX-Fluxbox on P4HT DT w/ antiX21, SUSE Tumbleweed, Q4OS, WXP
antiX21 on Compaq PIII 1 Ghz DT, w/ Debian, MX18FB, W2K
Re: MX-Fluxbox 2.0 beta testing thread
Hello Jerry3904 and Everyone
MX-19_64 mx-fluxbox
We move windows with alt+left-click-hold, so why not move icons the same way [trialed.]
Snap set false.
success with this:
table Actions
Lock: control right doubleClk
Reload: middle doubleClk
Drag: alt left hold
EndDrag: left singleClk
Execute[0]: left doubleClk
Execute[1]: right singleClk
Press key Alt+hold left mouse button to drag and drop idesk icon (if not locked.)
The exec0 with left single-click calls the command0 upon Drop.
The exec0 with left double-click no open app upon Drop, but you have double-click to execute icon normal.
The Lock toggle does work. control+right-double-click; all icons.
That brings up the mid-measure observation that the right-click edit menu is not available to an icon that has blank the command1 line.
create a command1 response on a per icon basis.
idesk is a real gem.
MX-19_64 mx-fluxbox
We move windows with alt+left-click-hold, so why not move icons the same way [trialed.]
Snap set false.
success with this:
table Actions
Lock: control right doubleClk
Reload: middle doubleClk
Drag: alt left hold
EndDrag: left singleClk
Execute[0]: left doubleClk
Execute[1]: right singleClk
Press key Alt+hold left mouse button to drag and drop idesk icon (if not locked.)
The exec0 with left single-click calls the command0 upon Drop.
The exec0 with left double-click no open app upon Drop, but you have double-click to execute icon normal.
The Lock toggle does work. control+right-double-click; all icons.
That brings up the mid-measure observation that the right-click edit menu is not available to an icon that has blank the command1 line.
create a command1 response on a per icon basis.
idesk is a real gem.