Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!columbia!rutgers!cbmvax!carolyn From: carolyn@cbmvax.cbm.UUCP (Carolyn Scheppner) Newsgroups: comp.sys.amiga Subject: IFF News Message-ID: <1015@cbmvax.cbmvax.cbm.UUCP> Date: Thu, 20-Nov-86 12:34:44 EST Article-I.D.: cbmvax.1015 Posted: Thu Nov 20 12:34:44 1986 Date-Received: Thu, 20-Nov-86 23:15:46 EST Reply-To: carolyn@cbmvax.UUCP (Carolyn Scheppner) Organization: Commodore Technology, West Chester, PA Lines: 152 ======== IFF News ======== Carolyn Scheppner Amiga Technical Support In mid-September, we printed/duped a new batch of IFF docs and disks. The new batch is labeled "September 19, 1986". There were a few fixes and changes which I will describe for the benefit of those who have the April 30, 1986 release. In addition, I recently received some new material (SMUS.h, 8SVX.h, Read8svx.c) from EA. Listings of these new files are attached. FIXES/CHANGES INCORPORATED IN SEPT 30 DOCS/DISK =============================================== Document 1. Errata/Addenda from previous printing were incorporated. 2. New listing for SeeILBM. Disk 1. The source for the readpict.c module no longer "contains binary". The problem was a control character in a comment. (If you want to find it using Emacs, search for the word "via" in a comment line. I think the control character is in the word "handle" in the same line) 2. Revised source for SeeILBM. The revisions to SeeILBM were: - Polling eliminated. It now Waits for mouse activity. - Checking of window->MouseX and MouseY replaced with saving and checking of msg->MouseX and MouseY. This makes little difference to SeeILBM but is necessary when SeeILBM is used as a base for a program that can't handle its messages immediately. You want to know where the mouse was when the button was PRESSED, not where it is when you HANDLE the message. - Handling of ILBMFrames modified to use only one global frame. It should now work properly with LISTs and PROPs but I don't have any to try it out on. NEW INFORMATION SINCE SEPT 30 RELEASE ===================================== 1. EA just told me that they have defined two more SID values in SMUS: (SID value) (Next data byte) #define SID_Clef 135 0=treble,1=bass,2=alto,3=tenor #define SID_Tempo 136 beats per minute (0-255) These values are also defined in the attached SMUS.h header file. 2. I recently discovered that the IFF object modules on our distribution disk were compiled without disabling stack checking. This is fine if you're linking with LStartup.obj. However, if you plan to link with AStartup ... Amiga.lib, LC.lib, you'll have to first recompile the IFF modules using the -v flag on LC2. 3. I am expecting some new FORM and Chunk descriptions from several third-party developers. I'll let you know when I get them. Remember that ALL NEW IFF FORMS and Chunks should be registered with me. This will hopefully avoid name conflicts and unneccesary duplication of existing formats. Some suggestions when designing new FORMs and chunks - Read the docs carefully and see if an existing chunk, FORM, or CAT/LIST of FORMS will fill your needs - If you decide that you need a NEW form or chunk, call me first to find out if a suitable new one has been registered. - If you need to design a new form or chunk, follow the guidelines in the EA specs. Think ahead when designing a chunk. An IFF FORM or Chunk does not become a standard just because it's "IFF". Try to design something that will be useful to other applications and future applications of your own. If possible, discuss your form/chunk ideas with other programmers. A bulletin board is a good place to get ideas from programmers with a variety of interests. Try to include variables for pertinent features even if you are not supporting them in your current application. - Include a couple of pad variables in your chunk for future expansion. Make your chunks an even size if possible because some home-brew readers may choke on the required pad byte 0 after an odd-size chunk. - Remember to register the form/chunk with me. Do this as early as possible in your program development so that it will be possible to work in suggested modifications or additions. The information I need includes: - Your name, address, phone number - Name and description of your product, and information on any other commercial or public domain software that supports your form/chunks - Names of form/chunks and itemized description of their contents. (see IFF specs for examples) - Purposes of the form/chunks WHERE TO REGISTER FORMS/CHUNKS ============================== US MAIL Carolyn Scheppner Software Tech Support CBM 1200 Wilson Drive West Chester, PA 19380 PHONE 215-431-9180 UUCP ...{allegra,caip,ihnp4,seismo}!cbmvax!carolyn HOW TO ORDER IFF DOCS AND DISK ============================== The IFF specs and disk containing docs, source, Lattice object, and some executable examples is available for $20 from Kim Montgomery / Software Tech Support Commodore Business Machines 1200 Wilson Drive West Chester, PA. 19380 Make the check out to Commodore Business Machines, be sure to include your name and address, and ask for "IFF docs and disk". -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Carolyn Scheppner -- CBM >>Amiga Technical Support<< UUCP ...{allegra,caip,ihnp4,seismo}!cbmvax!carolyn PHONE 215-431-9180 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=