Search Issue Tracker

Fixed in 2021.1.X

Fixed in 2019.4.X

Votes

29

Found in

2019.4.13f1

2021.1.0a2

Issue ID

1287702

Regression

Yes

Double-clicking a script in the Inspector window does not open the External Script Editor

Inspector Framework

-

How to reproduce:
1. Create a new Unity project
2. Create a new script and attach it to any GameObject
3. In the Inspector window double-click the Script field

Expected result: the external script editor is opened
Actual result: nothing happens

Reproducible with: 2019.4.13f1, 2021.1.0a2
Not reproducible with: 2018.4.28f1, 2019.4.12f1, 2020.1.0a1, 2020.1.11f1, 2020.2.0b9, 2021.1.0a1

  1. Resolution Note (fix version 2021.1):

    Fixed in 2021.1.0a5

  2. Resolution Note (fix version 2019.4):

    Fixed in 2019.4.14f1

Log in to vote on this issue

Comments (17)

  1. omx-jonson

    Nov 02, 2020 09:24

    As a workaround (which is painful, but still better than nothing) :
    In inspector, where the script component is, there's 3 small dots. Click them and from the dropdown select "Edit script". It opens Visual Studio.

  2. omx-jonson

    Nov 02, 2020 09:20

    Seriously, lads. How can something like this go into the LTS?
    You add new LTS version, and it has such a HUGE error.
    Nothing seems to work.
    Please fix this ASAP.
    What's next? Hide mouse cursor in editor? :)

  3. CGCowboy

    Nov 01, 2020 15:54

    This simple little bug is a workflow crusher when you have lots of scripts.

  4. AaronVictoria

    Nov 01, 2020 09:35

    Any one seeing this, a short-term workaround is to switch your inspector to debug mode.

  5. jcbadboy

    Oct 30, 2020 16:38

    This issue decreases usability and productivity. Very important to fix it.

  6. Rodolfo-Rubens

    Oct 27, 2020 20:27

    Not only the script object field, all the disabled object fields stopped being interactable, I have a lot of systems that shows disabled object fields and that bug broke them...

  7. AcidArrow

    Oct 27, 2020 10:12

    What are you changing in an LTS version that breaks basic functionality like this?

    Why wasn't this caught by QA before release?

    Or was it caught but you decided it's not a blocker?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues