Information

This feature request is for a new prim property and a the following function:

llSetLinkMouseoverText(integer link_num, string text, string face_delimiter);

This applies the text and face_delimiter values as prim properties to link, link_num.

When you mouse over a prim that has a touchevent and the mouse icon changes to a clicking hand, 0.5 - 1.0 seconds later, mouseover text is read and delimited. The list element corresponding to the link face number you are mousing over will show in a popup unless the text is a null string.

example:

When mousing over a link with mouseover text, "0,1,2,3,4" and a face_delimiter of ",", a popup will occur containing the text, "2" if you are hovering over face 2. No popup will occur if you are hovering over an unknown face, if the face number exceeds the list length or if the delimited text is a null string.

A delimiter is necessary so we have link face mouseover feedback capability with mesh objects and in case commas are needed in the actual popup text and to prevent implementing a function that forces set text lengths per face. This way an overall string can be used and divided up as necessary.

A delimited string is also preferred instead of a list in case we get more than 9 face capability with prims in the future.

If delimiter is nullstring, the full text shows no matter which face is hovered over.

Benefits:

HUDs on in-world touch objects can have tooltips for buttons that use icons instead of settext or to give a brief description of what a button does or how it is used.

Other Information

Function can alternatively be named llSetLinkTooltipText().
The text parameter should have a minimum 255 byte limit, with a preferred limit of 1023 bytes.
The face_delimiter parameter can have a 9 byte limit.

There could also be an additional "delay" parameter that allows the creator to tailor how long before the mouseover text displays in case the text is large or intuitive which in both cases could be deemed annoying to the end user with shorter times with repeated or accidental mouseovers.

This feature should also support global use of texture_UUID or equivalent so non-localized(viewer only) textures can be shown in the popup for help aid purposes. Currently only localized textures are supported.

Related to https://jira.secondlife.com/browse/BUG-9916 but that feature requests dedicated start, intermediate and end events which I feel are unnecessary and traffic intensive.

Comments welcome. Thanks in advance for any consideration.

Links

Related

• [BUG-9916] Add hover events to LSL for HUDs #17350

Duplicates

• [BUG-225145] HUD attachment tooltips #4020

{
  'Business Unit': ['Platform'],
  'How would you like the feature to work?': 'h1. Information\r\n\r\nThis feature request is for a new prim property and a the following function:\r\n\r\nllSetLinkMouseoverText(integer link_num, string text, string delimiter);\r\n\r\nThis applies the text and delimiter values as prim properties to link, link_num.\r\n\r\nWhen you mouse over a prim that has a touchevent and the mouse icon changes to a clicking hand, 0.5 - 1.0 seconds later, mouseover text is read and delimited. The list element corresponding to the link face number you are mousing over will show in a popup unless the text is a null string.\r\n\r\nexample:\r\n\r\nWhen mousing over a link with mouseover text, "0,1,2,3,4" and a delimiter of ",", a popup will occur containing the text, "2" if you are hovering over face 2. No popup will occur if you are hovering over an unknown face, if the face number exceeds the list length or if the delimited text is a null string.\r\n\r\nA delimiter is necessary so we have link face mouseover feedback capability with mesh objects and in case commas are needed in the actual popup text and to prevent implementing a function that forces set text lengths per face. This way an overall string can be used and divided up as necessary.\r\n\r\nBenefits:\r\n\r\nHUDs on in-world touch objects can have tooltips for buttons that use icons instead of settext or to give a brief description of what a button does or how it is used.\r\n\r\nh1. Other Information\r\nFunction could alternatively be named llSetHoveroverText() or llSetLinkTooltipText().\r\nThe text parameter should have a minimum 255 byte limit, with a prefered limit of 1023 bytes.\r\nThe delimiter paramter can have a 9 byte limit.\r\n\r\nComments welcome. Thanks in advance for any consideration.',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'Target Viewer Version': 'viewer-development',
  'Why is this feature important to you? How would it benefit the community?': '?',
}