1 13:42
> An: How to use LiveCode
> Betreff: Re: player object problem on Win7
>
> Well, QuickTime was the problem. Installed it and now my stack/standalone
> works.
>
> > This is why many of us have been requesting for years that the RunRev
folks
> license a media play
On 08/15/2011 02:41 PM, Nicolas Cueto wrote:
Well, QuickTime was the problem. Installed it and now my stack/standalone works.
This is why many of us have been requesting for years that the RunRev folks
license a media player technology that could be included in the engine, rather
than relyi
Well, QuickTime was the problem. Installed it and now my stack/standalone works.
> This is why many of us have been requesting for years that the RunRev folks
>license a media player technology that could be included in the engine, rather
>than relying on QuickTime.
Count me in on that request.
AFAIK, Neither LiveCode nor Windows has ever included a QuickTime installer.
In answer to your question, yes, to get the most functionality from a player,
the user must have QuickTime installed. Otherwise, playback features are quite
limited. This is why many of us have been requesting for yea
Sorry to be replying to my own question.
A Win7 installation does not include QuickTime. And I've confirmed QT
is not installed on my machine.
If this lack of QT is the source of the problem, does this mean Win7
users of my LiveCode stacks must have QuickTime already installed?
If so, argh! I h
Hi.
A stack and its standalone version work fine in WinXP but not in Win7.
The problem relates to the player object. It's filename gets set to an
url on my webserver, and the url is a reference to an MP4 video. When
the Win7 version sets the player object to the filename, both the
stack in the ID
