Hi Arthur, sorry for not responding earlier :) I did not have an immediate insight, so I was not sure what else to say. Even new files get detected correctly in my version. The error log is incomprehensible (email client probably inserted line breaks), and the screenshot too coarse grained to decipher much. Perhaps could you clear the error log first and then try to reproduce the problem systematically, and finally send me a more focussed error log?
Thanks, Holger On Mar 5, 2009, at 2:11 PM, Arthur Keen wrote: > Holger, > > Thanks for responding so quickly. > > The only difference I can think of is that I am replacing the files > with new ones, so the "create date" is changing. I just realized I > should have sent you my error log. I am getting a lot of "Could not > inspect" and "File out of synch" errors in the logs. I have included > the log file (tbc.log). This will be much more informative to you. > > > > <tbc.log> > > Another potential difference, is that I am creating a lot of N3 files > every time I run a translation, a couple of hundred model files each > time. I have included a screen capture to put this in context. > > Also, I would like to mention that TBC has enabled me to build the > kind of models I would not have dreamed of trying with the other tools > that I have used. The re-factorization capabilities are amazing. > > thanks > > Arthur > > <pastedGraphic.png> > On Mar 5, 2009, at 3:12 PM, Holger Knublauch wrote: > > >> >> Hi Arthur, >> >> I just did a test to reproduce your scenario. I have an .n3 file in >> my >> workspace and (without having it open in TBC), edit its base URI with >> an external text editor. Then I select the file in the workspace and >> hit the Refresh (F5) key. The system then does an internal check and >> updates to the new base URI (in gray behind the file name). So this >> appears to work fine, and I don't need to restart TBC. >> >> The only case where this would not work is if the N3 is still open in >> TBC. >> >> What is different from in scenario? >> >> Holger >> >> >> On Mar 5, 2009, at 12:05 PM, Arthur wrote: >> >>> >>> I am writing a translator that translates reservoir model >>> specifications to OWL in N3. The translator writes the resultant N3 >>> files into a TBC works space, so that I can easily view the results >>> using TBC for debugging. I routinely run into problems where TBC >>> will >>> not open the generated N3 files and will mark them with a red x. >>> This >>> happens even if I close the N3 files I was inspecting before >>> regenerating the N3 files and even after doing a refresh (although >>> if >>> you "close all" this will work, see below). >>> >>> When viewing the files in a text editor in TBC, synchronization >>> works >>> as expected as TBC will let you know when files have been updated >>> and >>> prompt you on whether to update the viewed file or not.) I have >>> found >>> 2 work-arounds 1) cause TBC to reload after generating new N3 >>> files, >>> 2) select "close all" to close all open N3 files and close folder >>> trees in the workspace before re-generating the N3 files, and then >>> issue a refresh on the topmost folder before viewing the generated >>> files. Work-around 1 works the best as when TBC comes back up, it >>> opens all of the models that I had been looking at, so there is no >>> need to re-open them. The refresh does not seem to work as I had >>> expected and reloading TBC every time seems a little extreme. >>>> >> >> >> --~--~---------~--~----~------------~-------~--~----~ >> You received this message because you are subscribed to the Google >> Groups "TopBraid Composer Users" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/topbraid-composer-users?hl=en >> -~----------~----~----~----~------~----~------~--~--- >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
