Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!shelby!Portia!jessica.stanford.edu!davef From: davef@jessica.stanford.edu (David Finkelstein) Newsgroups: comp.sys.mac.hypercard Subject: What to do about > 32K of data? Message-ID: <938@Portia.Stanford.EDU> Date: 16 Mar 89 18:12:25 GMT Sender: USENET News System Reply-To: davef@jessica.stanford.edu (David Finkelstein) Distribution: usa Organization: Stanford University Lines: 35 I'm writing a stack that has to deal with > 32K of data. Basically I've got a really large text file located on a file server that I need to read in and store, so I can display any part of the file to the user. [I need to load the entire file into HyperCard because network access is too slow to read through the file to get to each line of information I want.] No problem really; I just use three fields. However, the user of the stack can choose to view any part of the text information, meaning potentiall *all* of the information, or large disjoint subsets, at once. I can't just throw the information into a scrolling field; I'm limited to 32K. The solution I have so far is to place the scroll bar of a scrolling field alongside a non-scrolling field. I also place my own buttons on top of the scroll buttons. Then as the user scrolls the scrolling field (which has the same number of lines as I wish my non-scrolling field had), I manually fill in the lines of the non-scrolling field with whatever information should be on that line (reading in from the 3 fields mentioned above). It works, but it's slow, especially since I have to watch for times when the user moves the scroll box or clicks in the scroll bar (there's a noticable delay before my non-scrolling field gets updated). Any ideas on what I can do to display > 32K of information to the user? Any ideas on how I can improve the performance of the setup I have? Thanks... *************************************************************** David Finkelstein |davef@jessica.stanford.edu Academic Information Resources | Stanford University | Just say "please."