Build window: set an object's hover text without writing a script #1054

New issue

Open

opened 2026-10-25 06:58:38 +00:00 by sky_line · 0 comments

sky_line commented

2026-10-25 06:58:38 +00:00

Owner

Add a way to set an object's floating hover text (the text normally set with llSetText) straight from the Build / Edit window: a text box, a colour and an alpha, plus a Clear button. Today it takes writing and dropping in a script.

Constraint: hover text is a server-side prim property that only scripts can set; there is no viewer→simulator message for it. So the viewer has to use a script for you:

the Edit window creates a tiny one-shot script in the object's contents, with the chosen text, colour and alpha baked in;
the script calls llSetText(...), then removes itself (llRemoveInventory(llGetScriptName())), so the text stays and no script is left behind;
with several prims selected, apply per prim, or offer root-only / all-linked choices.

Rules to respect:

The user needs modify rights on the object.
Scripts must be allowed where the object is (parcel / region no-scripts settings); explain the failure if they aren't.
Confirm before replacing existing hover text that a running script keeps resetting: a scripted object's own script may overwrite the text again.
Show the current hover text in the field: the viewer already knows it from object updates.

Where: Build window, Object or Features tab (wherever it fits); a matching entry in the right-click menu would be nice.

Done when: a user with modify rights can set, change and clear an object's hover text from the Edit window without writing a script, and no helper script remains in the object afterwards.

Add a way to set an object's floating hover text (the text normally set with `llSetText`) straight from the Build / Edit window: a text box, a colour and an alpha, plus a Clear button. Today it takes writing and dropping in a script. **Constraint:** hover text is a server-side prim property that only scripts can set; there is no viewer→simulator message for it. So the viewer has to use a script for you: - the Edit window creates a tiny one-shot script in the object's contents, with the chosen text, colour and alpha baked in; - the script calls `llSetText(...)`, then removes itself (`llRemoveInventory(llGetScriptName())`), so the text stays and no script is left behind; - with several prims selected, apply per prim, or offer root-only / all-linked choices. **Rules to respect:** - The user needs modify rights on the object. - Scripts must be allowed where the object is (parcel / region no-scripts settings); explain the failure if they aren't. - Confirm before replacing existing hover text that a running script keeps resetting: a scripted object's own script may overwrite the text again. - Show the current hover text in the field: the viewer already knows it from object updates. **Where:** Build window, Object or Features tab (wherever it fits); a matching entry in the right-click menu would be nice. **Done when:** a user with modify rights can set, change and clear an object's hover text from the Edit window without writing a script, and no helper script remains in the object afterwards.

sky_line added the

feature

labels

2026-10-25 06:58:38 +00:00

sky_line added this to the Slipstream project

2026-10-25 06:58:38 +00:00

sky_line self-assigned this

2026-10-26 02:58:26 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sky_line/Slipstream#1054

No description provided.

Rows
Columns