comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: Expose Events (easy questions)
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Expose Events (easy questions) [message #30028 is a reply to message #30026] Thu, 04 April 2002 08:38 Go to previous messageGo to previous message
Ted Cary is currently offline  Ted Cary
Messages: 53
Registered: October 2001
Member
David Fanning wrote:

> If you want my opinion, I'd stay as far away
> from the APP_SCROLL keyword as possible.

The behavior on our Macs here has nothing to do with APP_SCROLL. I replaced
the APP_SCROLL switch with /VIEWPORT_EVENTS, /EXPOSE_EVENTS. No difference.
I've tested the program on 3 different Macs now, even an iMac, and the X field
of the expose event structure always contains the y screen size. Did anyone
else test this on a Macintosh?

I'm still wondering why the documentation says to use this technique "when
displaying images or anything else displayed in device units." It's supposed
to be "good for displaying large images because the entire image does not have
to be redrawn when viewport events are generated."

Is setting RETAIN to 0 and then handling expose and viewport motion events
really the correct what to deal with large images? The documentation makes it
sound like it's the preferred way, but nobody seems to have ever used it. I'll
write something to test if this method is really any better... it's just hard
to believe they'd make such claims in the documentation for no reason.

Thanks to everyone who took the time to test this out,

Ted Cary
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: testcase
Next Topic: Re: journal file contents

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 14:05:35 PDT 2025

Total time taken to generate the page: 0.96068 seconds