From: Morten O. A. <mor...@gm...> - 2010-05-04 19:38:07
|
EBo, this bug calls for a fairly quick fix, so I'm aiming to release a minor update soon. However, I can send you a test version with a fix if you want, so we can verify that it solves the problem. I am actually looking at a simpler solution. The GUI update that runs into trouble isn't crucial, and the GUI is updated once and for all later, when the key generator is finished. So I merely added a flag to indicate that crossrefs should not be resolved. This flag is set for the database when the key generator starts, and cleared when it's finished. This prevents the crash, and if testing doesn't show any vidual effects, it should be OK. -- Morten On 4 May 2010 03:45, EBo <eb...@sa...> wrote: > I talked to one of friends who has done some java development in the past > (I've never programmed in Java...). Anyway, he was going to help beat on this > until I got your email back. We figure that the developers would do a better > job faster, so I let him off the hook for now ;-) > > We discussed the problem and came up with the following strategy for solving > the problem: > > If you create a temporary linked-list of cross references (with its head item) > in the class/method which calls the key generator, then there will be no > reason to recursively try to correct the cross references on the fly. After > updating all the individual keys, then the cross references can be updated > from the linked list. Fortunately, the code already exists to add the cross > references info in a citation, so I think this would be a reasonably clean > approach. > > Will you have time to try to work on this? Unfortunately, this is a bit of a > show stopper for me to continue some of my work. > > Thanks and best regards, > > EBo -- > > > Morten Omholt Alver <mor...@gm...> said: > >> EBo, >> >> thank you for reporting this problem! I could reproduce it >> immediately, but it was a fairly tricky issue to track down. The >> problem is when the GUI tries to refresh somewhere in the process of >> generating keys. In order to decide whether each entry is complete, it >> needs to follow crossreferences, but this process fails somehow >> because of temporary changes made by the key generator process. >> >> Now it's just a matter of finding a reasonably clean solution to this. :) >> >> -- >> Morten >> >> On 2 May 2010 11:26, EBo <eb...@sa...> wrote: >> > >> > I am collating several largish BibTeX databases and have an issue with key >> > generation on items which use crossref. Clicking on the item produces a >> > believable citation with the cross referenced items filled in, however if I >> > then type <ctrl>g to generate a key from the results jabref goes into an >> > infinite loop. >> > >> > Is there a trick or a fix for this? I probably have several hundred cross >> > referenced citations and patching them by hand is a very slow and painful >> > process... >> > >> > EBo -- >> > >> > ps: if the other attempts to post eventually come through please accept my >> > apologies for multiposting. > > |