Re the crash, the word "APPLICATIONS" quickly appears on the screen then the error box and APPLICATIONS goes away.

Gotta go now. But first a question about usability. The launcher being a document icon is listed in the home screen after all collections, which on my KT puts it in 4th page. So to launch any program I have to hit Home, scroll 4 pages, tap launcher etc. Is there any way you could make the launcher icon sit at the very top of the home screen list? Current work-around is creating a collection named __1 (or whatever puts it at the very top of the home screen), then adding the launcher to that collection; this trims the number of steps down to hitting Home, tapping __1 then the launcher icon, etc.

It doesn't seem to be "orientation" but take a look at it anyway, because what I get is 4 entries (yes! it's working now, but more on that below) all with the same title (the shell script name) - usability issue
config.xml

In swapping some sub-folders out and back in the launcher stopped crashing, so unfortunately I can't reproduce this crash anymore. However, now when all extensions are included the launcher menu wrongly shows just your helper entries, so I'm thinking that I should be able to identify the bad guy anyhow. Will continue swapping in/out tomorrow.

A usability issue: Your 6 helper entries fill up exactly one page here, so if I try scrolling that page to look for more (non-existent in this case) entries I always end up starting one the 6 entries by mistake. I can't tell due to previous issue, but will it show scrollbars or allow scrolling when more than a pagefull of extensions is available?

It resizes the buttons to one page. it can handle up to 30 in one page.

Right. you want params on button names. maybe. Ill have a look.

If you can find what broke it then great

I told you it crashed when you got too many entries. That is more than likely the problem. Can't remember how many I did make. And did not look for the magic number, as you said it is only useable (as in readable) for so many.

Solution: Extend launcher for nested menus, or scrollable menus. I vote for both.

That is to say: Now when you click a menu item the Kindlet exits. One shot.

Thanks,

I like the new changes. Have to try them out in morning. Does that mean, that I can change the menu.json during execution of a script, and since the launcher has to be restarted, then it would read the changed menu afresh. And do we end up back on home screen?

If we do end up back in homescreen, that might be a slight inconvenience if one disables screensaver out of helper, and wants to start something else afterwards.