[topbraid-users] When does TBC 'remember' prefixes - and how do I stop it?

I ran a check on import conflicts and was told that I had prefixes multiply defined across some models. I noticed that one of them was incorrect. I opened up the file to make sure (and made sure the path was correct) and sure enough the prefix had been corrected. But TBC was insistent that

Re: [topbraid-users] When does TBC 'remember' prefixes - and how do I stop it?

Hi Jack, does this also happen after you have closed all models (or better: restarted TBC)? If yes then I would like to know details of what you did to reproduce this. In general, prefixes defined in imported graphs remain in those imported graphs only, so editing the imported graph should

[topbraid-users] Re: When does TBC 'remember' prefixes - and how do I stop it?

It seems that the problem goes away if I close graphs and reopen them...at least some of the time. But I am loathe to close TBC and reopen it because it takes half an hour to do so (for version 4.2, 10 minutes for version 4.4). On Monday, July 7, 2014 4:08:08 PM UTC-7, Jack Hodges wrote: I

Re: [topbraid-users] Re: When does TBC 'remember' prefixes - and how do I stop it?

Jack, in terms of time it takes to re-open Composer, this is usually relative to the number of files open when closing Composer, as on opening Composer will try to establish the last known context.  Try closing all or most of the models before re-starting. For