leibow@video.dec.com (MICHAEL LEIBOW) (08/08/88)
Hi, Could somebody please post a tutorial or simple example of a program that creates a superbitmap window and then draws something into it. I would like to know how to control what part of the bitmap is shown in the window. I guess the sources for the lines demo that comes with workbench 1.2 would be a pretty good start... --Mike Leibow
carolyn@cbmvax.UUCP (Carolyn Scheppner CATS) (08/11/88)
In article <8808081146.AA18836@decwrl.dec.com> leibow@video.dec.com (MICHAEL LEIBOW) writes: >Hi, > >Could somebody please post a tutorial or simple example of a program that >creates a superbitmap window and then draws something into it. I would like >to know how to control what part of the bitmap is shown in the window. Please see SuperBitMap on Fish Disk 28. I open one, draw in it, change what part you're looking at, etc. Also print it, if you wish, but using tricks which are no longer needed. (1.2 or greater printer.device can handle dumping a superbitmap window's RastPort properly, without tricks) -- ========================================================================== Carolyn Scheppner -- CATS Commodore Amiga Technical Support PHONE 215-431-9180 UUCP ...{uunet,allegra,rutgers}!cbmvax!carolyn Programmers do it a little bit better. ==========================================================================
haitex@pnet01.cts.com (Wade Bickel) (08/16/88)
leibow@video.dec.com (MICHAEL LEIBOW) writes: >waste 20 bucks and buy Rob Peck's book, "Programmers guide to the Amiga." > >Comments on Peck's book: > I read most of the book last night and believe that the book is >a good introduction to Amiga programming. It is probably in execellent way >to go before trying to understand the RKM's. BUT, disreguarding the book's >good layout, There are just as many mistakes in the examples as there is >in the RKM's. I don't have my book next to me at the moment so I can't make >too many specific examples, but I do remember: [examples deleted] >So, if you want to learn how to program the amiga, I do suggest this book >because it is easy to read, but I suggest you be very careful when typing >in any of the examples. Go over the examples with a fine toothed comb before >compiling them. If you have a lint preprocessor, you should use it on the >examples to make sure they won't bomb out. A last thing to be careful about >is the disreguard to pointer and integer types. Peck mixes pointers and >integers in almose every example. This kind of programming will not work >if you use 16 bit integers (the default for Aztec C). > > --Mike Leibow I too have Rob Pecks book(s). I found it to be of relativly little use when dealing with the low-level system. The RKM/Exec/HardwareManule and the structure definitions seem to be the only real clues to the puzzel. However I found the book quite valuable when tackling intuition, and giving a general picture of what the differnt aspects of the system software are for. I really find the weak use of TYPES in his C code irritating, especially since I sometimes translate a routine from C to M2. I have found the Benchmark Definition module listings to be one of my best sources of information. Modula-2's specificity as to where a routine is being imported from is a great aid to figuring out how unknown code works. This is even more important when tracking down structure definitions. I think C programmers would find the Benchmark manule of value even if they never were to program in M2. Thanks, Wade. UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!haitex ARPA: crash!pnet01!haitex@nosc.mil INET: haitex@pnet01.CTS.COM