Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Problem with loading custom Properties View context models

Hello Christian,

The properties view models can be stored in two different ways:

- Workspace, in the metadata folder
- Plug-in, via an extension point

When a local properties view configuration is being edited, there is a hidden project (, IIRC) which is an Eclipse link to the metadata folder.

I've seen a bug recently, and indeed, the custom properties view configurations disappears after restarting Eclipse. I cannot access the SVN history yet, so I can't tell when this regression has been introduced. The CopyContext action writes the custom properties configuration to its own metadata folder, instead of the one from (It's really dangerous to have a single class name for all our Activators :) )

I will fix that as soon as the SVN is back online. It's really trivial. 

Camille Letavernier
+33 (0)1 69 08 00 59 - camille.letavernier@xxxxxx
CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE)
Papyrus :

-----Message d'origine-----
De : [] De la part de Christian W. Damus
Envoyé : mardi 12 mars 2013 01:54
À : Papyrus Project list
Objet : [] Problem with loading custom Properties View context models

Hi, Team,

Looking at the latest trunk (r10497-ish), I'm confused about how custom Properties View context models are supposed to be loaded.

I see that the hidden project that the properties view Customization Dialog creates is stored in the workspace metadata directory of the plug-in.

However, the ConfigurationManager class in the plug-in tries to load the user-defined custom contexts from that plug-in's workspace metadata folder.  That obviously won't find the models stored in the other plug-in's metadata.

Am I missing something?  Is something else supposed to inject the custom contexts from the customization plug-in into the ConfigurationManager?  It's quite possible that I'm missing a plug-in or working on the wrong version of it.

Or is this just something that broken in a refactoring when the Properties View plug-in was split up?  In any case, I can copy a context and edit it, and see it take effect in the Properties View, but after re-starting the workbench, my custom contexts are all gone.

I could fix this (for bug 402961) by having the ConfigurationManager load custom contexts from the customization plug-in's metadata directory, but that seems like the wrong direction for that dependency.


_______________________________________________ mailing list

Back to the top