🚀 go-pugleaf

In article <4487@well.UUCP> mo@well.UUCP (Maurice Weitman) writes:
>Jan, I just (even as we speak, as it were) tried it, and it
>worked fine.  Have you modified the MF bits in RSG's size -1
>resource?  Do you know about that?  I (possibly incorrectly) set
>...
>I'm not really sure what the possible ramifications are of doing
>this (with ResEdit, by the way), but after doing it with a number
>of applications, I haven't run into trouble yet.  It doesn't work
>with some programs, like PM 2.0a, but seemed to with RSG 4.0.  

This is not such a hot idea.  Most of these bits correspond to levels
of expected functionality for a given app.  Turning bits off will cause
an app to lose some of its functionality (i.e. slower switch time, loss of
backgrounding, etc.).  Turning bits on will cause apps to react incorrectly
in certain cases (a typical symptom is having the frontmost window of a layer
remain highlighted even when another layer moves to the front).

I suspect the reason that you haven't seen any problems with the apps you're
changing is that you're probably changing the wrong 'SIZE' resource.  As soon as
you change the size of an application with the Finder "Get Info" box, the
Finder makes a copy of the ('SIZE', -1) resource, names it ('SIZE', 0), and
changes the partition size there (so the original remains intact).  From then
on, the Finder uses ('SIZE', 0), so if you want to change bits you'll have to
change them here too.

Unless you are developing your own application, the only bit that it makes
sense to change is the background bit.  Even this one is unlikely to produce
startling results with most applications; they simply have nothing to "do"
in the background.  They simply waste CPU time.  However, many old
programs, especially demos, look very nice running in the background.
My personal favorite is Bill The Cat.

-Phil Goldman
Apple Computer
UUCP:{voder,nsc,sun}!apple!goldman
APPLELINK:GOLDMAN1