<d1b2>
<Aleksorsist> Time to publish the first community control layout for it, any secret shortcuts that I could bind to the various buttons?
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 250 seconds]
Degi_ is now known as Degi
<azonenberg>
Nice
<azonenberg>
glscopeclient doesnt have much in the way of keyboard automation at the moment
<azonenberg>
i think mouse buttons 8 and 9 are bound to start and stop trigger
<d1b2>
<Aleksorsist> Would be nice to have shortcuts for trigger menu (Ctrl-T?) and channel menus (Ctrl-1 for CH1, etc.)
<azonenberg>
The problem with the latter is that it's ambiguous
<azonenberg>
what if you have more than one scope connected?
<azonenberg>
multi instrument is a core feature of the platform
<d1b2>
<Aleksorsist> Touche, though some sort of keyboard control would make a USB hid oscilloscope control surface much easier to use with scopeclient
<d1b2>
<Aleksorsist> (this is another mini-project of mine, for all the button and knob scope fans)
<d1b2>
<Aleksorsist> Could do a shortcut to select a specific instrument then another to select a channel
<azonenberg>
Yeah there's options
<azonenberg>
But thats the kind of thing i want to work on after we've fixed a bunch of other more fundamental issues
<azonenberg>
like documentation and stability
<azonenberg>
And fully deprecated glscopeclient
<azonenberg>
there are a lot of things i want to do that will involve more sweeping code changes that i dont want to result in having to apply the same fix to two UIs
<d1b2>
<Aleksorsist> Those are definitely the priority! I can't wait for a solid windows build script myself
<d1b2>
<Aleksorsist> Though I look forward to helping fund UI/Accessibly work with the launch of ThunderScope
<azonenberg>
As soon as we get rid of glscopeclient, we can start building a purely visual studio (no mingw) windows build flow
<azonenberg>
GTK is holding us back there
<d1b2>
<Aleksorsist> I figured, it even made compiling on arch a PITA
<azonenberg>
Core accessibility work for things like screenreader support will require improvements to the GUI toolkit, that was one of the downsides to imgui vs GTK
<azonenberg>
They are open to it, but dont currently have funding dedicated to it
<azonenberg>
I've had it flagged as a fairly low priority because it's an inherently graphical tool
<azonenberg>
there are some potential fixes we can make wrt having options to reduce framerates for folks with sensitivity to fast motion
<azonenberg>
making the default colors reasonably colorblind friendly and easily changeable in preferences
<d1b2>
<Aleksorsist> Makes sense, I'd love to have the option to use only a keyboard, since that's much easier to map to other controls
<azonenberg>
File a ticket for it, but it'll definitely be a ways out as there are things that are both higher priority and prerequisites
<d1b2>
<Aleksorsist> You use GitHub issues right? I can add it onto the pile lol
<azonenberg>
Yeah
<azonenberg>
against scopehal-apps not scopehal, since this is a GUI side issue
<d1b2>
<Aleksorsist> Can do, how's the move away from GL going?
<azonenberg>
I havent touched much code in a few weeks since i've been busy with work and writing the ngscopeclient manual in my spare time