🚀 go-pugleaf

In article <15979@dhw68k.cts.com>, thecloud@dhw68k.cts.com (Ken McLeod) writes:
> 
> For those of you who have mind-numbing quantities of INITs whose
> icons march across the screen at boot time, and would like to
> see ALL the icons displayed in neat rows, I submit the following
> improvement on the INIT recently posted by David Phillip Oster.
> 
> The following is an INIT file that will "wrap" icons displayed at
> startup if there are more than can fit across the screen. A new
> row is started ABOVE the first, and so on. To use the INIT, it
> must be in the System Folder, and must be renamed relative to
> your other INITs, so that it will run at some point BEFORE the
> icons hit the edge of the screen.
> 
> Caveat: if run before John Lim's "Moire," or Tim Maroney's "Backdrop,"
> those two INITs will crash. The temporary solution, until I either

The crash is because I've been using an old version of ShowINIT that
didnt do an InitGraf(). Here in Australia, it's pretty difficult to
get source code for all these freebie things like ShowINIT. The original
ShowINIT i got was in a resource and i had to reverse engineer it.
That's why I never knew what version of ShowINIT i was using (until
you forced me to disassemble it !).

Guess it's time to upgrade to a newer ShowINIT. It still puzzle's me
why InitGraf() is needed though, as it is initialized by INIT 31
also. Perhaps someone can explain...

ps : a quick fix to moire is to replace PROC -4064 with a newer ShowINIT.
	This will be remedied in Moire 3.0 which is under development...