MX-23_fluxbox_alpha2_x64 released for testing

[siamhie]

@ceeslans I think monitor resolution might come into play with these tweaks. I'm working off a 1440 monitor so things could be much different with a 4K or 1080 (or lower) monitor.
I do have a 1080 stored away and will dig out this weekend and test it against my configuration.

But my initial issue is that only the volume tooltip and WiFi tooltip don't behave like all the other systray icons. I even had qbittorrent running (at the time of testing just now) and it behaves normally just like the apt notifier, clock and exit options.

One thing to point out, the volume and WiFi tooltips have a blue frame around the tooltip. All others don't. I'm not sure if I can easily change the icons for those two programs.


This is what works for the volume and WiFi tooltips.

Code: Select all

If panel is 35 pixels high then systray icon size needs to be minimum of 26.
If panel is 40 pixels high then systray icon size needs to be minimum of 31.
If panel is 45 pixels high then systray icon size needs to be minimum of 36.
If panel is 50 pixels high then systray icon size needs to be minimum of 41.
If panel is 55 pixels high then systray icon size needs to be minimum of 46.

[i_ri]

hello m_pav
tint2 system tray balloons
tint2rc
System tray (notification area)
systray_icon_size = 00

Signs of cooperation, size zero.

[siamhie]

hello m_pav
tint2 system tray balloons
tint2rc
System tray (notification area)
systray_icon_size = 00

Signs of cooperation, size zero.

Thanks @i_ri . That works even easier than having to remember to set the systray icon size 9 pixels smaller than the toolbar height.

When we move to beta, that will be the first thing I try.

[i_ri]

hello m_pav
new kernel. all well.

Code: Select all

  Host: ibm Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 compiler: gcc
    v: 12.2.0 Desktop: Fluxbox v: 1.3.7 dm: LightDM Distro: MX-23_fluxbox_x64
    Libretto Future 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: LENOVO product: 20428 v: Lenovo Yoga 2 11

mx-tweak 23.05 fluxbox
Other
The Use libinput driver selection can someday be removed?

[m_pav]

The Use libinput driver selection can someday be removed?

We've been in the process of moving from the older synaptics driver set to the modern libinput driver set for a while now and as synaptics did not work well for all machine types, neither will libinput, so, for some, the roles may be somewhat reversed. If you need Synaptics, go ahead and install synaptics and if you feel so inclined, make for yourself a snapshot to serve as your Live-ISO when the release goes final. In short, find and use what works best for you and your hardware.

[Jerry3904]

Excellent, thanks to both.

Will redo tomorrow.

Hmmm. I'm updating the rootMenu now with those changes but I think I'm going to have to do the work all over again once I run a new set of translations. The translations are created by an R script against a spreadsheet of translations applied to the four templates for menu-mx, appearance, settings and out-of-sight (all in mxfb-docs/tools). But now I have to introduce a string with a final element that changes for each language.

Is there a way to deal with that in the menu-mx_template?

WAIT: not sure if a *.csv will do this, but normally I could just put those 3 include strings within the spreadsheet of translations and have them end with a link to the top cell in the column where the language code is. Need to test later.

Result: Nope

[Jerry3904]

I have a hack:
--copy the header row in the spreadsheet of translations with the language codes
--add a new worksheet and paste in 3 times
--copy the basic command up to the language code like this:

Code: Select all

/usr/share/mxflux/menu-translations/appearance_

--tab down the 3 rows pasting the appropriate command in the entry box above the spreadsheet itself
--save as something like "menu-command_hack" (csv will only save the active worksheet)
--now go back to the full spreadsheet, introduce 3 rows for the commands, and paste in the results one at a time
--check carefully

[Jerry3904]

I'm seeing a problem with @Adrian's dockmaker that I have never seen before and can't solve. Occurs running updated Live on default demo account as well as on a new user "test" one. No dock after the app closes, and I'm unable to get it to show at all.

--launch Menu > Appearance > Dock > dockmaker
--click Edit and open the DefaultDock
--tab over to the quickshot icon and press "Delete this application"
--save and close

Edited script:

Code: Select all

TTIPS+=" --tooltip-text-padding     3"
TTIPS+=" --tooltip-border-size          0"
TTIPS+=" --tooltip-foreground-color #ffffff"
TTIPS+=" --tooltip-background-color #1d2324"

BACK="#1d2324"
BORDER="#1d2324"
HILITE="#1f56d9"

#commands for dock launchers


wmalauncher --command mx-tools --icon mx-tools --background-color black --border-color  --window-size 48 --hover-border-color $HILITE --hover-background-color $HILITE --tooltip-text "MX Tools" $TTIPS& sleep 0.1
wmalauncher --desktop-file custom-toolbox-mxfb.desktop --background-color  --border-color  --window-size 48 --hover-border-color $HILITE --hover-background-color $HILITE --tooltip-text "Settings manager" $TTIPS& sleep 0.1
wmalauncher --desktop-file mxfb-help.desktop --background-color  --border-color  --window-size 48 --hover-border-color $HILITE --hover-background-color $HILITE --tooltip-text "Help" $TTIPS& sleep 0.1
Type  :qa!  and press <Enter>...ndon all changes and exit Vim 19,10         Bot

Startup file is normal. Anybody else?

[Adrian]

$TTIPS needs to be quoted because it has spaces inside?

[dolphin_oracle]

terminal output is here:

Code: Select all

mx-dockmaker 
Program Version: 22.12
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

--background-color: Argument '<COLOR|GRADIENT>' is missing.
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

--background-color: Argument '<COLOR|GRADIENT>' is missing.