Quote:
Originally Posted by Sweetpea
Oh, I never talked about how to implement a scheme like this, it was just an idea I got when I started working with those fields... And how it would fit my way of working  |
Did the case that would work solve your problem (the MobiPocket reader case)?
Quote:
|
But a girl can dream, can't she?
|
Isn't that illegal? Or immoral? Or something?
Quote:
Oh, the major problem I saw were circular references...
Create a custom colum "new_title"
{author} - {title}
and then use {#new_title} for your {title}...
|
Arrgh. I took care of mutual recursion when displaying fields on the GUI, but I forgot to do it in save-to-disk. Fixed now.
Did you have the offending field displayed on the library view? And if so, didn't it display RECURSIVE_COMPOSITE_FIELD or some such in the table? I bet it did, and then you went ahead and used it anyway, just to see what would happen.
