naomi@jessica.Stanford.EDU (Naomi Takeuchi) (02/13/90)
I have a message handler that uses the NewFileName XFCN.
on CopyStacki
global response, decision
if response is "Yes" then
put NewFileName ("Save stack as: ","") into newname
if newname is empty then
put "Cancelled" into decision
exit CopyStack
end if
end if
etc., etc., etc.,
end Copy stack
The problem is that the first time this handler runs the newname global
variable gets garbage, mostly squares, underscores, and paragraph symbols,
when the user clicks "Cancel" from the NewFileName dialog box. All the
documentation I've read says that clicking the "Cancel" button returns empty.
The second time this handler runs, the function behaves normally and the
global newname becomes empty when the user clicks on the Cancel button. This
only happens on Mac Plus, and the MacSE, the XFCN behaves normally on the
MacII. Can anyone enlighten me as to why this is happening? Thanks in
advance for your help.
Naomi Takeuchi
--------------tom@wcc.oz (Tom Evans) (02/20/90)
In article <9122@portia.Stanford.EDU>, naomi@jessica.Stanford.EDU (Naomi Takeuchi) writes: > I have a message handler that uses the NewFileName XFCN. > > The problem is that the first time this handler runs the newname global > variable gets garbage, mostly squares, underscores, and paragraph symbols, > when the user clicks "Cancel" from the NewFileName dialog box. Me too. Note there are probably lots of different NewFileName XFCN's around, (that's what you get when the language doesn't have the feature :-) so most of them probably don't do it. The one I've got is by Andrew Gilmartin of Brown University. Any ideas (fixes or alternate NewFileName's) anyone? --------- Tom Evans tom@wcc.oz.au | Webster Computer Corp P/L | "The concept of my 1270 Ferntree Gully Rd | existence is an Scoresby VIC 3179 | approximation" Australia | 61-3-764-1100 FAX ...764-1179 | D. Conway