by drichm » Mon Feb 13, 2006 3:17 am
Multiple libraries is something for the more advanced user.
The most basic Multiple Library/Database support would be the equivalent of a "File -> Open (Database)" command, which most Windows programs have.
Of course, once this is added a whole can of worms is opened: such as copying information between databases for certain tracks, 'currently playing' issues, device synchronization configuration issues (which DB is used, is a device associated to a specific DB?), use a MIDI style interface? (i.e. multiple databased open simultaneously, with drag and drop support between them), etc, etc, etc...
However, "File -> Open" is all I need, and opening a new DB can close the currently open one. I could imagine that many others would want a lot more, though.
Dave
P.S. Scripts that copy databases around might be a nice solution for some, but I for one find it a sub-optimal solution (i.e. a hack, the problem with hacks is that when they go wrong they can go very wrong).
[quote]Multiple libraries is something for the more advanced user.[/quote]
The most basic Multiple Library/Database support would be the equivalent of a "File -> Open (Database)" command, which most Windows programs have.
Of course, once this is added a whole can of worms is opened: such as copying information between databases for certain tracks, 'currently playing' issues, device synchronization configuration issues (which DB is used, is a device associated to a specific DB?), use a MIDI style interface? (i.e. multiple databased open simultaneously, with drag and drop support between them), etc, etc, etc...
However, "File -> Open" is all I need, and opening a new DB can close the currently open one. I could imagine that many others would want a lot more, though.
Dave
P.S. Scripts that copy databases around might be a nice solution for some, but I for one find it a sub-optimal solution (i.e. a hack, the problem with hacks is that when they go wrong they can go very wrong).