Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!nrl-cmf!ames!pasteur!ucbvax!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Problems with Think Pascal 2.0
Message-ID: <762@husc6.harvard.edu>
Date: 5 Dec 88 12:33:38 GMT
References: 
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec/THINK Technologies, Bedford, MA
Lines: 74

In article  lipa@POLYA.STANFORD.EDU (William Lipa) writes:
>Well, here we go again. I haven't had any luck getting a response out of the
>Think technical support account (singer@harvard.harvard.edu), so I thought I'd

	That's right, why don't you smear my reputation?! Just make it sound
as though I'm ignoring you. :-)

	The account is no longer "singer", it's "siegel". Since Andrew Singer
doesn't work here anymore,  and I'm the only one who uses the account,  it was
a sensible move. Sorry for the confusion.

>1. Can't print to a LaserWriter SC in any font other than Monaco 12.

	This, as I understand, is not a Lightspeed Pascal problem. You shoud
double-check the installation of your LaserWriter SC drivers and fonts.
(This is coming to me second-hand; sorry I can't be more specific.)

>2. Occasionally when you Build Code Resource or Build Application, the linker
>   will produce an error message "Duplicate File Name", even though you've
>   specifically OK'd the overwrite of the previous version in the dialog.

	This has never happened to me, and I overwrite old programs all th
time, and I've not heard any other reports of it. You might try various
disk and directory diagnostics (Disk First Aid, HD SC Setup's disk test) to
check out the hard disk.

>3. The Build Code Resource and Build Application dialogs intermittently set
>   the default folder to the root directory of the disk, not the directory
>   of your project (which it should be if you double-clicked on the project
>   to start the compiler).

	Is there any correlation between this problem and (2)? 

>4. You can't use the tab key to get from item to item in the Set Project Type
>   dialog.

	This one we know about, but didn't get fixed for release.

>5. The editor still has the problem with leaving little bits of outlined text
>   behind when you delete in front of them. For example, if the line looked
>   like "normal OUTLINED" and you start backspacing though normal, parts of
>   OUTLINED will not move left like they should. LSP 1.0 had this bug!

	What usually gets left behind is the bottom part of the text; forcing
an incrcomp (pressing the Enter key, in other words) after you type should 
clear it up.

>6. If you ever open LightsBug, whenever you open the project again LightsBug
>   will appear, even if you had closed it before closing the project.

	This annoys me too, if that's any consolation. :-) 

>7. I had a very strange problem with a simple sorting program I wrote. Any
>   attempt to access or change the variables of the program caused a Bus
>   Error. The problem did not go away even when I created a whole new project
>   to replace the old one. The program didn't access the Toolbox at all.
>   However, now the program works fine. Very strange.

	There's no relationship between having bus errors and using the
Toolbox. I haven't the faintest idea what happened to your program...

		--Rich



Rich Siegel
Staff Software Developer
THINK Technologies Division, Symantec Corp.
Internet: siegel@endor.harvard.edu
UUCP: ..harvard!endor!siegel
Phone: (617) 275-4800 x305

Any opinions stated in this article do not necessarily reflect the views
or policies of Symantec Corporation or its employees.