Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!ncrlnk!ncr-sd!crash!pro-generic.cts.com!amir
From: amir@pro-generic.cts.com (Amir Michail)
Newsgroups: comp.sys.amiga
Subject: Amiga Scroll Box
Message-ID: <4603@crash.cts.com>
Date: 13 Jul 89 04:02:36 GMT
Sender: news@crash.cts.com
Lines: 23

I would like to thank all those answering my queries about the University of
Waterloo modem policies, etc...  I've also learned that this is not the place
to ask those kinds of questions (i.e. Amiga tech...) 
 
 I am currently working on some general Amiga scroll box routines.  So
far, I use a structure very similar to the Gadget structure which allows
linked scroll boxes on the screen which are checked for input all in one go
(i.e. CheckScrollBox(&First,IntuiMessage).  However, I have a problem as to
what kind of lists I should allow.  For example, I am thinking of supporting
arrays and exec linked lists; I would like a more elegant and generalized
approach!  With the current system, not only is memory wasted (i.e. on double
links), but the user must use a special UserData structure containing pointers
to PlainText, IntuiText, and Image structures.  This wastes a lot of memory on
each entry (at least 8 bytes) since the user may wish to only have plain text
without the other two.  Any advice on this problem (or recommendations) would
be welcome as I would like to make this code public domain in the near future.

        Amir Michail


UUCP: crash!pro-generic!amir
ARPA: crash!pro-generic!amir@nosc.mil
INET: amir@pro-generic.cts.com