Hi from Paris,
I have the same problem too, and I have found no
solution.HC was perfect in that field. You could do
a world trip in no time at all, and not a flicker on the
screen. I also await a solution.
-Francis
"Nothing should ever be done for the first time !"
___
Thank you for reminding me about being able to extract data from
another stack without going to it first. This will help resolve some
other issues I've been running into. I appreciate your help.
Reuben Rivera
On Mar 7, 2006, at 4:59 PM, [EMAIL PROTECTED] wrote:
Hi Ruben,
I share your pain. Th
Reuben Rivera wrote:
> Thanks very much for your suggestion. The screen now looks steady
> as a rock...no more motion sickness.
Actually, the other solution is to ship Drammamine with every copy of
your stack. It saves coding.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperAct
Thanks very much for your suggestion. The screen now looks steady
as a rock...no more motion sickness. I really appreciated your help.
I had the lockScreen property set to true every other line of script
trying
to resolve the problem. Nice to have an "elegant" solution.
Reuben Rivera
On Mar
Hi Ruben,
I share your pain. This is one of the few instances where HyperCard has it
all over revolution. You can get around this somewhat in two ways.
1) You can hide any stack you don't want to see before you go to them for an
intermediate process. The problem with that is you have to remembe
Reuben Rivera wrote:
I've been working on a program that requires jumping from one stack to
another. I've tried to incorporate the lockScreen property to prevent
redrawing of the screen to keep me from sea sick while looking at the
screen and to speed up things. The problem I've run into is that
I've been working on a program that requires jumping from one stack to
another. I've tried to incorporate the lockScreen property to prevent
redrawing of the screen to keep me from sea sick while looking at the
screen and to speed up things. The problem I've run into is that
regardless
of where
