Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!rutgers!faatcrl!jprad
From: jprad@faatcrl.UUCP (Jack Radigan)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Programming differences between 2.0 and 1.3
Message-ID: <1372@faatcrl.UUCP>
Date: 9 May 90 02:00:35 GMT
References: <8aDCJNG00WB7Q_wUMI@andrew.cmu.edu> <11417@cbmvax.commodore.com>
Organization: FAA Technical Center, Atlantic City NJ
Lines: 22

mks@cbmvax.commodore.com (Michael Sinz - CATS) writes:

>Ok, so not so much "NO PROBLEM"  Well, the real answer is that you should
>program by the rules and not empirically.  That is, don't just try things
>and if they work think that they are right.  Design things while looking at
>the rules.  Many of the problems others have had was where they would write
>something and try it and when it worked, it was "right."  This is not
>the case as it may just work in your system...

Ok, here's one for ya.  I've followed the rules with JR-Comm, but I've noticed
one thing with the local dealer's A3000 that I've been sneaking on to do some
testing with 2.0.

With 1.2 and 1.3, I can open a window on the Workbench screen and keep the
window title hidden, but on the A3000, whenever I'm using the Workbench and
toggle the menu button to look at the menus I have the blank title bar remain
until the screen either scrolls or I do a clear screen on it.

I'm hoping this is just a bug in the current 2.0, but just checking to make
sure....

  -jack-