Open grumpyinca opened 2 years ago
In today's conversation Bri came up with an idea to have a Search operation that produces an infeasible result produce two buttons: "Extended Search" and "Trade". From there, if the user makes any change to the design, the button selection would immediately switch to the current situation of a Search or Seek button depending on feasibility.
In summary, this issue visualizes the development of a multi-Search function. As proposed, this issue overlaps with #615.
Observation of usage log information shows that it is common user behavior to invoke multiple consecutive searches without intervening changes even though the second search shows no improvement.
This Extended Search / multi-Search idea is that if the user invokes a second search after a first search has returned an infeasible result and no model changes have been made (see details in #615), a number of specific app behaviors would result. These might include:
A pop-up "begin" modal featuring: 1.a. Brief text explaining the issues (including warning that this might take a while) 1.b. Possibly an informational tooltip providing more detail 1.c. Context Help button and associated Help file 1.d Cancel and Continue buttons
Change Preference values to match those established by the tweakPrefs script.
Multiple Searches with different start points 3.a. The current start point 3.b. A start point with each free independent variable incremented by 1%. 3.c. A start point that matches the default design for that design type and units.
Selection of the best result