Difference between revisions of "Talk:LlResetAnimationOverride"
Jenna Felton (talk | contribs) (Created page with "The command ''llResetAnimationOverride'' is not cooperative when using ''"ALL"'' parameter: Issuing it resets override for all animations, also those overrided by another AO. Exa…") |
(Yes, JIRA can still be used for feature requrests.) |
||
(4 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
The command ''llResetAnimationOverride'' is not cooperative when using ''"ALL"'' parameter: Issuing it resets override for all animations, also those overrided by another AO. Example: Use two overriders the overrider A for Sitting and Standing, the overrider B for Walking and Jumping, both AO use the | The command ''llResetAnimationOverride'' is not cooperative when using ''"ALL"'' parameter: Issuing it resets override for all animations, also those overrided by another AO. Example: Use two overriders the overrider A for Sitting and Standing, the overrider B for Walking and Jumping, both AO use the example script. Now when you attach both overriders, than your sit, stand, jump and walk animations are overriden. When you detach A, it resets all animations using the parameter ''"ALL"'', also animations, overriden by B, the effect of B is now destroyed. | ||
To solve the problem, i'd suggest to extend the command by possibility to take a comma-separated list of animation states to be resetted, so you simply issue the command, say ''llResetAnimationOverride("Sitting,Standing");'' to reset just | To solve the problem, i'd suggest to extend the command by possibility to take a comma-separated list of animation states to be resetted, so you simply issue the command, say ''llResetAnimationOverride("Sitting,Standing");'' to reset just two to defaults. The command would cause than a loop through animation states, but on lowest level with more chance for completing while detaching the AO. | ||
[[User:Jenna Felton|Jenna Felton]] 02:48, 9 May 2013 (PDT) | [[User:Jenna Felton|Jenna Felton]] 02:48, 9 May 2013 (PDT) | ||
:I believe you should make use of [https://jira.secondlife.com the issue tracker]. [[User:Kireji Haiku|Kireji Haiku]] 00:11, 15 May 2013 (PDT) | |||
::I agree. It's not surprising it resets all (not just it's own). I do like your suggestion and I think you should open a issue on Jira. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 21:27, 18 May 2013 (PDT) | |||
: Thank you for your replies. The issue traker allows just bug reports, no feature requests any more, but when this issue is a bug than just in the design, not implementation. But after your two suggestions i added one and formated as feature request: [https://jira.secondlife.com/browse/BUG-2651 BUG-2651] [[User:Jenna Felton|Jenna Felton]] 11:13, 21 May 2013 (PDT) | |||
:: Feature requests ''are'' considered if they are entered in the BUG project. They work out the right place to put an issue when they triage it now. --[[User:Cerise Sorbet|Cerise Sorbet]] 07:11, 22 May 2013 (PDT) |
Latest revision as of 06:11, 22 May 2013
The command llResetAnimationOverride is not cooperative when using "ALL" parameter: Issuing it resets override for all animations, also those overrided by another AO. Example: Use two overriders the overrider A for Sitting and Standing, the overrider B for Walking and Jumping, both AO use the example script. Now when you attach both overriders, than your sit, stand, jump and walk animations are overriden. When you detach A, it resets all animations using the parameter "ALL", also animations, overriden by B, the effect of B is now destroyed.
To solve the problem, i'd suggest to extend the command by possibility to take a comma-separated list of animation states to be resetted, so you simply issue the command, say llResetAnimationOverride("Sitting,Standing"); to reset just two to defaults. The command would cause than a loop through animation states, but on lowest level with more chance for completing while detaching the AO.
Jenna Felton 02:48, 9 May 2013 (PDT)
- I believe you should make use of the issue tracker. Kireji Haiku 00:11, 15 May 2013 (PDT)
- Thank you for your replies. The issue traker allows just bug reports, no feature requests any more, but when this issue is a bug than just in the design, not implementation. But after your two suggestions i added one and formated as feature request: BUG-2651 Jenna Felton 11:13, 21 May 2013 (PDT)
- Feature requests are considered if they are entered in the BUG project. They work out the right place to put an issue when they triage it now. --Cerise Sorbet 07:11, 22 May 2013 (PDT)