CompuServe Archive

Michael, Get the Programmer's guide to the Amiga, both volumes of the Amiga Programmer's Handbook, the new ROM Kernel Reference manuals (both volumes), the Hardware reference manual, and the Amiga Developer's and Intuition Manuals (if you can get a hold of them). Its expensive stuff, but you'll find yourself going…

Harry, Programmer's Guide to the Amiga by the recently deceased Rob Peck, Amiga C For Beginners (its an Abacus book), and the Kerninghan and Ritchie Language definition, its expensive but worth it. Also, pick up a copy of the ROM kernel reference manuals and the Hardware Reference manual. Good Luck.…

Don't use any of the code in Inside the Amiga with C, its buggy and badly wr written. Scott

Robert That's not true, using ^= is like using |= or += when that bit isn't already set and its like using -= if that bit is set. Also, change the UpfrontLayer(window) calls to UpfrontLayer(dummy,window->RPort->Layer) where dummy was previously declared as LONG and change BehindLayer(window) calls to BehindLayer(dummy,window->RPort->Layer) where dummy…

Change BehindLayer(window); calls in my previous message to BehindLayer(dummy,window->RPort->Layer); where dummy has been previously defined as a LONG and all UpfrontLayer(window) calls to UpfrontLayer(dummy,window->RPort->Layer) where dummy is same as before. I made a typo in the previous message, this is the reason for the fix. Scott

To turn a GIMMEZEROZERO window into a BACKDROP window simply use this code: window->Flags^=GIMMEZEROZERO; RefreshWindowFrame(window); Forbid(); window->RPort->Layer->Flags|=BACKDROP; Permit(); BehindLayer(window); window->Flags|=GIMMEZEROZERO; RefreshWindowFrame(window); and there you have a BACKDROP GIMMEZEROZERO window. to make the same window back to a normal window again use this: window->Flags^=GIMMEZEROZERO; RefreshWindowFrame(window); Forbid(); window->RPort->Layer->Flags^=BACKDROP; Permit(); UpfrontLayer(window); window->Flags|=GIMMEZEROZERO; RefreshWindowFrame(window);…

Bob, You're right. If you look at page D-55 of your ROM Kernel Reference Manual (1.3) :Includes and AutoDocs (this is the listing of intuition.h) you'll find that the flags are defined in two sections, FLAGS that are requested but not directly set and flags that can be directly set.…

Does anyone know how to change the appearance of a window whose flags you have changed after it was opened so that its new flag states are reflected. Like if I open a BACKDROP window and later negate its BACKDROPness in the Flags field how can I make Intuition recognize…

Check how you're handling the EOF signal on Comm, you may be taking it and closing without sending a NAK. Also, what's the difference between you're handling of a text and a binary transfer? If you want, upload the source you have so far to Compuserve and we can all…

Tom Thanks for being sympathetic about my situation. I had been beginning to think that everybody thought the Lattice compiler was the end-all be-all compiler. So, which do you think is better, the latest revision of Aztec or Lattice 5.0.4? THANX Scott

Mike, You forget one thing, this is the main menu, and in my program nothing is done before the main menu is displayed, therefore, it cannot be me writing to the pointer. Scott

But the problem on the Lattice compiler is that a switch statement that works fine on the IBM is not working when compiled by Lattice. It is a switch with seven cases, some of which in tern have switch statements nested inside of them. What happens is that when the…

Tom Thanx for the advice. Think I can get the vile and miserable wretch to give me my money back? Friendlily (is that a word ), Scott

Mike, The way I know that it's not a bug in my code is that that part of the program works fine on the IBM platform when compiled by Turbo C. But thank you, I think I will send it to SAS along with a nice big nastygram. Scott

Mike, Just because you have no knowledge of such a problem does not mean one does not exist. Out of the 50,000 or so Amiga programmers out there, how many do you think there are that have tried using such deeply nested logic. And then how many do you think…

but not bugs so bad that it generates completely unusable code that you can't tweak around. Scott Litvinoff

I didn't use GO, and the K+R and ANSI points were just sidepoints. Either way the compiler was in the wrong because the problem was in the handling of case statements and if statements. It just can't handle it. Too bad for Lattice but its simple, the Amiga C compiler…

Thumbs down to Lattice! What was once the largest producer of compilers for the Amigados environment has begun to go rotten. Their latest versions of the Lattice C compiler produces buggy code that often doesn't work, forcing you to tweak your code to fit tyhe compiler rather than the application.…

Usually Waite Group books are good but Inside the Amiga With C is filled with errors and is from the Waite Group, check it out, it SUCKS!

Don't even think about buying Amiga C for Advanced Programers or Inside the Amiga with C because the former is too complicated with too many listings and too few explanations and the latter is filled with errors that make no syntactical sense in C. Just another Amiga user looking out…

Could somebody please tell me what the difference between Turbo Silver 3.0 and Turbo Silver SV is? Thank You Scott Litvinoff