donV et al,
I digested the material about Dialog Fragments in the links above.
I then found it not too large a task to convert my menu code to use DFs in Ruboto-IRB.
I even developed techniques to support multi-level menus and text input.
It wasn't real pretty (involving some global variables) but it worked.
And it was compatible between Android 6 on my new LG phone and Android 4 on my tablet.
So far so good...
However, now I have a new problem!
A couple of weeks ago the LG phone auto-updated to Android 7.
(I know, maybe I should have turned off auto-update, against the provider's advice. But I was not given ANY clue about just what the update was going to do.)
The result is that now my new menu-simulating code using Dialog Fragments is broken.
In addition, Android 7 gives an error in the online tutorial here: https://github.com/ruboto/ruboto/wiki/Tutorial%3A-dialogfragment
I managed to rescue it using the Custom Dialog code example in demo-android-api.rb
But while perusing the sections in that demo file, I saw some other problems.
The example graphics demos for both Arcs and Sensors also no longer work.
Hint: the common syntax in these three broken sections is the "<" operator, for sub-classing.
I'm including a partial error trace from the Dialog Fragment demo.
The first line shows the 'ft' variable just before the new dialog is created.
So, is there a 'require' or 'java-import' I can add to still use Dialog Fragments?
Is there a general problem for inheritance in Ruboto under Android 7?
Anyone have any thoughts on continuing support for Ruboto-IRB?