Feature request #5396
Run algorithms in a different thread
Status: | Closed | ||
---|---|---|---|
Priority: | High | ||
Assignee: | Victor Olaya | ||
Category: | Processing/Core | ||
Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
Easy fix?: | No | Copied to github as #: | 15067 |
Description
Currently the module execution freezes the main GUI.
Execution of the modules should not be done on the main thread.
Related issues
History
#1 Updated by Camilo Polymeris over 12 years ago
I'll have a look at this during the next days, if nobody else is working on it.
#2 Updated by Victor Olaya over 12 years ago
Perfect!
There is a class named AlgorithmExecutor. That's where it should go. If you have questions, just ask me, ok?
#3 Updated by Camilo Polymeris over 12 years ago
Was implementing this in the GUI code, but am not longer sure that is the right approach. Perhaps it should be lower level, so the functionality can be used in other parts of the code?
#4 Updated by Victor Olaya over 12 years ago
IT should go on the AlgorithmExecutor Class. All other classes call it when executing an algorithm. It is on the gui package because it is used by gui elements, but we can move it later to another one. It is not itself a GUI class.
#5 Updated by Paolo Cavallini over 12 years ago
- Assignee changed from Victor Olaya to Camilo Polymeris
#6 Updated by Camilo Polymeris over 12 years ago
- File mt3.diff added
This weeks diff. Includes mostly GUI improvements (percentage, feedback and a close button) and some attempts at making the iteration code work. I'll update the blog at sextante-gsoc.blogspot.com with more details, but here some technical considerations:
- Am getting crashes with the (working thread) iteration code, apparently accesses to QPixmap, but haven't been able to find the source of the problem.
- Using "new-style" PyQT slots and signals. Is that ok?
Note that the cancel button only disconnects the finished signal, since the backends don't support cancelling. One could just terminate them, but that might be problematic (file access and such).
#7 Updated by Camilo Polymeris over 12 years ago
- File mt4.diff added
Iteration should work with the attached patch.
#8 Updated by Giovanni Manghi about 10 years ago
- Project changed from 78 to QGIS Application
- Category deleted (
63)
#9 Updated by Giovanni Manghi about 10 years ago
- Category set to Processing/Core
#10 Updated by Giovanni Manghi about 10 years ago
- Assignee changed from Camilo Polymeris to Victor Olaya
#11 Updated by Paolo Cavallini about 10 years ago
Possibly duplicated in #11324
#12 Updated by Giovanni Manghi over 9 years ago
- Status changed from Open to In Progress
- Priority changed from Normal to High
- Target version set to Future Release - High Priority
work undergoing as google summer of code
http://www.google-melange.com/gsoc/project/details/google/gsoc2015/mvcs/5741031244955648
#13 Updated by Giovanni Manghi over 7 years ago
- Easy fix? set to No
#14 Updated by Alexander Bruy about 7 years ago
- Status changed from In Progress to Closed
- Description updated (diff)
- Resolution set to fixed/implemented
Fixed in master