🚀 go-pugleaf

In article <46100184@uxe.cso.uiuc.edu> leonardr@uxe.cso.uiuc.edu writes:
>FLAME ON**
>	There seems to be a number of INIT now in the bitstream that require them to
>be loaded in a certain order in relation to others.  I would just like to put up
>this little flame to INIT writers (hey I write them too, I can flame!!) that
>they don't do things that they shouldn't, so that we don't have to figure out
>which order to load things!
>FLAME OFF**

AMEN!  A good example is Moire.  Moire has bombed out on me so many times
unless I let it load first.  Another thing I wish people would standardize
is the keypress to prevent loading.  I mean come on.  Some want shift,
some want option, some want command, and Remember? even wants the
mouse button!  If you're not going to standardize to the Shift key as
I believe the majority have, then at least put in the documentation
a way to modify it with resedit to make it standard.  Since I've flamed
Remember? already, let me compliment it. When you do hold the mouse button
down to prevent loading, it comes up with it's icon with a slash through
it.  This is a wonderful idea.  Font/DA Juggler does it also.  How many
of us have 8+ inits in our system folder and we don't want to load
init xxx.  If we could see the icons slashed through as they come up, we
can load whichever we choose.

Please INIT writers, try to let users know what's going on...
* Shift key not to load (and resedit instructions to change it to any key)
* Icon for loading using ShowINIT
* Icon for not loading using modified ShowINIT
* Don't assume.  There's dozens of INITs out there.  You have no way
  of knowing what's already been changed.  Not everyone's INIT can load
  first.

Ken


Ken Hancock                        |    UUCP: isle@eleazar.dartmouth.edu
Personal Computing Ctr. Consultant |  BITNET: isle@eleazar.dartmouth.edu
__________________________________/ \____________________________________
DISCLAIMER: If people weren't so sue-happy, I wouldn't need one!