hi to all,
I am new to this ocean. Now i am working with ARM7TDMI(LPC2148) with a GLCD(256x160). I have created a menu-sub menu items like our cell phone contacts.That menu items are having figures also and each sub menu item also has its own figure.Suppose the 1st fig is in 1st position when ever we press the down button that the highlight part has to scroll down. In GLCD screen, we are displaying 4 menu items in vertical manner.
1st item figure - figure name 2nd item figure - figure name 3rd item figure - figure name 4th item figure - figure name
To display 5th item we have to shift upper most item up(just like appearing scrolling down).
So, now we have 12 menu items and each menu item has at least 10 sub menu items, again for that each sub menu item has individual working screen( In this, more calculation part is there).
Now, my problem is the size of the code. It is really a big one.So any one can help me to reduce my code size and i need certain speed also.
Thank u.
--pardhu
Then don't you think it would be better to start with simpler projects in order to gain experience?
http://www.keil.com/books
"Now, my problem is the size of the code. It is really a big one"
What you describe inherently takes quite a lot of code - there is no escaping from that!
"So any one can help me to reduce my code size"
Without seeing your code, how do you think anyone is going to be able to do that?!
You could take a look at this article: citeseerx.ist.psu.edu/.../download
Use the Map file to determine what, exactly, is consuming the most memory.
Then investigate the Optimisation options available in the compiler...
Note that menu solutions are normally fully data-driven, so you have a fixed size code that only knows about menu items and about parent/child relationschips. It then has actions for moving between previous/next menu item with potential scroll. And for selecting a menu item and either perform an action (might be done with function pointers or returning an identifier processed by a switch satement) or scrolling/switching to a sub menu. Or trying to escape back from a sub menu to the parent menu choice, potentially resulting in scrolling/redraw/...
In the end, you need code to handle all the different actions. But the menu code does not increase in size with more menu choices or even if a sub menu have yet another sub menu.