Ah, thank you, mitk::PersistenceService::LoadModule() was the missing piece of information.
The service is not a nullptr anymore and I can get the properties associated with an ID and they are kept during the lifetime of the application. So, I added the call to AddPropertyListReplacedObserver(this) but BeforePropertyListReplaced() and AfterPropertyListReplaced() are never called. I thought they would be called when the user saves and load a scene. Did I miss something? Le 2016-04-06 05:49, Kolb, Christoph a écrit : > I have just tested the PersistenceService in a Plugin and got the same error > message: > "The calling module probably misses a US_MODULE_NAME compile definition > and/or a call to > US_INITIALIZE_MODULE in one of its source files." > > It worked after I added a dependency to MitkPersistence and > called mitk::PersistenceService::LoadModule() in the constructor of my > pluginView. I also needed to > put US_INITIALIZE_MODULE in the source. > > Regards > Christoph > > On Tue, 2016-04-05 at 19:09 +0200, Sascha Zelzer wrote: >> You could at least put a breakpoint in the activator load() method of >> the persistence module and another at the line where you try to retrieve >> the persistence service. Are both breakpoints hit? What is their hit order? >> >> Cheers, >> Sascha >> >> On 04/05/2016 10:31 AM, Kislinskiy, Stefan wrote: >>> Thanks Matt, seems like this feature could be broken and we should >>> investigate then. I just >>> found a bug in our tracker [1] which sounds like it was never completely >>> implemented? I'll >>> check. I would recommend you guys to subscribe to the bug to stay in the >>> loop. >>> >>> [1] http://bugs.mitk.org/show_bug.cgi?id=18542 >>> >>> Best regards, >>> Stefan >>> ________________________________________ >>> Von: Clarkson, Matt [m.clark...@ucl.ac.uk] >>> Gesendet: Dienstag, 5. April 2016 10:02 >>> An: Kislinskiy, Stefan >>> Cc: MITK >>> Betreff: Re: [mitk-users] Scene properties >>> >>> Hi there, >>> >>> This rings a bell in my mind. I believe I found similar things to Nil. >>> >>> I had an auto-loaded module, that created a dialog box to set the file name >>> of an IGTToolStorage >>> file, and the port name of the COM port to connect to, for an NDI Tracker. >>> I wanted to persist >>> the settings, so that the user didn't have to keep repeatedly setting the >>> filename and port, >>> which in all likelihood remain fairly constant for each users setup. I >>> could not get the >>> PersistenceService to work, and it performed differently on Linux/Mac to >>> Windows. Im basically >>> using MITK 2015.05.2. >>> >>> In the attached file you will see I ended up commenting it out, and >>> resorting to QSettings. >>> So, I would be interested in the outcome of this. >>> Any ideas what is going on? >>> >>> Is it something to do with the fact that its an auto-loaded module, and the >>> order of auto- >>> loading? >>> >>> Thanks >>> >>> Matt ------------------------------------------------------------------------------ _______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
