Pavel Sanda wrote: > Pavel Sanda wrote: >> i started to fix the original report but as i went in more and more >> problems appear and 'proper' fix will need major review od converter >> cache code. partial fix is oneliner. > > after some thinking i came to simpler draft: > lets use and manage index files, deletion policy etc. regardless > the state of the settings (cache enabled/disabled). > the only things which could be really disabled would be find & add > routines. > opinions?
I have at least some explanations for the original design: The code does not read the index, create the cache directory or remove cached items on purpose if the cache is disabled. The reason is that users who do not want the cache (e.g. for privacy reasons) should not be bothered with files on disk, and also if somebody disables the cache temporarily it should be preserved as long as it is disabled. After enabling again it would appear in exactly the same state as before. The if statement in the destructor looks indeed wrong to me (and I would just delete it). The other changes depend of course on the desired behaviour. The problem with the second running lyx instance is a general one: Not only the cache will be garbled, also the preferences, session etc, basically everything that lives in the user dir. Therefore a general synchronization would be the best solution IMHO. Georg
