Anonymous
to test
BobC, I expect the primary benefit from “testing” will come from wading through, attempting to launch, all (each of) the items.
A few may not properly launch (indicating a general problem, beyond the scope of the applauncher context).
Also, because the utility is not abiding the “OnlyShowIn=” attribute, some of the launchable items may be seem “broken” when launched from this context. Example: a user visits the applauncher during an iceWM session and, if Xfce or MATE are also installed on the system, s/he sees alien items like “enable/disable compositing”.
To suppress unwanted items, we can create + use an extended XDG desktop attribute, ala “X-antixlauncher-ignore” and plant /etc/skel/ copies of .desktop files for problematic items… but such pre-seeding would only be helpful for a newly-installed O/S or newly-created user accounts.
=======================
(a follow-on thought, primarily a note-to-self)
Related to, but separate from the above, the sysadmin of a given system (or each individual user) may wish to have the ability to suppress display of selected items. Attention to providing this funcionality is not “scope creep”, IMO, and I would plan to add a right-click context menu containing a “never show this item” action. Clicking would place a copy of the targeted .desktop file (containing a postpended “X-antixlauncher-ignore=True” line) into
~/.local/share/aplications/