to WIAK, 
Thanks for the comment. You are right, good insight.
I think you understand the importance of your notes.
*
Your website is very interesting and well presented.
I will spend some time reading what you have done.
*
You say you visited my "website", the electronic engineering site.
I have been interested in non-linear analog circuits since 1975. It is Part of my background.
In 2016 I finally had opportunity to explore Non-Resonant Narrow-Pass-Band Audio Filters,
for use in my ham radio activities with morse code.
After reviews and commendations, I published two papers.
*
About the project, mixing BASH and GTK:
The biggest problem I have is that I think in terms of the abstract organization,
and do not always see the complexity.
I admit the MGR is a kludge, patched together , over time, while employed with other production projects.
I do not present it as an ideal solution to a generalized "master menu" project ;
it is only a presentation for study of a GTK 'master menu' and GTK Double-Click <button> and GTK Embedded-Images.
The "CTB" [ Cold Tar Backup ] is a more polished project, but still not perfectly 'finished'. Nothing ever is.
==================================================================
The next project is "MCI" and is a readable presentation ,
a "showcase" of the basic ideas in GUI and Embedded-Images .
I suggest, that look at my next reply for "MCI" v. 3. .
Compatibility as Ubuntu upgrades their distros is something to test about: "Change and UpDate are the only constant rule".
To that end,
I run projects in 12 Puppy-"WoofCE" distros, ( as listed in the HELP page ).
#! Running Tests are done by way of a multi-boot-menu.lst. For example:
#! iso_BionicPup32-8.0+30(BionicBeaver)220407-2305
#! iso_JammyPup32-22.04+8(Jammy Jellyfish)22123-0700
#! iso_UPupFF+D-20.12+4(Focal-Fossa)210410
#! iso_S15Pup64-22.12+1-T_220922
#! iso_Slacko-7.0_DpupS7_14.2(Slacko7)220205
#! iso_Xenial64_7.5_XL-220401
#! iso_UpupTahr-6.0.6-k4.1.30-uefi-190211-0
I maintain separation between "DEV" and "TEST" and "PRODUCTION" versions, carefully, with standard name tags. and DateTimeSeconds tag.
My data subdir are on the Hard-Drive SDA, and copies are synched/updated into at least five others (SDB,SDC,SDD,et,al) daily.
This "backup" is process is written into my "TXN" re-format program , along with subdir and Date-Time-Stamps.
I have no GTK conflict "yet", on my little systems, between BASH code and GTK code.
But several projects by other contributors downloaded from Murga have given problems,
WHICH I attribute to the authors using BASH and GTK together, ( mix and mingle style ).
AS IF these are the same language system ... which they are not !
Each language (BASH and GTK) have their own interpreter, and can work together only in specified ways.
I describe the problem as BASH / GTK "InterAction" .
I have written this Double-Click + Embedded-Image <button> version , "MGR" and "MCI" trying not to mix the two languages.
For Example.
... WHEN GTK handles the maingui selection ,
..... THEN I use a GTK type function ( such as the "msg_DC_ReStart_window" ) to accomplish a limited GTK type task written in GTK dialect.
... WHEN GTK handles a maingui "Selection" or "<Action>",
...... THEN I use the GTK variable "EXIT" (<action> EXIT:guiS2F-ReStart</action>) to fall out and down to my if/fi[] BASH routines to do the non-GTK task.
....WHEN the BASH routines call BASH SubRoutines written in the top of the source, which the BASH interpreter can read and execute .
......THEN BASH sees BASH code and executes BASH code, ONLY !
I try to keep GTK interpreter reading/executing GTK code.
I try to keep BASH interpreter reading/executing BASH code.
...
