-> additionally, revert to using the stored string behaviour otherwise @sendim_sec=n,getstatus=0 shows /sendim rather than /sendim_sec
--HG--
branch : RLVa
-> see previous commit as well
-> lookups ended up refreshing before the actual attachments were attached leaving them (from a user's perspective unpredictably) detachable
--HG--
branch : RLVa
-> wearables would be properly filtered if there was at least one wearable lock
-> attachments would be properly filtered if there was at least one attachment lock
=> added explicit check for add-restricted folders
=> gray out the relevant context menu items (i.e. "Add to Outfit" and "Replace Current Outfit)
--HG--
branch : RLVa
-> bundle all permission checks in a predictable single function (see RlvActions::canChangeActiveGroup)
-> properly handle the case where a user is ejected from a group
-> provide feedback to the user after we force the previous group back when joining a new group
--HG--
branch : RLVa
-> TPVs implementing dynamic viewer data should call RlvSettings::initCompatibilityMode() with the setting
-> End-users also have manual control over the list through the "RLVaCompatibilityModeList" debug setting
-> Format: (;-separated)
* creator:<uuid>
* name:<perl-regex>
--HG--
branch : RLVa
This should have no effect on default 256m x 256m sized regions. Regions that
are not using the standard size are currently broken anyway, so the result
will just be a different form of broken if the region is running on a simulator
not supporting this feature yet.
* 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
Ansariel