Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for Marking Database for Delete in Perforce #42

Merged
merged 1 commit into from
Aug 19, 2021

Conversation

brwarner
Copy link
Contributor

This fixes a bug for Perforce users where triggering a rebuild of the generated Articy code would mark your package and database assets for "Delete" in Perforce despite the fact they'd been regenerated. They are now correctly checked out for edit instead.

Tested in Unreal 4.26. Builds in Unreal 5.

@brwarner brwarner merged commit d450c07 into development Aug 19, 2021
@brwarner brwarner deleted the stop-perforce-delete branch August 19, 2021 18:29
@brwarner brwarner linked an issue Aug 19, 2021 that may be closed by this pull request
brwarner added a commit that referenced this pull request Aug 21, 2021
* Updated to latest UE API for UE 4.27 and UE 5

* Fixed preprocessor directives for UE 5

* Fixed script method string return type

* Update ArticyImportData.cpp

Fixed a Bug where <id>.<id> string patterns were replaced by an GV access even if that pattern occured within a literal string.

* UE5 Support (#41)

* Update README.md

Added info for UE 5

* Fixed missing articy toolbar buttons. They now live in the Settings menu.

* Removed note about broken UI from Readme

* Guarding UE5 changes with #if's

* Updating Readme so it applies to both UE4 and 5

* Fixing registration order

Co-authored-by: Peter Sabath <31621424+peter-sabath@users.noreply.github.com>

* Use CheckoutPackages and SavePackages instead of PromptForCheckoutAndSave (#42)

* Updating Changelog

Co-authored-by: Christian Schildt <38693641+christian-schildt@users.noreply.github.com>
Co-authored-by: Peter Sabath <31621424+peter-sabath@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant