When using the Make Writable button, it is intended to make the file editable without the prompt to check an asset out popping up on subsequent attempts to save the asset. This does not work for Subversion (TortoiseSVN was used to test this) as it prompts the user to check the asset out each time. It does successfully save the asset however.
Note: This issue does not occur when using Perforce as your method of source control
Regression?:
No, this feature was added with 4.9
New 4.11 Steps
1. Set up a new blank project for source control using Subversion (I used TortoiseSVN)
2. Open the project, create a blueprint of the type "Actor" and check it in.
3. Open the newly created blueprint and edit it in some way (i.e. Add a print string node)
4. Press "Save"
5. When it prompts you to check the asset out, press the "Make Writable" button.
6. Edit the blueprint again (i.e. Add a second print string node)
7. Press "Save"
8. The editor should not give any pop ups but the Asterisk * beside the blueprint's name will stay
9. Close the editor and when prompted, press "Save Selected".
10. Reopen the editor and check the contents of the blueprint
Result: The 2nd print string node (or the second change you made) was not saved.
Expected: The editor should save successfully due to the "Make Writable" button being used. In the event of it failing to save, the user should be warned.
Old 4.9.2 Steps
1. Set up a new blank project for source control using Subversion (I used TortoiseSVN)
2. Open the project, create a blueprint of the type "Actor" and check it in.
3. Open the newly created blueprint and edit it in some way (i.e. Add a print string node)
4. Press "Save"
5. When it prompts you to check the asset out, press the "Make Writable" function.
6. Edit the blueprint again (i.e. Delete the print string node)
7. Press "Save"
Result: The editor prompts you to check out the asset again.
Expected: The editor should just save like normal since you hit the "Make Writable" button.
Head over to the existing Questions & Answers thread and let us know what's up.
0 |
Fix Commit | 2784626 |
---|---|
Main Commit | 2800829 |
Created | Oct 22, 2015 |
---|---|
Resolved | Dec 1, 2015 |
Updated | Jun 7, 2016 |