The model picker now names both your session model and configured model when they differ.
What's wrong with this entry?
When you have a session-scoped model on top of a different configured one, the picker now names both and says the pick replaces both, instead of saying the session model will be undone. Models not otherwise in the list appear as extra entries labelled "Current model" and "Base model".
- The effort you choose in the picker is now applied as the session's effort rather than written to
effortLevelin your user settings, so it does not outlive the session. - The notice is built at runtime around the two model names; the fixed part is "). Selecting a model here replaces both."
). Selecting a model here replaces both.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Search field in the model picker
Both mention model
-
v2.1.236
Cancellable waits when
/modeltalks to a cloud sessionBoth mention model
-
v2.1.239
Requesting a model you are not permitted to use can now step down instead of failing
Both mention model