* 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
-> Examples:
* @recvim:0,20=n - user can only receive IMs from people within chat-range (20m)
* @sendim:256=n - user can only send IMs to people who are at least a region away (256m)
* @startim:0,256=n - user can only start IMs to people who are on the same region they are (between 0moh oh and 256m)
-> Note that you generally can't rely on having location information for avatars beyond the current region (and maybe 1-3 surrounding neighbours) so large values are of limited use
-> On an isolated region using 4096m as the upper value will guarantee that you can only IM avatars on the same region regardless of elevation but none anywhere else on the grid
--HG--
branch : RLVa
-> [FIXED] "Pay" isn't disabled on the avatar context menu when @shownames restricted
-> [CHANGED] Show a notification when the user can't offer a teleport due to an RLV restriction
--HG--
branch : RLVa
-> RlvBehaviourToggleProcessor now requires implementing RlvBehaviourHandler<eBhvr>::onCommand(...)
-> existing RlvBehaviourToggleHandler was renamed RlvBehaviourToggleProcessor and is "implemented" as a simple typedef
--HG--
branch : RLVa
-> Example: issue @tplocal:50=n
-> gRlvHandler.hasBehaviour(RLV_BHVR_TPLOCAL) will return true but gRlvHandler.hasBehaviourExcept(RLV_BHVR_TPLOCAL, LLUUID::null) will return FALSE
=> since it's a modifier command it will be reference counted but that fact is lost on manual matching (tplocal=n != tplocal:<option>=n) so we keep track of reference counting in the command
--HG--
branch : RLVa
-> historically RLVa always had the concept of "local teleports" by tieing double-click teleports to @sittp rather than being subject to @tploc
-> location teleports were tied to @tploc regardless of the distance
=> this change divides position-based teleports in "local" and "remote" with different sets of rules (@sittp and @tploc respectively)
=> added @tplocal=n to restrict local teleport without impacting sit distance (@sittp still implies @tplocal)
--HG--
branch : RLVa
-> <behaviour>: (optional) command filter (e.g. tp)
<type> : (optional) any|add|force|reply
<separator> : (optional) user-defined separator
-> Examples:
@getcommand:tp;add=0 will show all restrictions that @clear=tp would clear
@getcommand:;reply;^-^=0 will show all reply commands separated by ^-^
--HG--
branch : RLVa
Kitty Barnett