05:22 <d1b2> <azonenberg> Prelimianry UI mockup of the confirmation dialog

05:22 <d1b2> <azonenberg> https://cdn.discordapp.com/attachments/776941750291267595/1163708481031905350/ui-mockup.png?ex=65408efa&is=652e19fa&hm=08d7678da57a6b930b74a69fe608e7df7242da743cb635007bc59824ba43dd40&

05:22 <d1b2> <azonenberg> Anyone have thoughts?

05:33 <d1b2> <johnsel> I just feel sad you pinged everyone but me 2 days ago lol

05:34 <d1b2> <johnsel> Looks good though, I like it. Might want to create a path to continue without aborting fully?

05:34 <d1b2> <johnsel> Partial apply or something like that

05:35 <d1b2> <johnsel> Or load “offline” instead

05:49 <juh> ^ maybe radio buttons to choose which setting to load, defaulting to the safer option

05:49 <juh> doubling as a checklist for the user to ensure that everything is hooked up as it should be

06:02 <azonenberg> Converting to offline load would be nice to add eventually

06:02 <azonenberg> But that's going to be part of a broader online/offline conversion refactoring

06:02 <azonenberg> it's less trivial than you'd think because it involves swapping out a driver-based scope for a mock scope after you're halfway through loading and have pointers all over the place pointing to it

06:06 <azonenberg> Per setting load would be a *huge* amount of work

06:06 <azonenberg> And it would also lead to confusing inconsistencies where e.g. displayed waveforms don't match the actual hardware settings

06:06 <azonenberg> The intent of a session is to put you exactly where you left off