aboutsummaryrefslogtreecommitdiff
path: root/application/pages/modplatform/flame
diff options
context:
space:
mode:
authorJamie Mansfield <jmansfield@cadixdev.org>2021-03-26 20:03:57 +0000
committerJamie Mansfield <jmansfield@cadixdev.org>2021-03-26 20:03:57 +0000
commit8e6400e8d8c3a2ec1b734c4405b27dd2b547a835 (patch)
treed37e139003701d3177c95004dd174d8b81c0eee1 /application/pages/modplatform/flame
parent73af0f271adba6a4165e0ed36c9ae436f849f9c7 (diff)
downloadPrismLauncher-8e6400e8d8c3a2ec1b734c4405b27dd2b547a835.tar.gz
PrismLauncher-8e6400e8d8c3a2ec1b734c4405b27dd2b547a835.tar.bz2
PrismLauncher-8e6400e8d8c3a2ec1b734c4405b27dd2b547a835.zip
NOISSUE Fix edgecase where new searches won't be processed
This resolves an issue with the modpacks.ch search functionality, in which a search issued while one is currently in progress won't be made and the UI won't allow for the search to be made after. Reproduction Steps: 1. Open the FTB pane in the Add Instance Dialog 2. Perform a search while MMC is still performing the initial search The search won't be performed, the existing search will have been aborted, and you are unable to try the search again (without trying a different search in the meantime). This was caused by 2 things: 1. A search cannot be re-attempted, and this logic doesn't consider failures. 2. The failure slot wasn't called when the NetJob was aborted, so the search would never be performed - but the term would be stored as if it had (trigering point 1). I have resolved this by doing 2 things: 1. If the failure slot is called, set a searchState of Failed. Allow search re-attempts in this case. 2. If there is a present NetJob, abort and reset it. The immediately continue with the search.
Diffstat (limited to 'application/pages/modplatform/flame')
0 files changed, 0 insertions, 0 deletions