Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ucla-cs!sdcrdcf!burdvax!psuvax1!psuvm.bitnet!zsr
From: ZSR@PSUVMB.BITNET
Newsgroups: comp.sys.atari.st
Subject: I hates meeses to pieces...
Message-ID: <9282ZSR@PSUVMB>
Date: Mon, 5-Jan-87 12:54:42 EST
Article-I.D.: PSUVMB.9282ZSR
Posted: Mon Jan  5 12:54:42 1987
Date-Received: Wed, 7-Jan-87 18:47:44 EST
Expires: Tue, 20-Jan-87 00:00:00 EST
Lines: 43

My rodent and I have *not* been getting along very well lately.  It seems that
the GEM routine that moves the mouse (and stores the area underneath the sprite
image, as it should) saves an old version of what is under the mouse, my
application draws to the screen (changing what is under the mouse) and then,
when the mouse is moved from its present spot, the old background (without the
screen updates) is copied back in its place.  In other words, when I move the
mouse (such as for making a "rubberband line"), the mouse leaves a trail of
garbage on the screen.  If there was some way that I could find out where
GEM stores the area of the screen that is under the mouse so I could modify
that as well, the problem would be solved.

Another example:  I wrote a program that allows the user to make a rubber box
(using graf_rubberbox), and then lets him drag it around the screen.  It works
great, except when the mouse is over the outline of the box while dragging.
When this happens, GEM saves the corner of the box (which is under the mouse),
the user moves the box elsewhere, then GEM rewrites the screen that was under
the mouse, complete with the corner of the box (which is not actually located
elsewhere).  This has been *sooooo* frustrating.

There must be a way around it, because programs such as DEGAS don't have the
fragmentation problem.  Argh, beaten by small, furry animal!

On the lighter side, here is a tidbit of knowledge that I can pass on to
all.  (I learned it the hard way, of course...)  I was using a command shell
(from RIS Industries, or something?  I think I got it with the Dev. Kit or
it was public domain).  The command shell works well, but you *cannot*
use programs that use any of the forms library or file selector routines with
it.  You must drop back to the desktop to run these programs.  What I end up
doing is editing and compiling under the shell, dropping to the desk to run
the program, then warmstarting (setting the paths and such...) the command
shell again.  Trying to use the above routines (and possibly others) resulted
in a not-so-spectacular system crash (no time bombs, just nuthin').

I hope my ramblings have helped some poor soul who was about to make the
same mistake.  On the other hand, is there anyone who could help to get
me back on speaking terms with my mousie?  Please reply to the net because
this account can go POOF at any time.  Thanks in advance!
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Christopher Johnson
Penn State University

ZSR @ PSUVM, PSUVMA, PSUVMB
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^