by Guest » Sun Jan 02, 2011 2:30 am
Hi!
I've just encountered the same problem, after having injected a supplementary information in my main database, namely, a sound file path for one side. This injection works fine (i.e., the original cards are recognized) when the *second* side is modified. But when the modification occurs on the *first* side, FCDL warns me no matching cards have been found. Unfortunately, I heavily relied on the previous behaviour (i.e., one identical side = same card) when updating programmatically my database by complex injection of pieces of new knowledge into old cards. So, for me, this new behaviour is clearly a regression. I can think to a workaround:
1. export all the offending decks;
2. swap "fixed" columns in first position;
3. re-import the decks;
4. modify the settings to make the second side appear first.
Since this represents some work, I would like to hear your opinion first, about the supposed problem, and the supposed workaround.
Cheers!
A.
Hi!
I've just encountered the same problem, after having injected a supplementary information in my main database, namely, a sound file path for one side. This injection works fine (i.e., the original cards are recognized) when the *second* side is modified. But when the modification occurs on the *first* side, FCDL warns me no matching cards have been found. Unfortunately, I heavily relied on the previous behaviour (i.e., one identical side = same card) when updating programmatically my database by complex injection of pieces of new knowledge into old cards. So, for me, this new behaviour is clearly a regression. I can think to a workaround:
1. export all the offending decks;
2. swap "fixed" columns in first position;
3. re-import the decks;
4. modify the settings to make the second side appear first.
Since this represents some work, I would like to hear your opinion first, about the supposed problem, and the supposed workaround.
Cheers!
A.