>Message: 4
>Date: Mon, 27 Aug 2001 23:19:23 +0100
>Subject: Re: New quicktime coding in GoLive 5 on Mac - crash
>From: -- <email@hidden>
>To: <email@hidden>
>
>Dear List,
> Am I alone in this?
>
> If I copy and paste the new quicktime coding from the apple developer
>pages into a HTML page in GoLive I get a lock up as soon as I return to the
>WYSIWYG display from the HTML source display.
>
> I have tried various fixes, but this always happens, I just wondered if
>anyone else was having the same problems?
>
> The 'lock up' shows as a small grey window - like an alert box, but with
>nothing in it (about 3" wide x 1" high) sat on top of the page.
>
> I even went to Christoper Manns page (see last digest), copied the
>source code from his page, pasted that into a blank GoLive window - and boom
>- same crash again.
>
> This IS a bit pf a problem for us as we have about 1,000 pages coded in
>GoLive which contain panoramas...... Help :)
>
> (For an example of how the lock up manifests itself - see
>http://www.leedsvr.co.uk/quicktime_code_golive_crash.gif )
>
> Tony Quinn
> Leeds UK
>
>--__--__--
Hi Tony,
I've been using GoLive since V4.0 and while I was able to save my files in
source mode after adding the new QT code, I just went and opened one of the
pages (which was in source mode from the previous save) and switched to
layout mode and got exactly the problem you describe.
Mac OS 8.6, GoLive 5, Quicktime 4.1.2
Looks like we have a confirmed bug.
Just found what it is specifically as well.
GoLive does not support the CLASSID attribute in the object tag! In fact it
is that attribute that causes it to crash when switching back to layout
mode.
In fact the closer I look at it, GoLive's implimentation of the OBJECT tag
is VERY VERY different to the one Apple has given us.
Here are the list of attributes for OBJECT in GoLive
width
vSpace
useMap
type
tabIndex
standby
shapes
name
hSpace
height
disabled
declare
dataSrc
dataFld
data
codeType
codeBase
code
border
archive
align
accessKey
I'm assuming codeType is supposed to be the CLASSID, but as you can see
there is a "dataSrc" attribute which I suspect is synonimous with our src
param.
I'll submit a bug report to Adobe support - however given the fact they
never provide fixes for any other bug i encounter to any of their programs
(hello photoshop 6 having it's interface default back to factory fresh if
you disconnect an external monitor from a powerbook, in addition to not
bring the layer effects dialogue back onto the main screen) i suspect that
a fix for this will be bundled with the next paid upgrade - don't get me
started on my rant about the morality of making bugfixes only available
with paid upgrades - i buy it and it doesn't work, you darn well keep
giving me free patches until it does.
Cheers.
Matthew Godden
email@hidden
intermediaface
--------------
internet media and interface design
http://www.intermediaface.com
