This posting is older than 6 months and can contain outdated information.
Phew, you're going to great lengths there ;-)
Indeed... but I get a lot of satisfaction from figuring out how to make these things work. The text-file database idea struck me like a bolt of lightning, and works extremely well - I can generate the whole menu array from the script that writes the text file; and the entirety of the Remote Buddy action deals with the results.
And, I did get the if/then blocks working within the menureturn handlers, for the most part...
Multiple on menureturn/end menureturn blocks of course will cause
problems. But using "menuname" as a way to distinguish between
several different menus should work just fine.
Wow - a third way! I didn't even think of that. Quite elegant, and cuts down on lag by only generating one portion of the menu at a time. Of course, you lose the ability to travel up and down the menu hierarchy, as you can can with a single menua array (though you could certainly replicate it with a menu item that sends back to the prior menu).
Please let me know, if
you find any issues with that methodology, so I can have a look at
and eventually fix any existing problems.
I'll let you know of any issues I discover in my experimentation.
