[stepk]

Originally Posted by twobob

Okay... so Continuing the NEXT VERSION OF KUAL testing.

Great! Your screenies show that this version passed all tests on KT (or was it PW?).

Here is KUAL (WITH A BROKEN CONFIG FILE) so it FAILS-OVER to defaults...

Like you said, users upgrading will not get this error message.

Originally Posted by twobob

Okay... so NO CONFIG FILE [pictured]

OK. This is the same as #483.

Originally Posted by twobob

SORT BY "123" by priority, group priority first then action priority within group

OK. Of course the end result depends on the actual "priority" field value in each menu.json file. Picture 6 shows that you moved the Komic reader (or was it HUL? I can't remember) near the end of the list, and proves the point. Priority order was a user request. Priority is a numeric value, including negative numbers, default 0.

Originally Posted by twobob

SORT BY "ABC": lexicographic by group and by action name, same name groups coalesce

OK. Notice the "HELPER Landscape" has moved inside the Helper group in picture 6 vs. Picture 3 of #480/#483.

Originally Posted by twobob

Now SORT BY "abc" lexicographic by group, names within each group do not move

This is the default, like #480.

Originally Posted by twobob

So to recap IN THE NEXT VERSION:

we now have for sorting options:

sorting by group name; applies to -f=twolevel only. Summary of sort options
. abc lexicographic by group, names within each group do not move
. ABC lexicographic by group and by action name, same name groups coalesce
. 123 by priority, group priority first then action priority within group
(and lexicographic by group name within each priority tier)

We now have a QUIT button

And a REPLACE STORE BUTTON

FURTHER TESTING TO BE DONE
Will repeat that on a lower device...

@stepk: Thoughts on the testing appreciated - anything I missed?

Great testing and screenies, very helpful. Nothing to add. Thanks!