Re: Menus

[Stuart Booth]

On Sun, 7 Sep 2003 23:33:14 +0100, "Ian B" <<a
href="/group/xAP_developer/post?postID=iYbbwtJP2XCusYqu-LQgreDvGM7dFGGaH9ZW5IZ4sS4NSaQKdHlcY4UW8WUVNa1xIWncP6y8OWXo">Ian@M...</a>>
wrote:

>Do I try and hold the menu system (or part thereof) in local memory or
try
>and update a line at a time from the PC. The answer to this little
quandary
>will dictate the level of power of the micro needed etc. I think my
biggest
>concern is speed if I don't hold at least some of the data in memory.

One of the things I love about the Slim (or at least what I've used of
it so far) is that it's rapid. Once you get used to devices like it
you probably do end up whizzing around the menu structure
automatically without thought.

I would probably then agree with you that maybe waiting for each
screen to appear would get rapidly irritating for a high frequency of
usage.

Initially I thought it might be possible to cache the immediate
next/previous screens, but a double sequence would still require a
load, and maybe a fast/slow alternating response would be even more
infuriating.

I daresay a cache would just add to the complexity and be out of the
question maybe?

How about loading a branch of the menu tree at once? So that you can
shoot down it or back up it quickly without having to load the whole
lot. There would have to be a pause as the branch was loaded
initially.

S
--
Stuart Booth
xAPFramework.net - a reusable xAP framework for .net

<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>
<a
href="/group/xAP_developer/post?postID=SQcafju0MZnnbodRVGwaCcf3jQHMnAj8msOFaJKUSMSi42jT3tBrgnkNbbezSpRk_q9_VRePkSkvuGw0Of2Lxw">stuart@x...</a>