Search Issue Tracker

Fixed in 2017.1.0f3

Fixed in 5.5, 5.6, 2017.1

Votes

0

Found in

2017.1.0b1

Issue ID

898826

Regression

Yes

When Perforce selected, some other unrelated GUI turns disabled.

Version Control

-

To reproduce:

1. Change Version Control Mode to Perforce in Edit -> Project Settings -> Editor
2. Observe other fields, which become disabled

Expected: Expected: changing Version Control Mode to Perforce should not prevent a user from changing other settings
Actual: other project settings are disabled when Version Control Mode is changed to Perforce

Reproduced in 5.6.0f3, 5.6.0p2, 2017.1.0b1
Did not reproduce in 5.5.0f3
Regression introduced in 5.6.0f3

Comments (1)

  1. 63c87b6a3f73857b04a75e76ab75bee3?d=mm

    RobJessop

    Jun 12, 2017 09:29

    This is actually working as designed, mostly.

    The editor settings are saved in files that are usually owned by version control. When you select Perforce as your version control provider, the inspector checks whether or not the editor settings file is open for edit. You haven't got a connection to Perforce, so the code plays it safe and assumes that you haven't got the settings file open for edit and disables the rest of the settings.

    The fix we've implemented for this issue is to get the inspector to explain this with the VCS status label at the foot of the inspector.

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.