Skip to content

Add missing constant SIT_OK#114

Merged
HaroldCindy merged 1 commit into
secondlife:mainfrom
tapple:SIT_OK
May 6, 2026
Merged

Add missing constant SIT_OK#114
HaroldCindy merged 1 commit into
secondlife:mainfrom
tapple:SIT_OK

Conversation

@tapple

@tapple tapple commented Apr 27, 2026

Copy link
Copy Markdown
Contributor

According to the wiki, llSitOnLink has 8 possible return values. But, only 7 of them are named constants. Add the missing one.

Discovered while auditing the Error enums for #113

@Martin-Pitt

Copy link
Copy Markdown
Contributor

If successful returns 1 you mean?

@tapple

tapple commented Apr 27, 2026

Copy link
Copy Markdown
Contributor Author

yes. I defined SIT_OK = 1

constexpr int32_t LSL_GEN_SIT_NO_ACCESS = -6;
constexpr int32_t LSL_GEN_SIT_NO_EXPERIENCE_PERMISSION = -2;
constexpr int32_t LSL_GEN_SIT_NO_SIT_TARGET = -3;
constexpr int32_t LSL_GEN_SIT_OK = 1;

@tapple tapple Apr 27, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The wiki is correct: this script seats me and prints 1:

default { state_entry() {
llSitTarget(<0, 0, 1>, ZERO_ROTATION);
llOwnerSay((string)llSitOnLink(llGetOwner(), LINK_THIS));
}}

[12:13 PM] Object: 1

Comment thread lsl_definitions.yaml
type: integer
value: -3
SIT_OK:
member-of: [SitError]

@HaroldCindy HaroldCindy May 6, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔕 May have to do another pass at these names later, "error" no longer fits. Doesn't block this at all.

@HaroldCindy HaroldCindy merged commit 1e7b086 into secondlife:main May 6, 2026
5 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators May 6, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants