<d1b2>
<azonenberg> Latest round of filter icons merged
<d1b2>
<chille0417> 🦈 ▶️
<d1b2>
<azonenberg> yep lol
<d1b2>
<azonenberg> There's a matching export icon i havent written the filter block but the icon already exists
<d1b2>
<azonenberg> can never have too many shorks in your code
ALTracer has quit [Remote host closed the connection]
ALTracer has joined #scopehal
ALTracer has quit [Quit: Quit]
<d1b2>
<chille0417> @azonenberg The OWON HDS200 series have devices with and without an AWG. I can check for an AWG by looking at the model number in SCPIDevice::m_model. But this will require a device to be connected and reply to an *IDN? before knowing if there is an AWG or not. I'm thinking that maybe someone want to be able to prepare a workspace without connecting the hardware. Any ideas how to do this in ngscopeclient? I'm thinking that maybe there
<d1b2>
should be some settings in the GUI that can enable/disable the AWG option. The constructor should auto enable this option whenever a user connects to an instrument with an AWG. Or maybe the exact model should configurable from the GUI? There might be some other model specific things like timebase settings and bandwidth limiting.
<d1b2>
<azonenberg> So generally speaking we detect what features the device has at connection time
<d1b2>
<azonenberg> And then these settings are saved to the scopesession
<d1b2>
<azonenberg> what's missing is the ability to load the AWG channel config offline; the MockOscilloscope class is (as the name implies) just a scope
<d1b2>
<azonenberg> and we don't have proper offline load support for other instrument types yet
<d1b2>
<chille0417> Hmm... okay. Then I will just stick to parsing m_model for now.
<d1b2>
<azonenberg> Yeah this is a longer term todo but not a blocker for the v0.1 release
<d1b2>
<azonenberg> since scopes are obviously the most improtant use case right now
<d1b2>
<chille0417> Some day I would like to propose a API for configuring things runtime. This would be great of things like offline configuration and such. I think it should be quite easy actually. I have done similar things in other projects before. But for now i will priotize to get the OWON driver working first.
<d1b2>
<azonenberg> More offline configuration kinda ties into the broader goal of being able to transition seamlessly between on- and off-line mode operation
<d1b2>
<azonenberg> so that if you lose connectivity to a scope you don't just hang ngscopeclient
<d1b2>
<azonenberg> it should print out a warning then switch to offline mode and give you the option to reconnect