View Changes: external changes desync state and trigger checks

External changes to source control are causing state desyncs which get expressed in code as multiple operations on the same items in the same UI visit. This check is in place because when only using the View Changes menu this should never happen. We need to make the View Changes data model resilient to external changes in the source control provider.

From UDN:

1. Have Editor connected to Perforce source control.
2. In your project, open a Map that uses OFPA.
3. Make an arbitrary change to an Actor and save it to force a Checkout.
4. Open the View Changes panel, hopefully the file will be listed in the default changelist.
5. In the P4 app, manually revert the file. Don't manually refresh in the View Changes panel!
6. Repeat step 3 to re-check out the file again.
7. You should observe the checkf being triggered in OnSourceControlCachedItemVisited.

How does TextureRenderTarget2D get TArray<uint8> type data?

How do I set a material as a post-processing material?

How to delete some elements correctly when deleting an array loop?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

Why does the REMOVE method of map container remove elements have memory leaks?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

UMG RichText not appear image when packaged

How does TArray loop correctly remove elements in blueprints?

What is the difference between Camera and CineCamera?

In UE5.4, custom variables in the level blueprint cannot be set to default values, and the eyedropper tool is also unavailable, whereas in UE4.27, these features work normally.