Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-226970] lsl scripting touch_start() function no longer works on prims with full alpha textures #5401

Open
2 tasks
sl-service-account opened this issue May 10, 2019 · 2 comments

Comments

@sl-service-account
Copy link

sl-service-account commented May 10, 2019

Simple reproduction steps confirmed

  1. rez two boxes very close to each other

  2. create a new default script in each

  3. edit the script to make it clear which script is the front or back object

  4. set the texture on the box in front with a fully transparent texture

  5. click on the box in front

    Observe that the script triggered is from the box in the back. What we expect is the script for the transparent box in the front to be triggered.

    Note: This only reproduces with transparent textures. If the box in front is set to transparent with the object editor the touch triggers as expected.

    Workaround

    Enable highlight transparent (ctrl+alt+T) which will make all transparent objects red-tinted, but be clickable.

    What just happened? (Original report)

    I have full alpha textures on prims which are placed over other prims to use as buttons. When the prim is touched the touch_start() method within the prims script no longer triggers.

    What were you doing when it happened?

    touching a prim with a full alpha texture that has a script in it with a touch_start() method.

    What were you expecting to happen instead?

    I was expecting the touch_start() method of the script to execute then I touched the prim

    Other information

    please fix this. Full alpha textures on prims overlaying other prims of multiple prim objects are frequently used as buttons and it is expected when the prim is touched for the touch_start() method to execute.

Links

Duplicates

Original Jira Fields
Field Value
Issue BUG-226970
Summary lsl scripting touch_start() function no longer works on prims with full alpha textures
Type Bug
Priority Unset
Status Accepted
Resolution Accepted
Reporter Chilly Charlton (chilly.charlton)
Created at 2019-05-10T06:32:51Z
Updated at 2019-05-14T15:02:59Z
{
  'Build Id': 'unset',
  'Business Unit': ['Platform'],
  'Date of First Response': '2019-05-10T11:00:55.115-0500',
  "Is there anything you'd like to add?": 'please fix this.  Full alpha textures on prims overlaying other prims of multiple prim objects are frequently used as buttons and it is expected when the prim is touched for the touch_start() method to execute.',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'I have full alpha textures on prims which are placed over other prims to use as buttons.  When the prim is touched the touch_start() method within the prims script no longer triggers.',
  'What were you doing when it happened?': 'touching a prim with a full alpha texture that has a script in it with a touch_start() method.',
  'What were you expecting to happen instead?': 'I was expecting the touch_start() method of the script to execute then I touched the prim',
}
@sl-service-account
Copy link
Author

Kyle Linden commented at 2019-05-10T16:00:55Z

Hi Chilly,

We weren't able to reproduce this issue based on the information you provided.
Will you please provide a Slurl to a location where an example object is present to test with.

Please update this report and press the Info Provided button.

Thanks!

@sl-service-account
Copy link
Author

Beware Hax commented at 2019-05-10T18:53:04Z, updated at 2019-05-10T18:54:16Z

i am affected by this bug too. my report BUG-226975 was closed as duplicate of this one.

if clicking on a transparent part of an alpha tetxure, the click goes through to the prim behind it instead, but it should happen on the transparent part. broken in the latest SL viewer. earlier SL viewers and TPVs show the correct behavior. EEP viewer branch also not affected.

 

to reproduce, chess board on crescent/215/76/55. clicks on the piece succeed, but where it's not a piece, the click goes through to the square background and the click can't be made. to make a move, one clicks first on the starting piece, then on the destination square. people around me complain they can't use my chessboard anymore and are forced to switch to a TPV.

 

also affected is the Go game made by Silent Ying, example location at Otherland/229/140/23. After a new game is started, instead of clicking on the transparent square and making a move, one clicks on the board behind it, and toggles coordinates on/off.

 

edit: if view transparency (ctrl+alt+T) is on, the bug does not happen, correct behavior is shown instead.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant