Community
Participate
Working Groups
Build Identifier: M20110210-1200 When a user cancels the search in an outline, the search form keeps its state but the displayed rows belong to the last executed search. Proposal: if a user cancels the search, all rows in the table should be discarded and the user show be notified of the canceled search. Reproducible: Always Steps to Reproduce: 1. Search in an outline 2. Results are displayed 3. Use a search that takes a while 4. Execute & cancel the search 5. Result of last search is still displayed but the search form shows the new search constraints
I'm not (yet) convinced that this is a sound proposal. Before we continue, please explain away the following two options: (1) this is not a framework issue. let the application decide and implement the desired behaviour (2) reset the search form to the previous state (so it matches the tables content) There might be also other options
Created attachment 213098 [details] Patch according to proposed solution
The option 2 would somehow violate the existing behaviour. If e.g. a form cannot be stored (VetoException), it's not just closed, it's kept open. In case of a search, the user might have spend several minutes creating a search (advanced search) and just forgot to add an addtional constraint. Thus it would not be a proper solution to just restore the last state, because the user would need to start again specifying the search constraints.
o If a user cancels the search, all rows in the table are discarded and the user is notified about the canceled search. o Additionally, any exception during loading the table data behaves the same: the table data is discarded and the table status is set appropriately. o If the severity of the table population status is IProcessingStatus.CANCEL, the table selection status is hidden and the population status is rendered like a warning (e.g. foreground color orange).
Used Stephan's patch as working base. Thank you for the contribution.
Bugfixes shipped on Scout 3.7 branch
