Motorised wrote:For the last week my patience has been worn very thin by an office junior in Tech Support. When you spend a bucket-full of money and the product fails, and you require the assistance of Tech Support you certainly do not appreciate being jerked from pillar to post or being treated like an idiot by an idiot. Or being told it’s my fault, when clearly it is not. I certainly hope somebody figures out what’s going on here before too much longer. It’s gone on for long enough.
Motorised wrote:For the last week my patience has been worn very thin by an office junior in Tech Support. When you spend a bucket-full of money and the product fails, and you require the assistance of Tech Support you certainly do not appreciate being jerked from pillar to post or being treated like an idiot by an idiot. Or being told it’s my fault, when clearly it is not. I certainly hope somebody figures out what’s going on here before too much longer. It’s gone on for long enough.
Motorised wrote:<iframe width="600" height="400" src="images/panos/haysGalleria.swf" allowfullscreen="true"></iframe>
It works but will not go to full screen.
Motorised wrote:I haven't uploaded the files to a server. When I double click on the swf file it works fine. The *.swf is being called from a web page using this code..
<div class="videoFrame">
<object width="600" height="400"> <embed src="images/panos/haysGalleria.swf" width="600" height="400" allowFullScreen="true"> </embed> </object>
</div>
The data folder is in the images/panos folder, "haysGalleriadata" is in there sitting right beside it. When I double click the swf file from within Expression web pro 4, in the folder list, it works fine. When I run the web page what I get is the image above.
Motorised wrote:When I use this code:
<iframe width="600" height="400" src="images/panos/haysGalleria.swf" allowfullscreen="true"></iframe>
It works but will not go to full screen.
Motorised wrote:What I find particularly exasperating is the fact Kolor are perfectly willing to release buggy software on unsuspecting users, and when they complain they’re told it’s their fault and that they’re doing something wrong.
Motorised wrote:Part of the obfuscation involves running the customer ragged with a series of relentless questions that have absolutely no bearing on the subject whatsoever or have either no answer or are totally unanswerable. And then have the audacity to feign surprise when the customer quite rightly gets upset, angry and frustrated.
Motorised wrote:Alexandrej, if you treated your customers with respect and not the utter contempt you seem to prefer and insist on insulting their intelligence by insisting it’s their fault your software doesn’t work as planned, then you’re going to have to expect some anger and frustration from your customers. Especially when you offer buggy software that doesn’t even have the right to be released as a beta, let alone as a finished product.
Motorised wrote:I would suggest that in this case it’s not the user that’s at fault but the software that’s got a bug and needs to be fixed.
Motorised wrote:Look at the image above and tell me it’s working perfectly and that the problem is not in the player, which incidentally is built by yourselves?
If Adobe released software that clearly didn’t work the whole world would be up in arms and Adobe would move heaven and earth to release a fix. How about you making an effort to fix this bug and stop putting the blame on the customer. Which is both deceitful and immoral.
Motorised wrote:Thank you Klaus, for your positive reply. Can you offer a solution? How about looking at the image above and telling me what the solution is?
Motorised wrote:Ok Klaus, now we're getting somewhere.
Let's assume this particular .*swf's Data folder is in the same folder as the .*swf file. And that the .*swf file has full access to its own Data folder. Why isn't it working?
Motorised wrote:Can you offer a solution? How about looking at the image above and telling me what the solution is?
Motorised wrote:As regards using the self generated code: I've found it doesn't work. It's a red herring and it leads you down the garden path to nowhere. When I asked tech support about it they suggested I should ignore the self generated code use the <object> code listed on the web site. So what's wrong with that? That works so why open a can of worms that's meaningless in the first place. If anybody can tell me the intended use for the self generated code in the html file, then I would be pleased to hear about it.
hankkarl wrote:What does the address bar in your browser show? does it contain the string "images/panos" ?
If not, you have the haysGalleriadata in the wrong place.
It may be that an iframe defines the "fullscreen" to be the size of the iframe. This article may help http://help.videojs.com/discussions/problems/120-video-in-iframe-fullscreen-not-working
Motorised wrote:I can't help thinking that if Tech Support had been a little more helpful rather than running me ragged round the block a few times, we'd all be in a much happier place now. A disgraceful situation considering the money we have to pay for their products.
python -m SimpleHTTPServer
python.exe -m SimpleHTTPServer
Users browsing this forum: No registered users and 1 guest