Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!noao!ncar!news.miami.edu!umiami!tcwan
From: tcwan@umiami.ir.miami.edu
Newsgroups: comp.sys.mac.system
Subject: Re: Icon-related wierdness in 7.0
Message-ID: <1991May31.084046.10294@umiami.ir.miami.edu>
Date: 31 May 91 12:40:46 GMT
References: <2845F5FC.16755@orion.oac.uci.edu>
Distribution: na
Organization: Univ of Miami IR
Lines: 41

In article <2845F5FC.16755@orion.oac.uci.edu>, jgray@balboa.eng.uci.edu (Jeff Gray) writes:
> Two questions:
[first question about editing ics# using a b/w mac deleted -- I don't know the
answer :( ]

> 2)  I have a couple international keymaps and under 7.0 the SICN flags that
> used to show up in the Keyboard control panel next to the name of the keymaps
> are now gone.  Looking at the System with Resedit, the KCHR and SICN
> resources are all there and the ID numbers still match.  The strange
> thing is that I connected an external drive that was still running 6.0.7,
> and when I opened the keyboard control panel (the Sys 7.0 version),
> the SICN flags had reappeared, but went away again after disconnecting the
> external drive.  Can anyone make sense of this behavior?
> 
> Jeff Gray
> jgray@balboa.eng.uci.edu

I don't know about the external drive, but I'd hazard to guess that it booted
off the external under 6.0.7 first, so you SICNs will appear correctly?

Anyway, I discovered that keyboard flags are now of types kcs#, kcs4, kcs8.
They have the same structure as ics#, ics4, ics8. What I did was to copy the
SICN into an ics# template (select the bitmap in edit mode, copy, and paste
into the ics# bitmap editor), and colorized it to get ics4 and ics8 icons.

Then, I created kcs#, kcs4, kcs8 resources with the same ID number as those
for the icons, and opened the ics# using the HEX Editor (not as an icon!),
selected everything, copied, and pasted into the kcs#, kcs4, kcs8 resources.

Now, if only there's an easy way to convert one resource type to the other...
(any clues??) I tried looking for the ICON editor template, but I guess it's
more complicated than that. :(

Note: do this on a copy of your system!! (a floppy system?)
I'm not responsible if you crash your drive. And please don't try this if you
don't know what you're doing.

Good Luck,
T.C. Wan
Dept. of ECE,
Univ. of Miami, FL