Ticket #185 (closed: fixed)
Output Parameters
Reported by: | Nick Draper | Owned by: | Roman Tolchenov |
---|---|---|---|
Priority: | major | Milestone: | Iteration 11 |
Component: | Keywords: | parameters | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
It has become apparent that some algorithms need to output more than just workspaces. The use of Parameters solely for output will cover these situations.
Currently we have a direction concept for workspace parameters, This needs to be moved up the inheritance tree to apply to all parameters. The default should of course be input, but we should also allow for output in InputOutput parameters.
Areas you need to consider when implementing this.
- Validation - when and where to apply will differ for input and output parameters
- Information outputted to the log - on algorithms execution only input and inout parameters should be logged. On completion inout and output parameters need to be logged. All parameters need to be stored in the algorithm history (with the direction included)
- Changes in the UI - The input dialog box should only ask for input for in and inout.
Change History
Note: See
TracTickets for help on using
tickets.
(In [1249]) re #185. All algorithm parameters now have direction: Input, Output, or InOut. Output parameters (except workspaces) are not shown in the ExecuteAlgorithm dialog box in QtiPlot.