AW: Again - Player/Image Object "always buffer" Problems
Tiemo Hollmann TB
toolbook at kestner.de
Fri Jun 22 09:06:03 CDT 2007
I would say "looking into the source code" without having explicit details
what to look for wouldn't give more insight as looking into your source
code. You only can track it down step by step, excluding one question, what
has any relation to the player, after the other.
Just my two cents
Von: use-revolution-bounces at lists.runrev.com
[mailto:use-revolution-bounces at lists.runrev.com] Im Auftrag von Dave
Gesendet: Freitag, 22. Juni 2007 15:59
An: How to use Revolution
Betreff: Re: Again - Player/Image Object "always buffer" Problems
On 22 Jun 2007, at 13:54, Eric Chatonet wrote:
> Hi Dave,
> Le 22 juin 07 à 14:39, Dave a écrit :
>> Af far as I can tell I'm doing everything that should be done and
>> the IDE crashes out.
> How many among us have ended by finding their own mistakes?
> Actually, if you don't find anything related to your problem in BZ,
> it might signify that it's an issue related to your stack *
> somewhere you have not thought of...
> You focus on 'alwaysBuffer' when the real cause is elsewhere.
> Investigate: overlapping controls, nested groups and ALL your code,
> pending messages, etc.
> So many fields to check.
> Good luck :-)
The problem is that in the "real" system there are a number of stacks
involved, any of which could be compounding the problem/ If I call my
Library function from a simple test stack it works ok, if I call it
from the main app, it crashes. With the level of debugging tools and
the fact that it crashes, it is difficult or impossible to track down
the problem. What is needed is some to look at the source code and
see why or how setting "alwaysBuffer" causes the IDE to crash.
Thanks a lot
All the Best
use-revolution mailing list
use-revolution at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
More information about the use-livecode