Run multiple queries
Bug #882539 reported by
Mathias Dannesbo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
TAPAAL |
Fix Released
|
Wishlist
|
Peter Haahr Taankvist |
Bug Description
Make it possible to run multiple queries subsequent.
Eg. by Ctrl- or Shift- clicking multiple queries in the list and and click "Verify".
Related branches
lp:~tapaal-contributor/tapaal/partial-order
- Jiri Srba: Approve
- Peter Haahr Taankvist (community): Needs Resubmitting
-
Diff: 257 lines (+72/-10)4 files modifiedsrc/dk/aau/cs/gui/BatchProcessingDialog.java (+48/-2)
src/dk/aau/cs/verification/batchProcessing/BatchProcessingVerificationOptions.java (+13/-3)
src/dk/aau/cs/verification/batchProcessing/BatchProcessingWorker.java (+8/-2)
src/pipe/dataLayer/TAPNQuery.java (+3/-3)
lp:~ptaank/tapaal/run-multiple-queries-
- Jiri Srba: Approve
- Peter Haahr Taankvist (community): Needs Resubmitting
-
Diff: 553 lines (+197/-61)6 files modifiedsrc/dk/aau/cs/gui/BatchProcessingDialog.java (+55/-6)
src/dk/aau/cs/verification/batchProcessing/BatchProcessingWorker.java (+9/-1)
src/pipe/gui/GuiFrame.java (+25/-10)
src/pipe/gui/undo/RemoveQueriesCommand.java (+32/-0)
src/pipe/gui/undo/RemoveQueryCommand.java (+0/-22)
src/pipe/gui/widgets/QueryPane.java (+76/-22)
Changed in tapaal: | |
status: | New → Confirmed |
Changed in tapaal: | |
importance: | Medium → Wishlist |
Changed in tapaal: | |
milestone: | 2.1.0 → none |
Changed in tapaal: | |
assignee: | nobody → Peter Haahr Taankvist (ptaank) |
Changed in tapaal: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
A solution could be, if multiple queries are selected and the user clicks verify that the models are automatically loaded into the batch processing and run there.
The problem is though, what will be the functionality, if multiple queries are selected and the user clicks "Edit"?
Perhaps a better solution to get an overview of satisfied queries would be to mark queries with green/red icons before them
remembering the most recent verification result. Of course, if the query or model is changed, the flags of all queries
should be resent to "don't know" immediately too.