 |
|
Page 2 of 2 | |
|
|---|
leeraut
Comment #22 Wednesday, December 29, 2004 10:47 PM
Comment #22 Wednesday, December 29, 2004 10:47 PM
Yes...there is a bug in the lstPlaylist script. After that line place an "On Error Resume Next" statement. That hopefully will fix it, as it did for me. The actual problem was that I had a playlist in my WMP "My Playlists" that had been removed from the destination it was pointing to. The script bombed because it tried to access the .Name property on a nonexistant object. You should check all your playlists to make sure they are valid.
On another subject, I am running into what appears to be another bug in that the volume control slider seems to "jump out of its track". I can move it above the slider track, way to the right beyond the slider track, etc. Not sure what to do about that one yet. Have not investigated it.
On another subject, I am running into what appears to be another bug in that the volume control slider seems to "jump out of its track". I can move it above the slider track, way to the right beyond the slider track, etc. Not sure what to do about that one yet. Have not investigated it.
leeraut
Comment #23 Thursday, December 30, 2004 11:09 AM
Comment #23 Thursday, December 30, 2004 11:09 AM
Question for Tiggs:
Any reason why sending a "Command executed" from another object to the wmp_pb_back or wmp_pb_forward objects results in double execution (that is to say, the next or previous command being executed twice by the player)?
Any reason why sending a "Command executed" from another object to the wmp_pb_back or wmp_pb_forward objects results in double execution (that is to say, the next or previous command being executed twice by the player)?
rabidrobot
Comment #24 Sunday, August 21, 2005 2:54 PM
Comment #24 Sunday, August 21, 2005 2:54 PM
I am having a strange problem with this and other DesktopX players. The visualisation window is very sensitive; moving it, resizing it, etc., causes it to freeze. The visualisation graphics stop, and I can only get them to update by dragging their container. I ask about this here because I am very interested in the manner in which the vis window can be toggled with this player. I hope to incorporate a similar, but not exact, function in a player object I'm working on.
Deleting and reloading the object seems to reset the vis window temporarily.
Also, Tiggz, in comment #14 you mention not being able to change visualisations. I have been able to create a vis window with a DXPlayer->Viewer Button->Show object. The visualisation in this window can be changed with a DXPlayer->Visualisation button->Next/Previous Visualisation Effect object. If I could only control where and how large the window created by the Show object was, I would have a solution for what I'm trying to do. Although this is a different approach than yours and _Martin_'s, I was hoping you might have some suggestions.
thanks in advance
Deleting and reloading the object seems to reset the vis window temporarily.
Also, Tiggz, in comment #14 you mention not being able to change visualisations. I have been able to create a vis window with a DXPlayer->Viewer Button->Show object. The visualisation in this window can be changed with a DXPlayer->Visualisation button->Next/Previous Visualisation Effect object. If I could only control where and how large the window created by the Show object was, I would have a solution for what I'm trying to do. Although this is a different approach than yours and _Martin_'s, I was hoping you might have some suggestions.
thanks in advance
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading files.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
|
|
Page 2 of 2 | |
|
|---|
Comment #21 Sunday, November 28, 2004 5:49 PM
(null)
Line: 131
Code:
(not available)
anybody else getting this error