Rev Crash Again!

[Wouter]

On 09 Jan 2004, at 07:39, use-revolution-request at lists.runrev.com wrote:

> Message: 5
> Date: Thu, 8 Jan 2004 23:17:08 -0700
> From: Dar Scott <dsc at swcp.com>
> Subject: Re: Rev Crash Again!
> To: How to use Revolution <use-revolution at lists.runrev.com>
> Message-ID: <744A00BB-426B-11D8-8618-000A9567A3E6 at swcp.com>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
>
> On Thursday, January 8, 2004, at 07:34 PM, Wouter wrote:
>
>> When in metacard   a stacks pixmapID < >  its windowid
>> then Dar's handler is working as a charm (here at least)
>
>  From the TD on alwaysBuffer:
>
> "You can find out whether a stack is currently being buffered by
> comparing its pixmapID property to its windowID property: if these two
> properties are not the same, the stack is buffered."
>
>  From the imag007 tip at www.sonsothunder.com:
>
>    -- The next two lines force the current card image into the 
> offscreen
> buffer
>    set the alwaysBuffer of stack pStackPath to false
>    set the alwaysBuffer of stack pStackPath to true
>
> (My function only works on "this stack", so this does not apply.
> Maybe.)

If you want your crash with your "this stack" do the reverse because
   it sets a stacks pixmapID =  its windowid (no buffering as you said)


>
> Maybe a good test to add to my function and to the imag007 tip is a
> check on the pixMapID and windowMapID.  If they are the same generate
> an error and don't set the imagePixmapID.

>  set the alwaysBuffer of stack pStackPath to false
>    set the alwaysBuffer of stack pStackPath to true


>
> (If a stack is not in memory, I don't know if setting the alwaysBuffer
> does what we want.  I haven't looked at that.)

You have set the cantmodify of the stack to false
before setting its alwaysbuffer to true otherwise t
the stack will not be buffered


>
> Dar Scott

WA