No one is that stupid. I blame Gremlins. ;-)
Bob
On Aug 9, 2012, at 8:40 AM, J. Landman Gay wrote:
> I'm not using it. But I just found the problem. Some idiot programmer was
> putting the new content into a field twice. Who'd be that stupid?
___
u
On 8/9/12 10:29 AM, Chris Sheffield wrote:
Jacque,
Is this for mobile by chance? And in particular for iOS? If so, are
you using iphoneSetRedrawInterval somewhere? This can have negative
effects on visual effects. If you're using this, trying setting it to
0 (zero) before locking the screen, the
isual effect is done. If you're
not using this, then I'm stumped. Sorry. :-)
Chris
--
Chris Sheffield
Read Naturally, Inc.
www.readnaturally.com
On Aug 8, 2012, at 10:42 PM, J. Landman Gay wrote:
> I'm doing this:
>
> lock screen for visual effect in rect tRect
>
ock screen for visual effect in rect tRect
unlock screen with visual effect push right very fast
end doChanges
The screen would be unlocked in mainstuff and only then what occurs in
doChanges would show.
I agree this would be the most likely reason. I searched the entire
stack
Afterthought (more likely): are you sure they are not "embedding" classical
lock - unlock screen around your command ? If you have
command mainStuff
lock screen
doChanges
unlock screen
end mainStuff
command doChanges
lock screen for visual effect in rect tRect
7;show group' before unlocking ?
lock screen for visual effect in rect (the rect of graphic "Fond")
< change the file name of image "Affiche" and set its size>
show image "Affiche"
switch tsens
case "left"
unlock screen with visu
I'm doing this:
lock screen for visual effect in rect tRect
unlock screen with visual effect push right very fast
I expect to see the new content push the older content off screen.
Instead I see the content change on the card immediately, and then a
copy of the new content pushe
