CompuServe Messages

<print the file and not be missing a lot of stuff that's off the right side of the paper!> Paper? What's that? OK. seriously. Once a function is working, I string it out horizontally. That way I don't have to scroll past a lot of code I don't need to see any more. The editor I use, KEDIT, shows me only the first 132 chars of each line. The rest only when I ask for it. I prefer to have as much "relevant" data on the screen as possible (old age effects on memory <g>) and not have to scroll up and down all the time. I'm sure you wouldn't want to see the code for "printf()" all the time. I also didn't want to split my work into more thatn one file, to keep it simple for my users. I feel bad enough that I force them to edit the source code. I was in 7-th heaven when I was able to run four simultaneous VM sessions at 96 rows by about 140 columns under OS/2 (before I retired from IBM last year). KEDIT is a PC version of XEDIT, the editor I used then, and I like most (I am as good with it, as I am with AniPro). I am slowly converting all my XEDIT macros to KEDIT and modifying them to help me work with C-code instead of REXX-code. With these macros I go from horizontal to vertical style as needed. But until I know all of C<g>, there will be manual intervention required. Until then, I'll be careful not to obscure the important sections of code. < that probably means that my AniPro experiments will come to a complete halt for 9 months until she graduates>. < … time is going to be consumed as a "support personnel" for my wife during evening, weekends, etc.> Her gain is my loss!<g>. < and make it read a DATA file – which is something that we don't want to get into- do we?> I think of the POCO program as THE data file (with some other stuff thrown in). The "compile-link-go" feature of POCO allows sophisticated users to generate data for a variety of problems by editing my C-code. Unless I develop a "particle/mass specification language" of my own, I must let the users edit the code. I just have to make sure that knowledge of C is not necessary to enter data for a useful set of particle system animations. Ed K