3 layer arrays not possible array [3][3] = { {1,2,3} , {4,5,6} , {7,8,9} }

EDIT: I read your post. Nevermind that last post.  

@Jon: No

@everyone else: Ok yes I agree I don't want a heavy GUI but my GUI will use a mouse but then the rest will be simple and clean. Thanks for the input. But one thing is I don't want the GUI to be like Ion or MOS or DoorCS. I want it to be different not just menus. So what I was thinking of doing is meshing the Ion type GUI with a mouse and directories and things. How's that sound.

Another update: I am thinking of adding multitasking and making an onboard contributation of 600 bytes towards it which would allow for two processes and two threads for each of those processer.( or four I forget)It would be able to be turned off by programmers who do not want it. But for programmers that do want it then it would provide a great aspect to programming. Any thoughts on that?

Major Update: I have been contemplating this and have decided I will include MOS libs as long as the app stays one page. One thing first anyone know where to find the source for them. I have looked almost everywhere and tried google.

Ok I don't get it though I have tried 3DS Max *cough* ille... *cough* and I don't get how games like Gears of War get such how gloss off of their meshes. It seems like everything homebrew never has the same gloss as say oblivion or something of the sort. How come??

EDIT: I heard you speak of not knowing a way to load the maps. Wouldn't a tilemap be sufficient where it tests the number to see what mesh to output and what region but it would have to be a 3-D tilemap or something like that. Just a suggestion. Anyways I hope this turns into the next Halo :lol:

Ok I know double posts are bad but this is an update. I have started coding the GUI which works like this.

Class
{
  WinStem, WinTopic, StartPosX, StartPosY, XOffset, YOffset, HeaderButtons, BackGroundColor
}
Basically WinStem adds it to a specific Child/Parent Class so if you defined WinStem as Desktop then it would be considered part of the desktop and destroyed when the Desktop is. If you defined a Window with WinStem desktop and then another window with the stem of the first window then when that window with WinStem as Desktop is destroyed then the second one is too. Basically like a tree. WinTopic is the header title and all the other stuff is self explanatory.

So what other GUI stuff do you guys want??

@trev: What MOS games do you have on your calc. And I don't think you guys are quite understanding how big the MOS libraries are and half of them are not used. Also I don't know sound seriously seems like overkill. Maybe some link functions would be sufficient.

@delnar: Your first objection is not really valid because TVF was made to run under Ion for 83 which I don't know why he would take the time to port it to 83 Plus and use MOS libraries and second tr1p1ea may have used MOS for Desolate but that was his first game and he admits he was a beginner when he made it and if you look at Maxcoderz 5 year aniversary which clearly uses a better grayscale engine and runs under Ion. So I think that proves my point about NexGenGS is not for the beginner programmer.

@Liazon: Yes Desolate runs on Venus on the 83

[offtopic] I finally tracked down one of the reasons that TI-Connect gives the Acces Denied Error and that is because if you try to send a .83p to your calc then it will trigger that error until you downgrade. Phew! that took me about 2 weeks to debug ever possible way to do it [/offtopic]

kk cool thanks

Input routines as in like letting the user type in a series of characters that are stored into a string. Other stuff like that for the graphscreen and the homescreen. And 3D wouldn't be overkill considering it doesn't take up that much space.

Bfr I already having a smoothscrolling tilemap implemented into NexGenGS and an aligned sprite routine.

EDIT: I also have input routines, and grayscale routines based off of RGP.