paul chipchase 6108ee0529 Add a new config option 'engine.ini:[Core.VirtualizationModule]:DisableLazyInitIfInteractive' that can be used to override LazyInitConnections if we want the VA module to be able to use slate dialogs safely. ...

#rb none

- If we want to use slate dialogs we cannot use LazyInitConnections, however slate dialogs only work on programs that a) support slate and b) are running in some interactive form. Commandline programs, or the editor runnning in unattended mode or running a commandlet cannot make use of the slate dialog.
- If this new flag 'DisableLazyInitIfInteractive' is set to true and 'LazyInitConnections' is set to true then the VA system will lazy init its connections unless we are running an interactive program that could make use of the slate dialogs, in which case 'LazyInitConnections' is disabled for safety.
- Ideally we'd merge these two values into a single enum but I am hoping that we can change how we connect in the near term in which case we will simple deprecate 'DisableLazyInitIfInteractive'. The use case is pretty niche at the moment so this will probably be easier for the next stage of work.

[CL 26230486 by paul chipchase in ue5-main branch]

2023-06-26 06:21:23 -04:00

..

Private

Add a new config option 'engine.ini:[Core.VirtualizationModule]:DisableLazyInitIfInteractive' that can be used to override LazyInitConnections if we want the VA module to be able to use slate dialogs safely.

2023-06-26 06:21:23 -04:00

Public

Add a way for VA backends to supply additional errors for failed pull operations when calling FVirtualizationManager::OnPayloadPullError

2023-04-25 08:47:06 -04:00

Virtualization.Build.cs

Now if the VA source control backend fails to connect we can display a dialog to the user asking for the correct credentials directly. Currently disabled by default.

2023-06-20 04:26:06 -04:00