Help for MX Fluxbox
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Working on the new MX-Fluxbox design for my old single-core 32-bit EEEPC 1000H.
The screenshot was taken on my main machine, because creating rofi themes is still more comfortable on a newer and faster machine.
The size of the launcher fits exactly the 1024x600 resolution screen of the netbook and is designed for using it in the fullscreen mode.
The theme is a variation of the "Familiar" theme I have presented before.
Last edited by kobaian on Tue Jan 17, 2023 12:28 pm, edited 1 time in total.
Wow... That looks awesome!
I wouldn't mind if such layout, configuration and choice of applications could be considered as basic concept for MX-23 Fluxbox
ceeslans wrote: Wed Jan 18, 2023 7:11 am
Wow... That looks awesome!
I wouldn't mind if such layout, configuration and choice of applications could be considered as basic concept for MX-23 Fluxbox
Thanks!
When it comes to tint2 it is worth noticing, that it looks well on a low resolution screen, where you don't have enough place for everything. On my main PC with a 1080p monitor I use the standard mx-comfort based panel on the bottom. The most annoying thing about having a non-auto-hiding tint2-panel on the top is that Fluxbox seems to ignore the fact, that the panel exists and opens the windows placing them very often underneath the panel.
The application choice is good particular for that PC. PCManFM-qt instead of Thunar, GPicView instead of gThumb. Thunar is for me too heavy and becomes with every new version less compatible with old good window-managers like Fluxbox, Openbox etc. But PCManFM-qt has its own problems like poor localization and it doesn't remember well default apps, so you have to edit the mimeapps.list file manually. So it is good for me, but I doubt it will be a good choice for default MXFB file-manager.
gThumb has its own very non-intuitive keybindings (e.g. going to next picture requires page-down instead of right-arrow) and its interface doesn't fit to the old wm's workflow well. I like GPicView for it's speed and simplicity.
When it comes to tint2 it is worth noticing, that it looks well on a low resolution screen, where you don't have enough place for everything. On my main PC with a 1080p monitor I use the standard mx-comfort based panel on the bottom. The most annoying thing about having a non-auto-hiding tint2-panel on the top is that Fluxbox seems to ignore the fact, that the panel exists and opens the windows placing them very often underneath the panel.
Have you tried changing the "panel_layer =" setting? I've read that the default value "normal" may be understood as "top." I use "panel_layer = bottom" which works for me.
Production: 5.10, 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
When it comes to tint2 it is worth noticing, that it looks well on a low resolution screen, where you don't have enough place for everything. On my main PC with a 1080p monitor I use the standard mx-comfort based panel on the bottom. The most annoying thing about having a non-auto-hiding tint2-panel on the top is that Fluxbox seems to ignore the fact, that the panel exists and opens the windows placing them very often underneath the panel.
Have you tried changing the "panel_layer =" setting? I've read that the default value "normal" may be understood as "top." I use "panel_layer = bottom" which works for me.
That's a kind of solution. But does FB respect the bottom-layered panel while maximizing windows?
The best solution will be to force the wm to treat the panel-area as "non-existent" but I don't know if it is possible. It is not only Tint2 problem, because I've got the same situation with LXQT-panel under my LXQT/Fluxbox environment. And, as far as I remember, FB ignores sometimes even its own FB-panel too.
