Quote:
Originally Posted by thomass
Are nested menus possible for this version?
|
Quote:
Originally Posted by stepk
no, they aren't.
|
I tend to agree to that, officially.
Unofficially? Yes nested menus are possible. At least on v0.3.2, have yet to install v0.4.0. and test there. A little feature in the parse-script that will circumvent showing of buttons if the referenced
menu.json does not exist. Putting an absolute path into
config.xml will do just fine - e.g.
/mnt/us/extensions/menu.json. Now the sub-menu folder with everything that is needed can be mounted into
/mnt/us/extensions with:
Code:
mount --bind /mnt/us/extensions/path/to/submenu /mnt/us/extensions
See how it can be a sub-directory? Beautiful, now you can restart KUAL and it only sees your submenu tree. Everything in
menu.json works now as it sits in
/mnt/us/extensions/menu.json and the hardcoded entry in
config.xml is no longer skipped. To get out of the submenu you have to define a button that runs a shell-script with this:
Code:
umount -l /mnt/us/extensions
Notice the
-l for "lazy" switch in umount? Important or it can't unmount as the dir is ironically busy by the script that tries to do the unmounting. Or alternatively run that script after each button press of the submenu, or a restart of Kindle will forget the temporary mount-binding.
Who said you can't hack functionality into KUAL?
Hopefully sometime soon there will be a native support for sub-menus.
Tested successfully on PW 5.3.3 with KUAL 0.3.2 and kterm running through KUAL.