Houston, We Have A Problem

[Alejandro Tejada]

on Wed, 13 Jul 2005 
Geoff Canyon wrote:

> That's a puzzler. 

Locking the screen or hiding
the imported image produces
another puzzling behavior too.

If you hide the imported image or
lock the screen, (To hide from users
the sudden change in the screen, 
when the imported image appears in 
the first stack), the copied image to 
stack 2 turns in a black rectangle...

What is the meaning of this? 
Is Metacard using the updated screen for
this operation of copying this image?

Test this variation of Geoff Canyon's handler:

on mouseUp
  lock screen
  go stack test1
  import snapshot from rect (rect of grc 1) of window
(windowID of stack test1)
  go stack test2
  create img
  set the rect of the last img of stack "test2" to the
rect of the last img of stack "test1"
  set the imagedata of the last img of stack "test2"
to the imagedata of the last img of stack "test1"
  unlock screen
end mouseUp


Geoff Canyon wrote:

> This works in either environment:

> on mouseUp
>    go stack test1
>    import snapshot from rect (rect of grc 1) of
> window (windowID of  
> stack test1)
>    go stack test2
>    create img
> 
>    -- here's the change:
>    set the rect of the last img of stack "test2" to
> the rect of the  
> last img of stack "test1"
>    set the imagedata of the last img of stack
> "test2" to the  
> imagedata of the last img of stack "test1"
> 
> end mouseUp


Visit my site:
http://www.geocities.com/capellan2000/


		
__________________________________ 
Yahoo! Mail 
Stay connected, organized, and protected. Take the tour: 
http://tour.mail.yahoo.com/mailtour.html