Hi Len,
What you describe may be caused by this bug:
<http://quality.runrev.com/qacenter/show_bug.cgi?id=7213>
Although I haven't investigated this in detail, I can imagine that the
debugger causes a callback to be sent internally before the URL
finishes loading, which means that Rev will never wait for the url to
load. At this point, there is nothing you can do about it. Wait for
the bug to be fixed.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Dutch forum: http://runrev.info/rrforum/
Benefit from our inexpensive hosting services. See http://economy-x-talk.com/server.html
for more info.
On 28 sep 2008, at 14:42, Len Morgan wrote:
Mark,
I certainly has some of the same symptoms of the bug you listed but
I can understand why the debugger might get a little confused if it
has to stop on the message declaration (on mouseUp in the case above).
I am several lines down in the handler before my breakpoint, and the
line that is giving me problems is a few lines beyond that. It was
very
consistent in skipping the rest of the handler and landing at the
line AFTER the call to the handler in the handler "above" it. It
also was
very consistently working right if I put the breakpoint AFTER the
put URL ... line. For what it's worth, the file was never downloaded
with the breakpoint before the put URL ... but always downloaded when
it was AFTER it.
len morgan
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
