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 Non-Gausian Narrow-Pass-Band Audio Filters,
for use in my ham radio activities which are with morse code.
After development / reviews , I published two papers, recv'd 20,000 'reads' .
This very old man is happy about that.
*
About the project, regarding 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, nor am I concerned with such.
I admit the first versions of "MGR" were patched together , over time,
while we employed with other production projects.
I do not present it as an ideal solution to a generalized "master menu" project ;
MGR is only presented for study of a BASH+GTK 'master menu'
with 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 is important, as Ubuntu upgrades their distros frequently.
"Change and UpDate are the only constant rule".
...
To that end,
I run/test my projects in 22 Puppy-"WoofCE" distros,
#! Running Tests are done by way of a multi-boot-menu.lst.
Including, 32bit and 64bit, saveDATA/subdir and saveDATA.4fs formats. [/color]
...
For example:
"iso_NoblePup32-24.04-240907"
"iso_BookwormPup32-23.11-B4_v12_K:6.1 _ 64__ 231210"
"iso-bionicpup64-8.0-uefi _______ K:4 __ 64_ 231219"
"iso_BionicPup32-19.03-K5.9 __ K:5.9___ 231209"
"iso-UpupTahr-6.0.6-k4.1.30-uefi_ K:4.1 ______ 190211"
"iso-BionicPup32-8.0+30_BionicBeaver_____ 220407"
"iso_ManticPup32-23.10+1 __ K:6.1 _______ 231209"
"iso-JammyPup32-22.04+8_JammyJellyfish___ 22123"
"iso-UPupFF+D-20.12+4_Focal-Fossa________ 201210"
"iso-KineticPup32-22.10+2________________ 230604"
"iso-Slacko-7.0_DpupS7_14.2________________ 220205"
"iso-Xenial-64_7.5_XL_______________________ 220401"
"iso-S15Pup-64_22.12+1-T__________________ 220922"
"iso-Quirky_April-7.0.1F-uefi________________ 200511"
"iso_devuanpup-9.7.0-chimaera_4.0_i386____ 211206"
"iso_LxPupSc-slacko-20.01+0-T_k:64_________ 200129"
"iso_slacko64_14.2_32-674-bit_compatible___ 220227"
...
I maintain separation between "DEV" and "TEST" and "PRODUCTION" versions, carefully,
with standard name tags. and DateTimeSeconds tag.
My saveDATA entities 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.
...
We have no GTK conflict "yet", on my little systems, between BASH code and GTK code.
But several projects by other contributors which we have 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 !
Both languages (BASH and GTK) have their own interpreters,
and can work together only in specified ways.
I describe the inherent 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.
...
(end)
