Ok, now I know what this is... Sigh. The SqueakMap package is turning
into a headache here!

I think I need to do something smart about this. The current SqueakMap
package contains some loose methods to the base image. When Scott made
3.4alpha he took my base changes and put them into the image. I then
mistakenly removed them from SqueakMap package (and released as 1.01)
which worked of course for 3.4alpha but then suddenly SqueakMap didn't
work in plain old 3.2!

Then I rolled back to 1.0 (and released that as 1.02) and put those
methods back. But I botched another thing which forced me to release
1.03. Phew!

What happened then is that a fix was posted and integrated into 3.4alpha
(5108 from Brent Vukmer). Fine. But what happens when we install
SqueakMap? Arrg! We write over the fix!

Just check the versions of method FileList2>>morphicViewFolderSelector:

Soo.... Hmmmm. The Correct Thing To Do here is probably:

1. Release 1.04 of SqueakMap and remove those pesky methods just as I
did in 1.01. Plus some other fixes perhaps.
2. Revise the preamble to preinstall a little "SqueakMap basefixes 3.2"
package if it is being installed in 3.2.

I will do this tomorrow.

regards, Göran