* Change RlvCommandOptionHelper::parseOption<RlvCommandOptionGeneric>(rlvCmd.getOption()) to RlvCommandOptionHelper::parseOption<RlvCommandOptionGeneric>(rlvCmd.getOption(), rlvCmdOption ) as otherwise a wrong template go picked wich resulted in linker errors.
=> we don't (need to) check the return type in those cases since it can't ever fail to convert so we just end up with less nice looking code
* Rearrange RlvBehaviourDictionary to be above the classes that need the defintion (RlvBehaviourDictionary::instance call)
* Change '(".("RLV_FOLDER_FLAG_NOSTRIP")"' to '(".(" RLV_FOLDER_FLAG_NOSTRIP ")"'. The GCC preprecessor does not like it w/o spaces.
* Add template<> to those specialization that missed it
* Change template<> template<> to just template<>
=> GCC seems to hate the templated std::enable_if (try boost::enable_if in the future); meanwhile try to #define a solution
=> Nicky changed a function parameter name matching a template parameter name so start differentiating between the two
--HG--
branch : RLVa
-> the attachment will be killed on teleport and readded at some point after teleport (can be much, much later)
-> since we clean up restrictions on detach (=kill) the attachments appears to loose restrictions
-> problem is worse on viewers that hide the teleport screen and allow the user to interact with the world right up until the teleport sequence
-> this is a simulator-side bug which isn't actually our business but users think it's a viewer-side bug so we'll try to mitigate it somewhere client-side
=> repro: teleport and then right-click to get an active selection => the attachment will get killed => at some point after it will reappear once the new region sends an update message for it
--HG--
branch : RLVa
Nicky