Closed rhfogh closed 1 week ago
Hi @rhfogh,
Keeping / (carrying over) the parameters from previous dialogs is not possible in the GPhL workflow dialogs. Ill close the issue, please feel free to re-open if I did not answer your question
Excellent. Please do close the issue.
On 20/06/2024 07:04, Marcus Oscarsson wrote:
Hi @rhfogh https://github.com/rhfogh,
Keeping / (carrying over) the parameters from previous dialogs is not possible in the GPhL workflow dialogs. Ill close the issue, please feel free to re-open if I did not answer your question
— Reply to this email directly, view it on GitHub https://github.com/mxcube/mxcubeweb/issues/1256#issuecomment-2179884622, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACK5QEFI4TPU6GESW6K34KDZIJWFVAVCNFSM6AAAAABJSNSZNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZZHA4DINRSGI. You are receiving this because you were mentioned.Message ID: @.***>
This has been added in PR #1253. Can anyone tell me if this is also active in the JSON-Schema-driven popups made by Jean-Baptiste for Global Phasing?
The point is that for popups that are generated by code, complete with setting of default values, one does not want to reuse the last parameter values. If the GPhL workflow pops up a UI for a new crystal or a new acquisition step, you want it to use the default values set by the code, not the values used last time for a different crystal, which may be completely inappropriate.