.

SS-Pro , IE7

If you add sound to an object (object-editor)
it will produce a white pixel at the border
of the left-upper side of you browser screen. (preview & online)

An additional object with sound added
will produce another additional pixel

If you have 20 buttons on a page with sound
added to them...then you will get 20 (unwanted) white pixels...etc



Do below to reproduce it...takes you less then 3 minutes:


1) Make a new project.
2) Background black.
3) Red square in the middle.

now do a preview...no unwanted dots.

4) Add sound to the square obj-editor > sound

do a preview...DOTS !!!! (white)

That's all...very basic.


-----------
It's a BUG
----------


I absolutely dont get it why this was not noticed (and solved) during development.
tell your testers to watch the screen (without sunglasses)
...instead of watching the girls outside.

Next time send your beta's,alfa's and zulu's to me
Obviously i'm better at this then your own (payed) staff.

I dont want to sound negative but i again lost 1 day to figure it out.


--------------------------------
2 Workarounds untill it's solved:
--------------------------------

Put a small rectangle or something else on top (background-colored)
so it gets covered...lucky enough the dots are not in the top-layer.

Or dont use (SS internal) add-sound to objects at all



Radio

.

As I stated earlier, this is a browser issue. If you took a little time doing some research on bugs that happen in IE you would have found that when <embed> code is used in IE, it will produce a minimum 1x1 pixel area on the browser - even if there is nothing to display. This also occurs in Opera. Firefox however, does not display anything unless there is something to display.

You can get around this IE browser issue by adding some CSS code to your project. In a custom header, add:

<style type="text/css">
#SsndX { display: none; }
</style> 

where sndX is the name of your sound selection (Sound Editor->Selection tab).

.

Thanks Larry.

Let me add some (of my own) definitions
since we dont fully agree on what should be considered a bug.

Ok lets say it's a browser-issue
but its a bug also.


What is a bug:

" An error or malfunction in software that will cause something not to function properly for MOST users "

I did not have to look that up in some dictionary that's my defenition and you can't say that it is in-correct.

I could even take this further and say it's a bug if it causes problems for ANYONE
...but i know that is impossible due to non-stadardisation...etc

For me a bunch of unwanted white-pixels on a black-background is unacceptable and therefore a malfinction.

since MOST users are on IE.
since i am on IE.
since MOST of my visitors are on IE.

...it will not function properly for them and therefore it is a BUG.

You could say but there's no problems with this and that browser
Yes that might be the case...but like always
in this unfair world majority rules.

Yep ...then simply not use that "embed" function and solve it some other way.
no idea if SS uses that...obviously yes
maybe javascript can solve it ?

So a workaround should be built-in
Or better a different way to add sound to objects maybe javascript can solve it ?

Again this bug or whatever you call it should be clearly mentioned somewhere
(for as long as it's there) to prevent people like me loosing
many hours work for nothing...WHICH IS THE WHOLE POINT HERE.
i dotn want those ugly dots.

Why dont we add a bug/issue-code to every possible menu > function with known problems.
i see *85 i look it up and decide if i want this or not...could even be a tiny-winy button
that will bring you to the right issue on the list
Such list could also be online for easy updating.


What else can i say

Thanks for the workaround !


Radio

Hello Radio,

As Larry pointed out, each browser has their own idiosyncrasies. We do our best to work around them when we can. However, some browser developers post updates frequently. If we attempt a work around one, it may not work on another, or, after spending a great deal of time on our end, the browser developer may post a fix. We try to keep up as much as we can, and we believe we do a pretty good job covering all the major browsers (especially since we also have to consider mobile browsers, as well as the standard desktop browsers).

Having said that, we always appreciate hearing of a problem. And if we can, we'll do our best to tackle it. I would invite you to use our Registered User contact form to submit bugs that you have uncovered. And please be sure to include your Serial Number so we can track any problems against the product, release, and your account.

.

Thanks Derry.

But the point is that you dont want to drive your SS-pro users up the walls
when they spend hours and hours and hours to learn and finally implement a function.

Only to find out then that this function causes problems,side-effects...etc.

You could avoid that by:

1) Not implementing such function (at the cost of progress)
2) Give a warning of possible unwanted side-effects (much better)
3) Include a built-in or external workaround (even better,together with a warning)

I understand how difficult it is to keep up

But..for example if this is an "embed-audio" function issue then you should have known about it a long time ago
even i (not in the business of making internet software) heard something about it months ago.
So it takes way to long before it's repaired/updated or before a notification can be found somewhere at VM or here.

And yes i can notify you...sad enough that will also be AFTER i lost many hours.
since i dont want to bother you with something that might be some error i made myself.
I can also ask the forum or here...but thats also after the irritation and takes to much time....even 1 day is to much.


It's all about user-friendly-ness


Radio

radio,

Your complaint is still about IE's behavior - not SiteSpinner. As Derry stated, there is not way for them to anticipate every quirk in every browser on the market.

By your way of thinking, the inability of IE6 to display transparent PNGs should have caused VM to forgo the use of any PNG image format in their software until Microsoft decided to fix their browser.

Or the EULA copyright issues (recently fixed in IE versions) that caused IE users to "click to activate" a flash file would be enough to have VM forgo including a way to include flash in SiteSpinner until Microsoft settled the lawsuit.

Or maybe they should stop development for mobile support until all makers of mobile devices decide on a "standard."

What you want is nearly impossible. How can VM spend the manpower to test their product in every browser and still provide a tool that has a decent price? Have you looked at the cost of Dreamweaver or Microsoft's Expression Studio lately? Do you really think Adobe and Microsoft products have no bugs and work in all browsers?

And I have no idea why you think IE is the standard in the browser world. Just because more people use it does not make it standard. IE is as far from the W3C standard as any browser can be. Microsoft has even gone so far as to develop its own subset of javascript (a standard) called JScript.

I agree that there are things in SS and SS-Pro that need improving. But I try to work with VM tech support to fix those problems instead of complaining and bashing the product. Several people have spent many hours supporting you and have tried to come up with work-arounds to your problems so you can get your project completed. All at no cost.

Do you have a Paypal account? I would like to buy back your copy of SS-Pro since you are so dissatisfied with it. Maybe you can use the money to find a better product.

I don't see the "bug" in IE7 even following Radio's instructions with his red-rectangle test project. I do see something in Opera, Firefox and Chrome -- for me it shows mostly as a light grey vertical line about 10 pixels high at the top left corner. Even then it doesn't always show for me. I have to fiddle a bit -- e.g. minimize the browser window, then maximize again.

This will affect only pages with dark backgrounds, and even then, many visitors will not even notice -- let alone care. And there are simple workarounds.

So on a scale of 1-10, this bug rates at about 0.5. I suggest VM fix the 1-10s first -- then start on the 0.5s

.

I understand all your arguments.

But in the end...i can say nothing more then:

" You have to look at it from a users point of view "

I should not be bothered with all these problems

WYSIWYG

I understand that is a difficult task for VM.

Ok...lets forget about it..ill try to do with what i have
better then having to start all over again with some other
unknown software and throwing away 5 years of WYSIWYG

I have a new strange effect...lets see how to solve that.


Radio

This message has been edited. Last edited by: radiotechscan,