On Tue, Apr 27, 2010 at 11:39 AM, Per Olofsson <magervalp@gmail.com> wrote: > On Sun, Apr 25, 2010 at 9:30 AM, Ullrich von Bassewitz <uz@musoftware.de> > wrote: > >> Maybe I'm going about this all wrong! Does anyone know of a publicly > >> available windowing library for text mode on CBM machines? A port of > curses > >> for CC65 would rule the world, if there's enough resources on our > machines > >> to handle such a library. > > > > There are a two window libraries I do currently remember: Fields by > Joseph > > Rose and simplemenu by Magervalp. The first one is available from the > contrib > > directory, the second one was available from paradroid.net, but the link > on > > the page doesn't work, so you may have to contact Magervalp directly. > > index file added: > > http://paradroid.net/simplemenu/ > > IMHO forcing a refresh is the way to go, as preserving the content > underneath quickly eats up memory. > > I've just about finished my menuing. I decided to use screen buffering. On the VDC memory isn't a problem because of the unused space from $1000 to $1FFF in VDC RAM. On the VIC-II I do lose about 2k of RAM to the screen and color buffers (1000 bytes each). I do intend on support REUs in the future and I may be able to finagle the code to write out the screen to the REU which is both faster than memcpy and has the advantage of not using any system RAM in the process. I do want to look at your menu code and see how much of it I can reuse. I have displaying and hiding working, as well as key handling for the menu options and moving left-right between menus. I do not yet have the code in place for navigating up and down in menus, so that's the part I think will benefit me the most. The next major task I have is a dialog box system. I'm going to be coding up radio buttons, check boxes, text boxes, and buttons. Honestly, I'm going to be in deep waters for myself here because I've never implemented these things without events before. I *assume* that I can create a struct for the events that has a pointer to a function that would be called when the user causes an "event" on the various GUI elements. What I'm afraid of is making a system that will be bloated and eat into useful RAM, while at the same time I don't want to hard code each and every dialog in the app. -- Payton Byrd <http://www.paytonbyrd.com> <http://it.toolbox.com/blogs/paytonbyrd> ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Tue Apr 27 19:39:09 2010
This archive was generated by hypermail 2.1.8 : 2010-04-27 19:39:12 CEST