dingwat has quit [Quit: Connection closed for inactivity]
Ekho- has quit [Quit: CORE ERROR, SYSTEM HALTED.]
Degi has quit [Ping timeout: 260 seconds]
Degi has joined #scopehal
Ekho has joined #scopehal
dingwat has joined #scopehal
gurki has quit [Ping timeout: 260 seconds]
Stephie has joined #scopehal
Stephie- has quit [Read error: Connection reset by peer]
<d1b2>
<azonenberg> Ok hmmmm
<d1b2>
<azonenberg> So i'm getting ready to document the stream browser in the manual to get ready for the release
<d1b2>
<azonenberg> and i'm trying to think about some ways we can make it a bit more intuitive
<d1b2>
<azonenberg> I know we're nominally frozen but I don't want to go out of my way to document "wrong" or confusing behavior while we still have time to change/fix it
<d1b2>
<azonenberg> @fredo_62168 in particular, i don't like the multi step flows for changing things like sample rate and depth
<d1b2>
<azonenberg> i feel like we'd be better off moving the timebase dialog entirely into the sidebar and not having it be a separate popup
<d1b2>
<azonenberg> what is the benefit from a UX perspective of the extra step?
<d1b2>
<azonenberg> @aleksorsist @macaba any thoughts from you?
<d1b2>
<azonenberg> the more i look at it and start sketching up documentation, the less i like the link buttons
gurki has joined #scopehal
<d1b2>
<azonenberg> it may have been the easiest way to implement the code originally, but i don't think it's the right way
<d1b2>
<macaba> I agree the sidebar would be a great place for timebase controls, I tend to keep docking that dialog underneath. Failing that, a thunderscope specific default layout where the dialog is already docked under the sidebar. In some cases the dialog will always have a place to get to advanced features coming later, Iām not sure the timebase controls are included here. I can imagine a couple of advanced features later, and I suppose it could always
<d1b2>
return in a future version.
<d1b2>
<azonenberg> @macaba what i mean is we have timebase in the sidebar
<d1b2>
<azonenberg> it's just links that spawn the dialog
<d1b2>
<azonenberg> i dont see the point in the extra step
<d1b2>
<azonenberg> and yes channel controls make sense to have a dialog because there's so many different settings
<d1b2>
<azonenberg> the sidebar should only be for common stuff
<d1b2>
<azonenberg> (but we can potentially have a tree to exapnd to less common settings or something)
<d1b2>
<macaba> Ah yeah, might as well put a control in the space where the link currently is š
<d1b2>
<azonenberg> exactly
<d1b2>
<aleksorsist> Agreed, It's one of the most commonly used controls so it be top level
<d1b2>
<azonenberg> Sounds good, let me spend some time on that. also have to fix a few other bugs
<d1b2>
<azonenberg> Definitely feels like we're close but i dont want to rush a release and have problems
<d1b2>
<azonenberg> i want to get all of the measurement refactoring done, keep putting that off
<d1b2>
<azonenberg> ok yeah there's a bunch of things i need to work on in the sidebar
<d1b2>
<azonenberg> trying to make it a little more consistent with the rest of the UI