info-mac@uw-beaver (07/01/85)
From: Moderator John Mark Agosta <INFO-MAC-REQUEST@SUMEX-AIM.arpa>
INFO-MAC Digest Tuesday, 25 Jun 1985 Volume 3 : Issue 13
Today's Topics:
MacDeveloper electronic newsletter available
Re: C Programming Caution (Digest V3 #11)
Problems with MenuSelect (Toolbox Routine)
annoying feature in MacWrite
Macwrite problem
Re: Macwrite problem, cont...
Hex version of Mazewars programme
An interesting quote
----------------------------------------------------------------------
Date: Wed, 5 Jun 85 15:23:34 cdt
From: werner@ut-ngp.ARPA (Werner Uhrig)
Subject: MacDeveloper electronic newsletter available
From lsr@apple.UUCP
This is part 1 of MacDeveloper, an electronic magazine for Macintosh
Developers. I got this from a BBS in San Francisco; the SYSOP, Harry
Chesley, is the one responsible for editing and putting it together.
Distribution is unlimited as long a all 5 parts are distributed. (It
was originally packed into 1 file, but I separated it for easy
posting.)
The 4th section gives information about submitting articles, including
the phone number of the BBS and how to contact Harry.
This section is the cover page, table of contents, and editorial.
Larry Rosenstein Apple Computer
UUCP: {nsc, dual, voder, ios}!apple!lsr CSNET: lsr@Apple.CSNET
I forgot to mention in the first posting that the first 4 files are
MacWrite 2.2 documents using standard fonts. Therefore, they should
be readable by any Macintosh owner. Also, if you print these out on
the LaserWriter, you will need to use a 90-95% reduction in order to
get the page numbers to come out properly.
===================
[ The MacDeveloper Newsletter is posted, thanks to lsr and Werner, on
SUMEX in NEWS-MD1.HQX through NEWS-MD5.HQX It was ftp'd from NGP as
shown below. -jma ]
[ for those blessed with ignorance of the above UNIX-lingo, FTP to NGP,
change to subdirectory "public" and GET the files with names mac.MDi,
where i=1,5. Werner ]
------------------------------
Date: Wed, 19 Jun 85 23:05:48 PDT
From: ihnp4!amdahl!sjl@uw-beaver.arpa (Steve Langdon)
Subject: Re: C Programming Caution (Digest V3 #11)
In his posting: erik%ucbssl.CC@Berkeley (Erik Kilk) says:
>After spending several evenings searching for an intermittent problem
>in SimpleTools, I found it and a serious problem I bet most C
>compilers have. ... Followed by text that explains how the Megamax
string conversions can screw you up if the memory manager moves stuff
around during a toolbox call. ... >I am using Magamax C but don't
blame them for this problem, I bet the >other compilers have the same
difficulty.
Mac C from Consulair does not have this problem because Bill Duvall
was too smart to try and hid the differences between string formats.
To quote from the manual:
"Mac C does not use 'glue' routines to convert strings for those traps
which use them (there are about 20) because it would be inconsistent
with Mac C philosophy to have such hidden routines, and because this
kind of automatic conversion cannot be perpetuated through all calls,
results, packages, and routines. A 'glue' routine that performs
string conversion can always be written by the programmer."
Caveat Emptor.
Steve Langdon ...!{ihnp4,hplabs,sun,nsc}!amdahl!sjl (408)746-6970
------------------------------
Date: Mon, 24 Jun 85 14:28:09 mdt
From: oml%a@LANL.ARPA (Olaf Lubeck)
Subject: Problems with MenuSelect (Toolbox Routine)
I am new to the Mac and I have been trying to use the Toolbox
from DeSmet C. My problem is the following:
I have a procedure that interprets a menu using MenuSelect. It
works inconsistently. If I select a menu item before doing anything
else with the mouse button, MenuSelect returns the correct item
number. However, if I click the mouse in some area other than the
menubar and then subsequently click in the menubar, MenuSelect returns
0 and never pulls the menu down. MenuSelect acts as if the menu is
inactive.
Has anyone else encountered this problem? Write to me at
oml@lanl.arpa or (cmcl2 | ihnp4)!lanl!oml.
------------------------------
Date: Fri, 21 Jun 85 18:05 GMT
From: R.COHEN%LLL@LLL-MFE.ARPA
Subject: annoying feature in MacWrite
From: Ron Cohen <R.COHEN@LLL.MFENET> To: info-mac@LLL.MFENET
I've noticed an annoying feature of both old and new MacWrite: If you
cut or copy to the clipboard text adjacent to a delimiter (i.e., a
character such as (, ), [,], |, !, @, #, etc.) or the delimiter
itself, you get extra spaces when you paste it back in text. For
example, if your text includes the string [abc] and you cut the abc,
and then paste back inside the brackets, you get [ abc ]. Cut the
bracket out of the string a[b and repaste and you get a [ b. Paste it
in front of the string xyz and you get [ xyz. The same applies to
text on the right side (but not the left) of punctuation marks like
period, comma, semicolon, question mark, colon, apostrophe and quote.
Someone at Apple must have thought this through very carefully and
decided this feature would be a great convenience for typists of
straight text (it is kind of convenient if you want to copy words
inside parentheses to another part of your text without worrying about
adding spaces). But it is a pain in the neck if one is trying to edit
technical typing. I would like to find out (1) if anyone else out
there has noticed this feature and been annoyed by it; (2) does anyone
know of a fix? and (3) does anyone know why MacWrite was made to work
this way, and if it's such a great idea, why wasn't it described in
the MacWrite manual?
------------------------------
Date: 21 Jun 1985 11:53:32-EDT
From: Michael.Barton@cmu-ee-henry
Subject: Macwrite problem
I recently had the following problem with Macwrite: I had done a
resume six months ago on the original version of Macwrite. This
included sections with italics in justified paragraphs. No problem.
I'm now using Macwrite 4.5 and I converted the resume. Now the
italicized parts overwrite each other on printing. (I think this
applies to any text which is longer than 'plain text'). I went back
to my original Macwrite disk and the original version of the resume.
This old disk also has the old system folder. SAME RESULT!! Then I
rebooted with the old Macwrite and old system and it was fine.
1) What is different about running old Macwrite with the old system
from
rebooting first, then running old Macwrite with the old
system?
2) Why doesn't the new Macwrite handle italics correctly? (Rebooting
from this disk didn't fix it)
Any help appreciated.
-Mike Barton
------------------------------
Date: Friday, 21 June 1985 23:16:24 EDT
Sender: Michael.Barton@cmu-ee-henry
From: Michael.Barton@cmu-ee-henry.ARPA
Subject: Re: Macwrite problem, cont...
John,
Thanks for your interest. Here is the full sequence:
1- Macwrite4.5 with converted resume and recent System disk. The
original work was done in Seattle 10 point and the new System disk had
this font. This failed with the italicized section running off the
end of the justified line and the words overwriting each other in the
line.
2- Old Macwrite with old resume. Old Macwrite is on the original disk
I got with the Mac which has an old system on it. This is the System
and Macwrite originally used to create the resume. This failed
identically.
3- At this point the old Macwrite disk was the startup disk since I
ran Macwrite from it and it had a System on it. I then rebooted and
reran Macwrite. As far as I can see this should be no different from
#2. But this worked fine.
4- I tried inserting Macwrite4.5 with the recent System and rebooting
in analogy with #3. This failed.
It seems to be a justification problem rather than a font problem
since both systems had Seattle 10 point and in both cases it showed as
being selected with italics in the relevent section. It could also be
an Imagewriter problem since the overrunning did not appear on the
screen, only on the printed version (high quality was all I tried).
-Mike Barton
------------------------------
Date: Sat, 22 Jun 85 14:30:59 EDT
From: kevin@harvard.ARPA (Kevin Crowston)
Subject: Hex version of Mazewars programme
A while back I posted a short little assembler programme I was given
that allowed me to run Mazewars on a 128K Mac. This is the hex
version of that programme.
The programme opens up the AppleTalk resources necessary for Mazewars
and then launches a programme called MW. To use it, put it on your
Mazewars disk and rename the Mazewars programme MW. Then simply
launch this programme. It will run for a bit and then the first
Mazewars screen will appear.
Kevin Crowston
---------------
[ Find this under DEMO-MAZEWARS-LAUNCH.HQX -jma ]
------------------------------
Subject: An interesting quote
Date: 24 Jun 85 09:49:42 EST (Mon)
From: Christopher A Kent <cak@Purdue.EDU>
"Just about every computer on the market today runs Unix, except the
Mac (and nobody cares about it)."
Bill Joy
6/21/85
------------------------------
End of INFO-MAC Digest
**********************