Re: [mdt-papyrus.dev] [Refactoring Service] Questions

["Christian W. Damus" <give.a.damus@xxxxxxxxx>]

Hi, Gabriel,

Any listeners attached to the IReloadableEditor will have to be informed that the editor was reloaded, so I think we would still need it to be involved.  The only case that I know of in which the user would be prompted is if the editor that needs to re-load resources is dirty (has unsaved changes).  But, that shouldn’t happen in your case because a precondition of refactoring is that all editors and saveable view parts are saved.

What, exactly, is the prompt that you’re seeing and why is it happening?

Christian

On Tue, Aug 11, 2015 at 6:09 AM, Gabriel Pascual <gabriel.pascual@xxxxxxxxxxx> wrote:

Le 07/08/2015 15:16, Christian W. Damus a écrit :

 That implies that your refactoring should be free to unload/reload resources as necessary to do its work, without reference to the lifecycle service.

Hi Christian,

I removed the dependence to LifeCycleEventProvider and I manage load/unload/save in Refactoring service, but in editor context, this one detects changes and it asks if it has to be reloaded.
This is the IReloadableEditor interface that gives it this behaviour. Do you have an idea how to get around this behaviour ?

Regards

Gabriel

--

<logo.jpg>

	Gabriel PASCUAL Software Engineer
6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE www.all4tec.net