| Key: |
VWR-6232
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Expected Behavior
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Ordinal Malaprop
|
| Votes: |
203
|
| Watchers: |
20
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
1.20 RC
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is original of duplicate:
|
|
|
|
|
 |
|
|
|
|
VWR-6806
"double-tap to run" feature should be removed or mapped to another key
|
|
|
|
|
Relates
|
|
|
|
This issue is related to by:
|
|
|
|
VWR-12373 Debug option AllowTapTapRun has stopped working in version 1.22.11 - only the Adv > Character > option works
|
|
|
|
|
|
VWR-6275
Character runs when not supposed to.
|
|
|
|
|
|
|
SVC-2134 Allow additional detected controls (eg: CONTROL_SHIFT_FORWARD CONTROL_SHIFT_BACK)
|
|
|
|
|
|
|
VWR-6250 Implement User Definable input mapping
|
|
|
|
|
|
|
VWR-6690 Move option for double-tap-run from advanced-character to preferences menu under "input & camera"
|
|
|
|
|
|
|
VWR-6256 Meta-issue: Bugs that effect C:SI Combat Samurai Island
|
|
|
|
|
|
|
|
|
|
|
|
| Linden Lab Issue ID: |
DEV-13500
|
This is a basic change in behavior and should not be implemented. Double-tapping is a behavior not currently directly recognized by LSL and which does not currently have any particular meaning; there is an amount of content for which it has been trapped via LSL and used for special purposes (fast moves, special attacks and so on).
This will obviously cause unwanted behavior:
- Under heavy lag (double-tap to run will be detected first because it is client-side, while other double-tap implementations are detected server-side)
- In scripts where double tap doesn't override animations
- In scripts where double tap expects the character to be walking
Also, making it an option doesn't solve one main concern, since it is off by default. That is, even if sometimes it doesn't cause any unwanted behavior, no new scripts will dare to use this previously useful key combo because it will be known by users to be used by the client. Scripters yet only have only a few usable keys detected by LSL, taking that one away is a bad move.
Hence we urge Liden Labs to revert this "feature", set it off by default or find a way to map it to another key.
|
|
Description
|
This is a basic change in behavior and should not be implemented. Double-tapping is a behavior not currently directly recognized by LSL and which does not currently have any particular meaning; there is an amount of content for which it has been trapped via LSL and used for special purposes (fast moves, special attacks and so on).
This will obviously cause unwanted behavior:
- Under heavy lag (double-tap to run will be detected first because it is client-side, while other double-tap implementations are detected server-side)
- In scripts where double tap doesn't override animations
- In scripts where double tap expects the character to be walking
Also, making it an option doesn't solve one main concern, since it is off by default. That is, even if sometimes it doesn't cause any unwanted behavior, no new scripts will dare to use this previously useful key combo because it will be known by users to be used by the client. Scripters yet only have only a few usable keys detected by LSL, taking that one away is a bad move.
Hence we urge Liden Labs to revert this "feature", set it off by default or find a way to map it to another key. |
Show » |
made changes - 09/Apr/08 02:33 PM
| Field |
Original Value |
New Value |
|
Summary
|
1.20 source - double-tapping should not have a change in behaviour
|
1.20 source - "double-tap to run" should be optional, and NOT the default
|
made changes - 09/Apr/08 02:39 PM
|
Key
|
MISC-1100
|
VWR-6232
|
|
Component/s
|
|
User Interface
[ 10033
]
|
|
Project
|
4. Second Life Misc Issues - MISC
[ 10000
]
|
1. Second Life Viewer - VWR
[ 10003
]
|
|
Component/s
|
Miscellaneous
[ 10036
]
|
|
made changes - 09/Apr/08 02:40 PM
|
Link
|
|
This issue is duplicated by VWR-6231
[ VWR-6231
]
|
made changes - 09/Apr/08 02:41 PM
|
Affects Version/s
|
|
Source code
[ 10012
]
|
made changes - 09/Apr/08 02:52 PM
|
Summary
|
1.20 source - "double-tap to run" should be optional, and NOT the default
|
1.20 source - "double-tap to run" should not be implemented
|
made changes - 09/Apr/08 08:50 PM
|
Link
|
|
This issue is related to by VWR-6250
[ VWR-6250
]
|
made changes - 09/Apr/08 09:19 PM
|
Link
|
|
This issue is related to by VWR-6256
[ VWR-6256
]
|
made changes - 10/Apr/08 02:21 AM
|
Summary
|
1.20 source - "double-tap to run" should not be implemented
|
1.20 RC - "double-tap to run" should not be implemented
|
|
Environment
|
1.20 source
|
1.20 RC
|
|
Affects Version/s
|
Source code
[ 10012
]
|
|
|
Affects Version/s
|
|
1.20 Release Candidate
[ 10300
]
|
made changes - 10/Apr/08 02:22 AM
|
Comment
|
[ updating title and version it effects.
]
|
|
made changes - 10/Apr/08 02:22 AM
|
Description
|
From sldev mailing list relating to proposed changes in v1.20 - https://lists.secondlife.com/pipermail/sldev/2008-April/009013.html
* DEV-4706 Make running more intuitive by double-tapping forward
This is a basic change in behaviour and should not be implemented. Double-tapping is a behaviour not currently directly recognised by LSL and which does not currenty have any particular meaning; there is an amount of content for which it has been trapped via LSL and used for special purposes (fast moves, special attacks and so on).
Adding a standard client behaviour to double-tap would break this existing content.
|
From sldev mailing list relating to proposed changes in v1.20 - https://lists.secondlife.com/pipermail/sldev/2008-April/009013.html
* DEV-4706 Make running more intuitive by double-tapping forward
This is a basic change in behavior and should not be implemented. Double-tapping is a behavior not currently directly recognized by LSL and which does not currently have any particular meaning; there is an amount of content for which it has been trapped via LSL and used for special purposes (fast moves, special attacks and so on).
Adding a standard client behavior to double-tap would break this existing content.
|
made changes - 10/Apr/08 05:40 AM
|
Link
|
|
This issue is duplicated by VWR-6279
[ VWR-6279
]
|
made changes - 10/Apr/08 07:38 AM
|
Link
|
|
This issue is duplicated by VWR-6275
[ VWR-6275
]
|
made changes - 10/Apr/08 10:48 AM
|
Link
|
|
This issue is related to by SVC-2134
[ SVC-2134
]
|
made changes - 11/Apr/08 02:32 AM
|
Linden Lab Issue ID
|
|
DEV-13500
|
made changes - 11/Apr/08 03:54 AM
|
Link
|
This issue is duplicated by VWR-6275
[ VWR-6275
]
|
|
made changes - 11/Apr/08 09:30 AM
|
Link
|
|
This issue is related to by VWR-6275
[ VWR-6275
]
|
made changes - 17/Apr/08 10:31 PM
|
Summary
|
1.20 RC - "double-tap to run" should not be implemented
|
Petition *against* 1.20 RC - "double-tap to run" implementation
|
made changes - 19/Apr/08 07:18 AM
|
Link
|
|
This issue is related to by VWR-6690
[ VWR-6690
]
|
made changes - 20/Apr/08 11:47 AM
|
Link
|
|
This issue is related to by MISC-1137
[ MISC-1137
]
|
made changes - 22/Apr/08 05:53 AM
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Fix Version/s
|
|
1.20 Release Candidate
[ 10300
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
|
Assignee
|
|
Tofu Linden
[ Tofu Linden
]
|
made changes - 23/Apr/08 07:40 PM
|
Link
|
|
This issue Relates to VWR-6806
[ VWR-6806
]
|
made changes - 23/Apr/08 07:57 PM
|
Comment
|
[ Created VWR-6806.
People whose vote to have this feature removed were not heard by LL, please vote for that issue.
]
|
|
made changes - 23/Apr/08 08:01 PM
|
Status
|
Resolved
[ 5
]
|
Reopened
[ 4
]
|
|
Resolution
|
Fixed
[ 1
]
|
|
made changes - 23/Apr/08 08:05 PM
|
Summary
|
Petition *against* 1.20 RC - "double-tap to run" implementation
|
"double-tap to run" feature should be removed, set off by default or mapped to another key
|
|
Description
|
From sldev mailing list relating to proposed changes in v1.20 - https://lists.secondlife.com/pipermail/sldev/2008-April/009013.html
* DEV-4706 Make running more intuitive by double-tapping forward
This is a basic change in behavior and should not be implemented. Double-tapping is a behavior not currently directly recognized by LSL and which does not currently have any particular meaning; there is an amount of content for which it has been trapped via LSL and used for special purposes (fast moves, special attacks and so on).
Adding a standard client behavior to double-tap would break this existing content.
|
This is a basic change in behavior and should not be implemented. Double-tapping is a behavior not currently directly recognized by LSL and which does not currently have any particular meaning; there is an amount of content for which it has been trapped via LSL and used for special purposes (fast moves, special attacks and so on).
This will obviously cause unwanted behaviour:
- Under heavy lag (double-tap to run will be detected first because it is client-side, while other double-tap implementations are detected server-side)
- In scripts where double tap doesn't override animations
- In scripts where double tap expects the character to be walking
Also, making it an option doesn't solve one main concern, since it is off by defaut. That is, even if sometimes it doesn't cause any unwanted behaviour, no new scripts will dare to use this previously useful key combo because it will be known by users to be used by the client. Scripters yet only have only a few usable keys detected by LSL, taking that one away is a bad move.
Hence we urge Liden Labs to revert this "feature", set it off by default or find a way to map it to another key.
|
made changes - 23/Apr/08 08:07 PM
|
Link
|
This issue Relates to VWR-6806
[ VWR-6806
]
|
|
made changes - 23/Apr/08 08:09 PM
|
Link
|
|
This issue is duplicated by VWR-6806
[ VWR-6806
]
|
made changes - 23/Apr/08 08:28 PM
|
Summary
|
"double-tap to run" feature should be removed, set off by default or mapped to another key
|
"double-tap to run" will cause unwanted behaviour and changes semantics
|
made changes - 24/Apr/08 06:20 AM
|
Assignee
|
Tofu Linden
[ Tofu Linden
]
|
|
made changes - 01/May/08 11:27 PM
|
Summary
|
"double-tap to run" will cause unwanted behaviour and changes semantics
|
Petition *against* 1.20 RC - "double-tap to run" implementation
|
|
Description
|
This is a basic change in behavior and should not be implemented. Double-tapping is a behavior not currently directly recognized by LSL and which does not currently have any particular meaning; there is an amount of content for which it has been trapped via LSL and used for special purposes (fast moves, special attacks and so on).
This will obviously cause unwanted behaviour:
- Under heavy lag (double-tap to run will be detected first because it is client-side, while other double-tap implementations are detected server-side)
- In scripts where double tap doesn't override animations
- In scripts where double tap expects the character to be walking
Also, making it an option doesn't solve one main concern, since it is off by defaut. That is, even if sometimes it doesn't cause any unwanted behaviour, no new scripts will dare to use this previously useful key combo because it will be known by users to be used by the client. Scripters yet only have only a few usable keys detected by LSL, taking that one away is a bad move.
Hence we urge Liden Labs to revert this "feature", set it off by default or find a way to map it to another key.
|
This is a basic change in behavior and should not be implemented. Double-tapping is a behavior not currently directly recognized by LSL and which does not currently have any particular meaning; there is an amount of content for which it has been trapped via LSL and used for special purposes (fast moves, special attacks and so on).
This will obviously cause unwanted behavior:
- Under heavy lag (double-tap to run will be detected first because it is client-side, while other double-tap implementations are detected server-side)
- In scripts where double tap doesn't override animations
- In scripts where double tap expects the character to be walking
Also, making it an option doesn't solve one main concern, since it is off by default. That is, even if sometimes it doesn't cause any unwanted behavior, no new scripts will dare to use this previously useful key combo because it will be known by users to be used by the client. Scripters yet only have only a few usable keys detected by LSL, taking that one away is a bad move.
Hence we urge Liden Labs to revert this "feature", set it off by default or find a way to map it to another key.
|
made changes - 13/Nov/08 11:10 AM
|
Workflow
|
jira-2007-12-22a
[ 54460
]
|
jira-2008-11-14
[ 65040
]
|
made changes - 13/Nov/08 11:32 AM
|
Workflow
|
jira-2007-12-22a
[ 65040
]
|
jira-2008-11-14
[ 73355
]
|
made changes - 13/Nov/08 05:04 PM
|
Workflow
|
jira-2008-11-14
[ 73355
]
|
jira-2008-11-14a
[ 98623
]
|
made changes - 13/Nov/08 05:19 PM
|
Workflow
|
jira-2008-11-14
[ 98623
]
|
jira-2008-11-14a
[ 104327
]
|
made changes - 13/Nov/08 05:28 PM
|
Workflow
|
jira-2008-11-14
[ 104327
]
|
jira-2008-11-14a
[ 108179
]
|
made changes - 13/Nov/08 05:46 PM
|
Workflow
|
jira-2008-11-14
[ 108179
]
|
jira-2008-11-14a
[ 113797
]
|
made changes - 13/Nov/08 06:17 PM
|
Workflow
|
jira-2008-11-14
[ 113797
]
|
jira-2008-11-14a
[ 125089
]
|
made changes - 13/Nov/08 06:44 PM
|
Workflow
|
jira-2008-11-14
[ 125089
]
|
jira-2008-11-14a
[ 135364
]
|
made changes - 13/Nov/08 07:02 PM
|
Workflow
|
jira-2008-11-14
[ 135364
]
|
jira-2008-11-14a
[ 142646
]
|
made changes - 12/Mar/09 12:09 PM
|
Link
|
|
This issue is related to by VWR-12373
[ VWR-12373
]
|
made changes - 19/Apr/09 07:27 PM
|
Status
|
Reopened
[ 4
]
|
Resolved
[ 5
]
|
|
Fix Version/s
|
|
1.22
[ 10430
]
|
|
Resolution
|
|
Expected Behavior
[ 9
]
|
|
Petition *against* 1.20 RC - "double-tap to run" implementation
