Closed jensschmeink closed 4 days ago
I would even say, that if a task is running, other projects should be greyed out / be inactive instead of showing a warning.
@rainman110 I would in this case disconnect all signals and turn the project dockwidget into the background/unclickable. But I do not really understand how all of this works. I would use gt::currentProcessExecutor().taskCurrentlyRunning()
to check whether a task is running, but at what point can I access the widgets and diasble them ? Is there a loop for the execution ? This should work with a signal slot in the app, shouldnt it ?
@NitenIchiry Without having had a look into the code. I would not disconnect any signals though. There is a QSignalBlocker
object that you can use to temporarily disable passing signals .
I would though check in the code, where the warning message widget is created, to only generate it, if a task is running and if the project is not the current project. Let me find out, where the message box is generated...
@NitenIchiry Please see here:
You simply need to add a check, whether the current project is not the one to switch
Summary
If you have a open Project and you double click it in the explorer while a task is running there will be a warning in a dialog
Expected Behaviour
As the project is the open project no warning should occur
Reproduction steps
Screenshots
Logs
No response
GTlab environment
OS
Windows