Uploaded image for project: 'Snowstorm'
  1. Snowstorm
  2. STORM-1810

Display Z coordinate in Script Error window

    XMLWordPrintableJSON

    Details

    • Type: Story
    • Status: Closed
    • Priority: Minor
    • Resolution: Released
    • Affects Version/s: None
    • Fix Version/s: Active
    • Labels:
      None
    • Environment:
      N/A
    • Test Plan:
      Hide

      Check on Preferences->Advanced->Show script errors in
      Also click on the radio button Separate window

      Rezz a cube
      Click on the content tab
      Click on the New Script button
      Replace the default script with the attached script BadScript.lsl
      Close the build floater
      Click on the cube: the Script Warning/Error floater appears with x, y, and z coordinates per the attached sample image ScriptError.png

      Show
      Check on Preferences->Advanced->Show script errors in Also click on the radio button Separate window Rezz a cube Click on the content tab Click on the New Script button Replace the default script with the attached script BadScript.lsl Close the build floater Click on the cube: the Script Warning/Error floater appears with x, y, and z coordinates per the attached sample image ScriptError.png

      Description

      Currently the Script Warning/Error floater may display the X and Y coordinates of the prim where an error has occurred. Adding the Z coordinate to this display (see attached ScriptError.png) would make this data much more useful.

      There is no net UI change here. I have removed the .nn decimal position for the X and Y coordinates (6 characters) and added a comma, a space, and at most 4 digits.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jonathan.yap Jonathan Yap
            Extended Group Visibility:
            jira-users
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                PagerDuty