#2051 closed task (fixed)
bad documented api-calls
Reported by: | Lennart Ochel | Owned by: | somebody |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Interactive Environment | Version: | trunk |
Keywords: | Cc: |
Description
From a user point of view the possible values of the most arguments from the API-calls are unknown (e.g.: setIndexReductionMethod, setPastOptModules, simulate, ...)
It is not possible to see what are the valid options for e.g. simulate(..., outputFormat="...").
Change History (9)
comment:1 by , 11 years ago
Milestone: | 1.9.0 → 1.9.1 |
---|
comment:3 by , 10 years ago
Milestone: | 1.9.1 → 1.9.2 |
---|
This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).
comment:4 by , 10 years ago
Milestone: | 1.9.2 → 1.9.3 |
---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:8 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
The situation has much improved since #2904 was closed. Unless there are specific points still to be addressed, I'd close this ticket.
Postponed until 1.9.1