Instead of having multiple windows, and multiple filters... etc, involving much
redesign,
coding and bug-fixing, why not simply implement a database locking mechanism
and open multiple instances of Scid.
The mechanism will simply test if a database is already open read-write, and
accordingly open it read-only. In this way games can be copied between DBs,
independant filters are easily achieved, and all with hardly any new code.
The only other issue AFAICS is the handling of the options file that get saved
when
Scid closes... How to do this best i'm not sure, but this issue seems less
critical
than the alternatives.
As other people have commented, Scid is (perhaps) becoming less stable, and
feature creep is obviously the most likey reason.
Steven
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
