azonenberg changed the topic of #scopehal to: ngscopeclient, libscopehal, and libscopeprotocols development and testing | https://github.com/ngscopeclient/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
Degi has quit [Ping timeout: 252 seconds]
Degi_ has joined #scopehal
Degi_ is now known as Degi
skipwich has quit [Remote host closed the connection]
skipwich has joined #scopehal
skipwich has quit [Remote host closed the connection]
skipwich has joined #scopehal
skipwich has quit [Remote host closed the connection]
skipwich has joined #scopehal
skipwich_ has joined #scopehal
skipwich has quit [Ping timeout: 252 seconds]
skipwich_ is now known as skipwich
skipwich_ has joined #scopehal
skipwich has quit [Ping timeout: 276 seconds]
skipwich_ is now known as skipwich
skipwich has quit [Remote host closed the connection]
skipwich has joined #scopehal
skipwich has quit [Remote host closed the connection]
skipwich has joined #scopehal
skipwich has quit [Remote host closed the connection]
skipwich has joined #scopehal
<_whitenotifier-3> [scopehal-apps] azonenberg opened issue #730: Don't allow scrolling or zooming the timeline to the point of overflowing int64 timestamps - https://github.com/ngscopeclient/scopehal-apps/issues/730
<azonenberg> Hmmm random thought
<azonenberg> Given that the filter graph is intended to be one of the primary ways to interact with ngscopeclient
<azonenberg> Should we have it open by default so it's easier to find and saves a few clicks having to open it every time?
<azonenberg> (probably in a second tab behind the waveform views although you can rearrange it)
<d1b2> <azonenberg> @aleksorsist any thoughts from your end?
<azonenberg> (also more generally, we should have another dev call soon it's been a while)
<d1b2> <aleksorsist> I think having it be in a second tab is a good idea
<d1b2> <aleksorsist> I wouldn't want to have it always on my screen though, nor there right away
<d1b2> <david.rysk> the discoverability of some of the UI is not very clear to me 😄
<d1b2> <david.rysk> e.g. how to do measurements etc
<azonenberg> yeah generally improving the new user experience is one of the big things i want to work on
<azonenberg> fundamentally one of the problems is that i'm essentially the only dev on the frontend side of things
<azonenberg> we have a bunch of people doing driver, filter, and build system work from time to time
<azonenberg> it's been months if not years since we've had a substantial contributor on the GUI side
<azonenberg> we've never had an actual UI/UX designer take a look at the project
<_whitenotifier-3> [scopehal-apps] azonenberg pushed 2 commits to master [+0/-0/±2] https://github.com/ngscopeclient/scopehal-apps/compare/e75c0bd1eed4...623a3f5d19b9
<_whitenotifier-3> [scopehal-apps] azonenberg 0f2b1c3 - Partial support for renaming docked waveform groups
<_whitenotifier-3> [scopehal-apps] azonenberg 623a3f5 - Cleaned up some unnecessary code for hit testing
<_whitenotifier-3> [scopehal-apps] azonenberg pushed 5 commits to master [+0/-0/±12] https://github.com/ngscopeclient/scopehal-apps/compare/623a3f5d19b9...6c96adfd87aa
<_whitenotifier-3> [scopehal-apps] azonenberg fa78a29 - Even more cleanup of group renaming
<_whitenotifier-3> [scopehal-apps] azonenberg fd47078 - Added initial skeleton method for doing configuration of a new session. Doesn't spawn anything yet.
<_whitenotifier-3> [scopehal-apps] azonenberg cd38518 - Updated to latest upstream imgui
<_whitenotifier-3> [scopehal-apps] ... and 2 more commits.
Yamakaja has quit [Quit: Bye]
Yamakaja has joined #scopehal
Yamakaja has joined #scopehal