Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.

Postponed

Votes

20

Found in

5.0.0b12

Issue ID

646705

Regression

No

You cannot resize a box collider when you have two inspectors

Inspector Framework

-

You cannot resize a box collider when you have to inspectors open at the same time. Happens probably for reflection probe as well (though is untested).

2) How can we reproduce it using the example you attached

1 Create new project
2 Create empty object and add BoxCollider to it
3 Open up two inspector tabs which are visible at the same time
4 Select this object with boxCollider in Hierarchy

5 Click "Edit Collider"-button in first Inspector tab(which was opened first), notice that you CAN see the draggable rectangles and it works as expected

5 Click "Edit Collider"-button in second Inspector tab(which was opened second), notice that you DON'T see the draggable rectangles and you CAN'T edit collider - what is not expected

Expected behavior: Both Inspector tabs should be synchronized

Comments (21)

  1. skillster-jocke

    Nov 20, 2018 09:26

    Still there in 2018.2...

  2. ChristianHolzer

    Apr 23, 2018 13:44

    I'm also having this issue with 2017.3.

  3. croixbk

    Feb 28, 2018 10:34

    Still a problem in 2017.3

  4. antoniolea

    Dec 06, 2017 10:40

    happens in 2017.2

  5. MS_3D

    Aug 17, 2017 10:30

    Still a problem in 5.6.2 and 10 2017.1
    Come on guys. I really need a second Inspector.
    That switching Layouts Workaround slows my workflow down.

  6. Efril

    Mar 26, 2017 13:03

    Faced this issue after updating to 5.5.2f1.

  7. kodekq

    Jan 26, 2017 09:34

    Still a problem in 5.5.1!!!! Are you seriously?

  8. Keeetrab

    Dec 30, 2016 11:25

    Still in 5.5.03f

  9. codegasm

    Dec 17, 2016 08:56

    Just ran into this 5.5.0f3

  10. Rakbhu

    Jun 04, 2016 18:00

    And still a problem in 5.3.5

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.