[comp.sys.mac.apps] Superpaint weirdness with 7.0

mark@hsi86.hsi.com (Mark Sicignano) (06/06/91)

Using Superpaint 2.0a, on my LC with System 7.0, I noticed something
strange.  When I am editing a document, and I open another file, then
close the second file, my scroll bars don't return?  I can't use them,
and they aren't active.  Clicking on them does nothing.  I can scroll around
in the document using the hand tool, or by autoscrolling with another tool.

If I click the zoom box or resize the window, then the scroll bars come
back to life.  Also, if I was to cut something from the second document,
then return to paste it in the original document before I bring the scroll
bars back to life, it locks up for a while, then I bomb!  (Sorry forgot
the number :-( )

Compatibility stack said that it was supposed to be compatible... 
Any ideas out there?

-mark
-- 
Mark Sicignano                                  ...!uunet!hsi!mark
3M Health Information Systems                   mark@hsi.com

mark@hsi86.hsi.com (Mark Sicignano) (06/07/91)

In article <3744@hsi86.hsi.com> mark@hsi86.hsi.com (Mark Sicignano) writes:
>Using Superpaint 2.0a, on my LC with System 7.0, I noticed something
>strange.  When I am editing a document, and I open another file, then
>close the second file, my scroll bars don't return?  I can't use them,
>and they aren't active.  Clicking on them does nothing.  I can scroll around
>in the document using the hand tool, or by autoscrolling with another tool.

I noticed that this is also happening after I return from dialog boxes
as well.  Not just when I open another document and close it.

It's really an annoyance.  Is 2.0a the latest release?

-mark

-- 
Mark Sicignano                                  ...!uunet!hsi!mark
3M Health Information Systems                   mark@hsi.com

mason@habs11.enet.dec.com (Gary Mason) (06/08/91)

>strange.  When I am editing a document, and I open another file, then
>close the second file, my scroll bars don't return?  I can't use them,

MacWorld(?) newest issue mentions this in their compatibility table (assumed to
be derived from the Apple stack).

Cheers...Gary
mason@habs11.enet.dec.com