lazarus@BOSCO.BERKELEY.EDU (01/14/88)
I am having trouble with using FKEYs from dialog boxes. It seems to date from my switching to the new system, but occurs with and without Multifinder. Have a text box active in a dialog box (e.g. Key Caps, SFPutFile in a word processor, etc.). I use Shift-Cmd-7 for the Date FKEY. (I put date in my filenames!) It comes out preceded by the 7. The key down event for the FKEY itself is NOT swallowed. (Similar results occur for any FKEY, even ones which produce no text.) However, no problem if I use Date in a document. BTW, I wrote an FKEY which brings up its own Modal Dialog. Can I use any resource # for the DLOG or are there guidelines similar to DA resources? andy
oster@dewey.soe.berkeley.edu (David Phillip Oster) (01/15/88)
I use the FKEY DateKey 1.1. It definately has some bugs handling 1988. As
soon as we entered the new year, it began to put a garbage character on
the front of the day. I'd write to the author to see if there is a newer
version. It also doesn't work in Macterminal.
It _is_ shareware after all. Did you pay your shareware fee?
There is a bug in the system with FKEYs: Here is how you trigger it:
(Caution, read the _entire_ directions before trying this.)
1.) Run from a System file on a floppy.
2.) eject that floppy.
2.) Insert an unformatted disk into that same drive.
3.) format the disk, so that you are looking at the "Name this disk"
dialog.
4.) trigger an FKEY.
The system will eject the new disk and prompt you for the system floppy.
5.) insert the system floppy, hit return.
The directory of the new floppy gets written onto your system floppy,
completely erasing the directory. Your system floppy has just been erased!
FLAME ON
Apple, you've got to work in your testing. Here we have a destructive
interaction between FKEYs and the Disk Iniitalizer package.
You also:
1.) can't use color quickdraw to Apple's printer drivers (Come on guys,
they are both your code, and System 4.2 is a second official release, at
least it shouldn't crash.)
2.) can't have a DA with a window on top of Macterminal when you select
"Clear Lines Off Top"
Apple, you are doing great stuff, but you've got to improve your testing.
FLAME OFF
--- David Phillip Oster --A Sun 3/60 makes a poor Macintosh II.
Arpa: oster@dewey.soe.berkeley.edu --A Macintosh II makes a poor Sun 3/60.
Uucp: {uwvax,decvax,ihnp4}!ucbvax!oster%dewey.soe.berkeley.edulazarus@BOSCO.BERKELEY.EDU (01/16/88)
The general release Date 2.? FKEY broke on my SE at work, so I didn't pay the shareware fee, I wrote my own. (Just gets port and recurses a PostEvent KeyDown for each char in the date -- probably a very stupid approach!), but I tried the FKEY / Dialog bug mentioned previously (the number key also shows up in the text) with several shareware/freeware/homebrewed FKEYS. a
dgold@apple.UUCP (David Goldsmith) (01/20/88)
In article <22582@ucbvax.BERKELEY.EDU> oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster) writes: >Apple, you've got to work in your testing. Here we have a destructive >interaction between FKEYs and the Disk Iniitalizer package. We have a very large testing organization which works very hard. No matter how large a testing organzation we have, however, or how dedicated, bugs will slip through. Thank you for reporting this one. >You also: >1.) can't use color quickdraw to Apple's printer drivers (Come on guys, >they are both your code, and System 4.2 is a second official release, at >least it shouldn't crash.) There has been some traffic on this problem on Usenet and elsewhere recently. We have tried to reproduce it several times, looked at the code, etc., and we have been unable to find any problem whatsoever. I have successfully printed color images from within both MicroSoft Word and beta copies of FullWrite. As far as I know, this has worked since system 4.1 (I was certainly printing color images before the Mac II was announced). Of course, I'm referring to printing color images in black and white; we certainly don't print them in color yet. However, there are no crashes we are aware of. There is special code in CopyBits on the Mac II which checks to see if a StdBits bottleneck is installed in an old GrafPort. If so, it converts any PixMaps to BitMaps before passing them to the bottleneck. If you have any information to the contrary, such as documents or applications which cannot print color images, please let me know via mail (I should point out that many applications, such as MacWrite and WriteNow, have a bug whereby they cannot handle PICTs greater than 32K in size, a category most color images fit into. This is strictly an application bug and unrelated to system software). -- David Goldsmith Apple Computer, Inc. AppleLink: GOLDSMITH1 UUCP: {nsc,dual,sun,voder,ucbvax!mtxinu}!apple!dgold CSNET: dgold@apple.CSNET, dgold%apple@CSNET-RELAY BIX: dgoldsmith
tecot@apple.UUCP (Ed Tecot) (01/21/88)
In article <8801140006.AA03433@ronzoni> ronzoni!lazarus (Andrew J Lazarus) writes: > >I am having trouble with using FKEYs from dialog boxes. >It seems to date from my switching to the new system, but occurs >with and without Multifinder. > >Have a text box active in a dialog box (e.g. Key Caps, >SFPutFile in a word processor, etc.). I use Shift-Cmd-7 for >the Date FKEY. (I put date in my filenames!) >It comes out preceded by the 7. The key down event >for the FKEY itself is NOT swallowed. > >(Similar results occur for any FKEY, even ones which produce no text.) I can't reproduce your problem. I don't have the Date FKEY, but I tried it with the Screen Dump FKEY that exists on the system (Cmd-Shift-4), as well as the eject FKEYs (Cmd-Shift-1 & 2). I tried it in SFPutFile (in MacWrite) and KeyCaps (which is not a dialog). I'd appreciate it if anyone who experiences this could give me more details as to the environment, such as what machine you are running on, what version of the system you are using (from About Finder...), as well as what DAs, INITs, cdevs, and FKEYs you are running. Also, what debugger (if any) you are using. Also, to make my life much easier, try setting up a floppy with only Apple software and see if it happens there as well. I suspect that some PD INIT or cdev is doing this, but you never really know. _emt