by Steegy » Fri Mar 10, 2006 7:39 am
Ok, but the track that I add to the playlist is an external track (added using a new SongData object and filled the path, artist and title), that is not in the library/database. So shouldn't the 'IsntInDB' property be true then?
Adding external tracks to the Now Playing list (by drag&drop) sets the IsntInDB property to true.
However, if I add them through code (new SongData, without using UpdateDB or so), then the IsntInDB property is not true.
There are no songs with ID = -1 (or without ID) in my Songs table, and I haven't found any occurence of these external tracks in the library.
BTW: This is about the "SaveAndRestoreNowPlaying" script, that I pm'ed you about some time ago.
SongID can be -1 even if track is in database, but MM doesn't know about it yet.
When would this be then?
Anyway, that part of the code works now, but it can be useful to fully understand why this behaviour of MM is happening.
Thanks
Steegy
Ok, but the track that I add to the playlist is an external track (added using a new SongData object and filled the path, artist and title), that is not in the library/database. So shouldn't the 'IsntInDB' property be true then?
Adding external tracks to the Now Playing list (by drag&drop) sets the IsntInDB property to true.
However, if I add them through code (new SongData, without using UpdateDB or so), then the IsntInDB property is not true.
There are no songs with ID = -1 (or without ID) in my Songs table, and I haven't found any occurence of these external tracks in the library.
BTW: This is about the "SaveAndRestoreNowPlaying" script, that I pm'ed you about some time ago.
[quote]SongID can be -1 even if track is in database, but MM doesn't know about it yet.[/quote]When would this be then?
Anyway, that part of the code works now, but it can be useful to fully understand why this behaviour of MM is happening.
Thanks
Steegy