Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upInspector disabled for locked files #934
Closed
Labels
Comments
|
Hey @vanustwo thanks for testing our stuff out and making this bug report, but can you give me a bit more to work with? Maybe a screen shot or gif or something... I'm having a bit of trouble getting what you mean. |
|
@StanleyGoldman thank you for the reply.
|
|
That's real weird. I'll give it a shot myself in a bit. |
|
I reproduced it. That's so weird. |
|
|
|
@StanleyGoldman Do you have an ETA for a fix? |
|
Not quite yet. I was pushing out a release yesterday and tried to see if this was an easy fix. |
shana
added a commit
that referenced
this issue
Nov 7, 2018
There's two issues going on here - The `loggedInUser` field wasn't getting seeded with user information on load, so checking whether the current user owns a lock would always fail until the connections changed event got triggered somehow - `GetLock` didn't account for not having user information, so if the user was logged out, it would default to not allowing any edits. Since the info wasn't getting seeded, it would always report files as being locked by someone else. It now defaults to allowing edits if the user isn't signed in. Now, this isn't a bug, but if the user is not signed in, all bets are kinda off on validating locks. We should probably warn the user that we can't check whether they own the lock, but we should probably not lock down Unity entirely because of it.
StanleyGoldman
added a commit
that referenced
this issue
Nov 28, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a file is locked like a material. The inspector view UI is disabled. Is there a way to stop this?