Hi,
In theory, the ReadOnly handler should only check the Papyrus ModelSet. The resource themes.xmi should be loaded in its own Resource set (Shared a the workspace level, because this is a Workspace theme). Thus, it should bypass the ReadOnly handler.
Camille
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Christian W. Damus
Envoyé : lundi 7 avril 2014 17:58
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Read-Only mechanism
Hi, Gabriel,
Have a look at what the SashModelReadOnlyHandler does to ensure that *.sash and *.di files are writable (especially when they are stored in the workspace metadata area).
In your case, you will have to be more specific about checking the resources than just comparing file extensions, because *.xmi is a shared extension. Probably content-type is your best option.
Hi,
Currently, I am working on task
4300079. I have an EMF resource to store theme preferences.
This resource is saved in workspace preference folder (<workspace_uri>/.plugins/oep.infra.gmfdiag.css/themes.xmi).
When I use PropertyEditorFactory from Papyrus layer to get existing edition dialog for EMF references, all fields in dialog aren't editable. I think problem comes
from Read-Only API and in particular from ReferencedModelReadOnlyHandler.
The verification is made in method AbstactPropertyEditor#checkInput() when editor ask if data source input is editable.
Someone would have an idea to resolve this problem ?
Gabriel
--
|
|
|
Gabriel PASCUAL
Software Engineer
|
|
6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net
|
|
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
|
