Swap PluginRunner
with TaskRunner
#1360
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Minor changes:
PixelProcessor
Major change:
PluginRunner
toTaskRunner
QPEx.createTaskRunner()
andQPEx.createTaskRunner(int nThreads)
methodsThe reasoning is that
PluginRunner
no longer really makes sense as a name: the class rather represents a simple and generic way to run tasks in parallel. It's also more general than in previous QuPath releases.The following script shows it in action:
When run interactively, this should show a progress dialog (after a short delay). But when using Run for project it will switch to using a command line task runner, and not generate a new dialog of its own.
The number of threads can also be specified. For example, for single-threaded tasks we can use
This is an easy way to provide a progress monitor for multiple tasks.