sw parameters in reverse order

[tomyjijo]

We have several shockwave objects built into our learning management
application. These objects use ini files to display user relevant learning
content. These objects no longer work in IE.

After investigation we found that SW Player 11 is reading the parameters 'sw1'
through 'sw9' in reverse order. On Mozilla, they are being read in the correct
order. This is amazing how such a turn around could happen with a new version
of the player.

Unfortunately our objects were programmed to read the parameters in their
order rather than by their name. To make things worse we do not have the
correct source code for most of the objects as they were developed in 97.

Does any one know if there is a fix for this? Any information you can provide
will be greatly appreciated.

Thanks in advance.

[Sean Wilson]

If you don't have the source, there's not much you can do - your
application /should/ have been written to utilise
externalParamValue("name") instead of externalParamValue(index)

[tomyjijo]

Thanks Sean. But that doesn't help me, right?

While I agree that not having the proper source is an error on our part, I do
not agree to your view that we shouldn't have used externalParamValue(index).
There is no way to foresee that a new version of the player would change a
basic functionality like this. ExternalParamValue(index) was a legitimate code
until SW player v11.

I think this is an unintentional bug. Please let me know if we have a way to
bring this to Adobe's notice, other than by the bug reporting on the site. I
did report this twice but there was no response.

We have more than 4000 courses affected by this and the damage is already huge.

[Sean Wilson]

> Thanks Sean. But that doesn't help me, right?

No, it doesn't sorry.

> While I agree that not having the proper source is an error on our part, I do
> not agree to your view that we shouldn't have used externalParamValue(index).
> There is no way to foresee that a new version of the player would change a
> basic functionality like this. ExternalParamValue(index) was a legitimate code
> until SW player v11.
>
> I think this is an unintentional bug. Please let me know if we have a way to
> bring this to Adobe's notice, other than by the bug reporting on the site. I
> did report this twice but there was no response.

That's the only way I'm aware of. No-one from Adobe monitors this forum.
Perhaps you could email Allen Partridge (Director Evangelist) directly:
allenp (at) adobe (dot) com