hansm@dutecai.et.tudelft.nl (Hans Mulder) (06/11/91)
Until now I have encountered a few problems I'd like to have solutions for: 1. In my terminal emulator (uw) I can use both the Command-key and the Control-key as control key. However in sys 7 command-key:space doesn't do anything, while before (6.0.7) it mapped in Control-key:space. Because Control-key:space maps into 'Mark set' in emacs, I think I am marking a position while I am not. A subsequent 'delete-region' has disastreous consequences if you find out a day or so later. How can I get back the Command-key:space -> Control-key:space mapping. 2. I want to be able to generate (encapsulated) postscript for inclusion in LaTeX (psfig), not the postscript generated by the laserwriter driver with all the TT font definitions in it. What are the possibilities (commercial or otherwise)? Can I tell the laswerwriter driver to forget about the font definitions? 3. I have a plus/2MB, a II/8MB, and a DW in a network. I'd like to boot the plus over the network from the two by means of a floppy (800K). I heard that the LC (or classic) was able to do this. Is there a way to make my plus diskless, while still running sys 7? 4. On the plus the only fonts installed are TrueType helvetica and times. I have a deskwriter (driver 2.0) but use the TrueType fonts instead of the deskwriter fonts. When printing, all applications except for Excel 2.2a act as expected: they complain about missing DW fonts, say that the bitmapped fonts will be used and, ofcourse, end up using the TT fonts (looks perfect). However, printing from Excel (on the plus) yields the same messages, but actual bitmapped font output. But I don't have bitmapped fonts installed! Is this a memory shortage and a subsequent font substitution of invisible built-in bitmapped fonts? E.g., built-into the system to deal with menu/window titles etc., which get to be used when there is insufficient memory for the required TT font? This problem does not occur on the II. Thanks in advance. Hans Mulder hansm@dutecah.et.tudelft.nl or hans@umunhum.stanford.edu
Juha.Hyvonen@hut.fi (Juha Hyv|nen) (06/12/91)
In article <1991Jun11.101937.2303@donau.et.tudelft.nl> hansm@dutecai.et.tudelft.nl (Hans Mulder) writes: +------------------------ ! 1. In my terminal emulator (uw) I can use both the Command-key and ! the Control-key as control key. However in sys 7 ! command-key:space doesn't do anything, while before (6.0.7) it mapped ! in Control-key:space. Because Control-key:space maps into 'Mark set' ! in emacs, I think I am marking a position while I am not. A ! subsequent 'delete-region' has disastreous consequences if you ! find out a day or so later. ! How can I get back the Command-key:space -> Control-key:space mapping. !........................ Is there a KCHR resource in uw? If so, try the following (with ResEdit): 1. Copy the "KCHR" resource from uw into a (new) file (e.g. "uw keyboard"). 2. Change the file type to 'kfil'. 3. Change the file creator to 'movr'. 4. Save the changes. 5. Quit all applications (except the Finder). 6. Drag the "uw keyboard" file into the System file (not folder). Now everything (with the keyboard) should work as before. System 7 uses only the "keyboard layouts" that are in the system suitcase. Older systems could use the one in an application, too. / (.__o /_/ __/ .. ! / ! Juha.Hyvonen@hut.fi (juh@cs.hut.fi) !/ ) ! ------
bruner@sp15.csrd.uiuc.edu (John Bruner) (06/14/91)
In article <1991Jun11.101937.2303@donau.et.tudelft.nl> hansm@dutecai.et.tudelft.nl (Hans Mulder) writes: >> 1. In my terminal emulator (uw) I can use both the Command-key and >> the Control-key as control key. However in sys 7 >> command-key:space doesn't do anything, while before (6.0.7) it mapped >> in Control-key:space.... In article <JUHA.HYVONEN.91Jun12095639@sauna.hut.fi> Juha.Hyvonen@hut.fi (Juha Hyv|nen) writes: > Is there a KCHR resource in uw? If so, try the following (with ResEdit).... There is no KCHR resource in uw. [At least, there's none in v4.2, the last distributed version. My development version uses KCHR's now.] v4.2 maps the keys itself by using the keycode and modifiers to form an index into a resource-based lookup table. Unfortunately, it doesn't handle "dead keys" correctly on Macs with ADB keyboards. I believe that the problem here is that Command-Space is now reserved by Apple for the Script Manager. I don't have IM VI handy, but I believe it switches to the next script system (Command-Option-Space switches to the next keyboard layout within the current script system, I think). Thus, uw no longer sees the event and therefore is powerless to do anything about it. -- John Bruner Center for Supercomputing R&D, University of Illinois bruner@csrd.uiuc.edu (217) 244-4476