CuraApplication.py add startReloadAll signal when reloadAll is called

[dfries]

Description

Uranium/UM/Scene/Scene.py commit "Scene.py add _hideReloadMessage, connect to startReloadAll" Uranium pull request Ultimaker/Uranium#964 depends on this commit and the signal startReloadAll, which it will
use to cancel file modification reload dialog. Once all the models
are reloaded, the file modification reload dialog is not needed.

Type of change

• New feature (non-breaking change which adds functionality) I could argue this is a bug.

How Has This Been Tested?

• Exercise F5 reloadAll

1. Load a set of models
2. Externally modify a file
3. Verify "File has been modified" dialog shows, don't click it
4. Press F5, verify the new model shows and "File has been modified" dialog hides

Test Configuration:

• Operating System: Debian Linux

Checklist:

• My code follows the style guidelines of this project as described in UltiMaker Meta and Cura QML best practices
• I have read the Contribution guide
• I have commented my code, particularly in hard-to-understand areas
• I have uploaded any files required to test this change

[wawanbreton]

Hi @dfries, thanks for this change !
It looks overall good, however you are adding the startReloadAll signal in Cura, and using it in Uranium. Technically, Uranium is a standalone library (even though it is nowadays more of an integral part of Cura), and you are creating a dependency from Uranium to Cura, which is not allowed. Could you move this signal to QtApplication, which is part of Uranium ?

[github-actions]

Test Results

23 953 tests  ±0   23 951 ✅ ±0   47s ⏱️ -1s
     1 suites ±0        2 💤 ±0 
     1 files   ±0        0 ❌ ±0 

Results for commit 44c5788. ± Comparison against base commit 4e04d06.