[OpenWalnut-Dev] New Properties

Sebastian Eichelbaum eichelbaum at informatik.uni-leipzig.de
Sun Feb 14 16:42:04 CET 2010


I missed to mention how to use the m_active property in the template module. 
There are basically three possibilities:

  * for your convenience, overwrite the member function "activate" in your module
  * use m_active->getCondition()->subscribeSignal directly to set an own callback
  * add m_active->getCondition() to your m_moduleState condition set.

But in many cases it is not even necessary to react on m_active directly.

  In the most cases it should be sufficient to use m_active in your OSG update 
callback to set your childs node mask ( note that you can also set a callback on 
the scene node (offered by getScene) to overcome the problem of inactive 
callbacks when the node is deactivated (but please remember to remove the 
callback after your module finishes and remember to use addUpdateCallback 
instead of setUpdateCallback, as it overwrites all the other callbacks))

I'll update the template module on Monday to include the m_active property.

Bye
Sebastian

Sebastian Eichelbaum schrieb:
> I pushed it! :-)
> 
> An quite extensive overview/howto can be found in 
> modules/template/WMTemplate.* It describes how to write modules, how to 
> use properties and property constraints, how to modify the OSG 
> correctly, as well as how to use progress reporting.
> 
> Have a nice weekend.
> Sebastian
> 
> 
> Sebastian Eichelbaum schrieb:
>> Hi List
>>
>> As some of you might know, I've did a lot of work implementing a new 
>> class that should replace WProperty and WProperites. It will have 
>> several implications:
>>
>>  1. Your modules and your properties need to be adopted too
>>  2. Sorting of datasets (texture display order on surfaces) does not 
>> work right now
>>  3. the Navigation Slice Slider in the sagithal, coronal and axial 
>> dock views and the Toolbar Buttons for showing/hiding the slices will 
>> not work anymore
>>
>> If you rely on either No. 2 or 3 you should consider not updating as 
>> long as those features won't work. I will mail on this list when I 
>> made them work again.
>>
>> For point 1, there is only one thing to say: update your modules. Your 
>> old properties will work but do not get displayed in the GUI. 
>> Nevertheless, it won't be much work. The new properties are more like 
>> variables. A small tutorial on how to use them will be available in 
>> the WIKI soon.
>>
>> If no one has reasonable veto against pushing my changes to the main 
>> branch I will do so on Friday, ~ 12 o'clock.
>>
>>
>> Greetings
>> Sebastian
>>
> 

-- 
Dipl.-Inf. Sebastian Eichelbaum
Universität Leipzig
Institut für Informatik
Abteilung Bild- und Signalverarbeitung
PF 100920
D-04009 Leipzig


More information about the OpenWalnut-Dev mailing list