Skip to content

14.0.0 - New 'supercontext' var created, minor bugfixes.

Compare
Choose a tag to compare
@github-actions github-actions released this 30 Oct 10:56
· 1 commit to master since this release

My friend Lenz asked me some time ago the possibility to give EBG programs a "terminal" context (e.g.: you launch your script by app menu, and xterm is launched, with your script inside, with, let's say, "dialog" mode).
Before 14.0.0 version, EBG was pretty autonomous in deciding which widget to use, and first choice is always graphical widgets (yad, zenity, kdialog, etc. etc. etc. ), nonetheless it was impossible using, let's say, "dialog" mode if you weren't already in a terminal (e.g.: xterm ): in fact, forcing supermode="dialog" in a script launched by the panel (or from a menu ) ended in a script impossible to display up.

To address this issue EBG version 14.0.0 checks and prevents this situation by using a environmental variable "supercontext", that can have only values "terminal" or "windows" (different values are ignored); in the first case (export supercontext="terminal" ) EBG simply tries to find a terminal in which launch the script, and in this way is possible use the three "console" modes, namely: "gum", "dialog" and "none". Terminal are checked one by one (xterm, mate-terminal, lxterminal, konsole, etc. )

As all EBG "supervariables" (namely "supermode", "supericon", "supertitle" ), use of "supercontext" variable is optional, and depends upon programmer's needs: so, if you want, you can happily continue using EBG without it, and letting EBG to decide everything.

Enjoy ! ;D