Page 1 of 1

3 Potential Bugs In 2.0

Posted: Tue Sep 13, 2005 7:31 am
by theomania
Hello,

Downloaded 2.0 and everything is looking good, but i have found 3 potential bugs you might be interested in:

1) When getting FSCommand, the argument and command seem to be back to front.

2) I cant make the FPCSetEventListener work. This may be my bad, but i'm not having any luck. Old WM_NOTIFY method still works though.

3) My mouse wheel doesnt seem working with flash scroll bars. I tried loading the flash movie into Internet Explorer, and it works fine, but not using fpc. This is using the translucent style project.

Not sure if these are bugs, or maybe im doing something wrong, but just letting you know what i've found.

Regards,

T.

Re: 3 Potential Bugs In 2.0

Posted: Tue Sep 13, 2005 8:22 am
by Softanics
Thank you!

theomania wrote:2) I cant make the FPCSetEventListener work. This may be my bad, but i'm not having any luck. Old WM_NOTIFY method still works though.


Please send me your code to support (at) flashplayercontrol.com

theomania wrote:3) My mouse wheel doesnt seem working with flash scroll bars. I tried loading the flash movie into Internet Explorer, and it works fine, but not using fpc. This is using the translucent style project.


Could you please send me this movie to support (at) flashplayercontrol.com for testing? Thank you in advance.

Will Do..

Posted: Sun Sep 18, 2005 7:10 am
by theomania
One additional bug. The 'hand' cursor appears to flick when using a translucent movie. If i remove the EX_LAYERED style, the effect dissapears.

T.

Re: 3 Potential Bugs In 2.0

Posted: Sun Sep 18, 2005 9:16 am
by Softanics
We have fixed the issues. Updated version is available for downloading.

Re: Will Do..

Posted: Tue Oct 24, 2006 4:16 pm
by Silvia Tosolini
theomania wrote:The 'hand' cursor appears to flick when using a translucent movie.


I have the same problem.
I'm using the current .net edition.
As I can read in the previous post, the bug should be fixed since september 2005, maybe it has been fixed only in dll edition, not in .net edition.
I'm opening a new thread in .net section.