Hi Christian,

we have changed the policy so that all files in the (default) TopBraid project 
will be marked as read-only at start-up. The preferred procedure for customer 
projects is to create your own Eclipse project(s), and place your files there. 
Please leave the TopBraid project unchanged because we may want to take the 
freedom to upgrade or replace that folder with version upgrades. There are lots 
of rather static files in that project, including system ontologies that get 
may get updated regularly, and we want to clarify and simplify the contract 
here.

But if you want to continue storing your files in the TopBraid project, please 
use the "lock" button in the upper right corner of the Navigator view to unlock 
those files. This is not the same as the OS level read-only flag, and therefore 
you could not see this in the properties.

Cheers
Holger


On Dec 11, 2010, at 8:40 PM, Christian Fuerber wrote:

> Hi,
> since I have upgraded to TBC 3.4, I cannot modify my files anymore.
> Although they show up as read only files in the workspace, read only
> is not checked in the properties. How can I make the files writable
> again?
> 
> Thanks for any help!
> 
> Christian
> 
> -- 
> You received this message because you are subscribed to the Google
> Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
> TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
> 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-users?hl=en

-- 
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
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-users?hl=en

Reply via email to