Re: Weird behavior when writing a window

[Reeve <rfritchman@xxxxxxxxx>]

Well, Ken, opening and closing the file solves the immediate problem:
moonbounce is gone.  But the background goes blank before the next
window is written, so I have to do a little more work to make this a
pleasant user experience.

Thanks,
Reeve.

On 4/15/05, Ken Sims <mdrg5003@xxxxxxxxx> wrote:
> Hi Reeve -
> 
> >Hmmm...had the ASSUME and KEEP in place, so that's not it.  I've
> >manually positioned the subfile to overlay the moon-bounce data, and I
> >can watch the (old) data redisplay just before the window writes over
> >it.  It's like the window isn't really a window but a full screen from
> >a previous life with a new window pasted on top.
> 
> I've had this same situation.  IIRC it is putting a copy of the screen as
> it appeared when the display file in the service program is opened or
> something like that.
> 
> I got around it by opening and closing the display file in each call to the
> service program procedure.  It hurts performance but for my particular
> application it isn't used enough to be a problem.
> 
> If the window formats are in the same display file as the calling program
> another option that might work would be to share the display file's open
> data path.
> 
> --
> Ken
> http://www.ke9nr.net/
> Opinions expressed are my own and do not necessarily represent the views of
> my employer or anyone in their right mind.
> 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>