When slider dock made visible after hiding it for awhile(5-20min), it will hang without fail if the sound is enabled and scrolling of the items in slider dock is done. Windows will shut the it down and send a report back to Microsoft. The OS I am on now is windows vista home premium SP2
I am looking into it.
I will write again in this thread as soon as I find anything.
Just to be sure, you don't have this problem when sound is off?
sorry for the late answer, I had something important to do.
I don't seem to be able to reproduce this error.
I didn't thought the code for the sound would bug since I didn't write it.
It's really the default microsoft .net sound effect code. But I guess I was wrong.
I don't have access to window vista right now but I should be meeting with a friend who have it during this week.
I'll ask him to test a change I made in the app.
Sorry for the late reply, had things to do. Slider dock works fine when sound is disabled (being using R6 with sound checked off for the past few days without problems. Tried it with sound enabled today: launched Microsoft Office Word 2007, worked on a document for about 40 minutes and when I tried to rotate sliderdock to open up internet explorer, The dock crashed when the right arrow key was pressed. This does not happen when Sliderdock is hidden for periods of less than 2 minutes.
Thanks for your reply,
I might have found a way to fix this problem but I'll have to test it before releasing it.
In some forums where I found other developers having the same problem, the bug seems to be vista related.
In My Slider Dock Too. But it is for first instance of program when a click on icon who play sound but in second instance of program back to normal, in windows XP
For now I think it's best to not use sound if you are on vista.
I am working on the problem and will post a new version as soon as I fix it.
In case someone is wondering, I have made the fix for the sound.
I am now waiting for my friend to respond me back on whether it works on his computer correctly.
If his answer is positive I will release the new version.
Finally I have release the new version.
It include a fix to this problem, so now hopefully everything should work fine