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
<azonenberg> Zevv: because it's already open
<azonenberg> it won't let you open another one
Degi has quit [Ping timeout: 244 seconds]
Degi has joined #scopehal
<Zevv> duh silly me
benishor has quit [Quit: tah tah!]
benishor has joined #scopehal
<_whitenotifier-4> [scopehal] zevv edited pull request #950: Refactored SCPITMCTransport - https://github.com/ngscopeclient/scopehal/pull/950
<_whitenotifier-4> [scopehal] zevv edited pull request #950: Refactored SCPITMCTransport - https://github.com/ngscopeclient/scopehal/pull/950
<Zevv> I'm having a bit of a trivial stupid issue with entering values in properties dialogs, I'm simply not able to change them. For example a 'sine' module, freq or srate properties are stuck, any value I enter is simply ignored. Do I miss something?
<azonenberg> Zevv: are you hitting enter after you type the new value? does the display revert to the old value or something?
<azonenberg> are you using the correct unit suffix, e.g. "10M" for 10 MHz or so?
<azonenberg> 10 without any context means 10 Hz
<azonenberg> (and 10m means 10 millihertz)
<Zevv> yeah I think so
<Zevv> i'll go see whta's happening under the hood
<Zevv> ah it's imgui direct mode acting up I think: I have two different dialogs open allowing me to set the same parameters. For example, I ad a 'sine' module, then "sine_1' will pop up. Now on the node editor I do a right click the same dialog comes up, but not in a window now but as a popup
<Zevv> in this case the new dialog does not accept values. When closing the initial `sine_1` window, it does work
<azonenberg> ohhh. ok yeah if you have two properties windows open at once i could see them stepping on each other
<azonenberg> file a ticket, that's something we should work on - maybe if you right click and the dialog is open it should shift focus there instead of spawning a popup
<Zevv> does that go on scopehal or scopehal-apps
<Zevv> latter I guess
<azonenberg> -apps, its a gui issue not a backend one
<azonenberg> i should also probably change the default of spawning the properties dialog when a filter is created
<Zevv> yeah i figured
<Zevv> yeah i was a bit confused why I got the same dialog twice
<azonenberg> a lot of that is legacy history. the graph started out (in the glscopeclient era) as being purely a visualization of the filter interconnects
<azonenberg> and gradually has become a more fundamental part of the ui
<_whitenotifier-4> [scopehal-apps] zevv opened issue #816: Entered data is not accepted when the same value is open in two dialogs - https://github.com/ngscopeclient/scopehal-apps/issues/816
<Zevv> yeah I get that. that's evolution for you
<azonenberg> way back in the day
<azonenberg> strict columnar layout, square corners, no freedom of layout, i dont even think you could drag ot make connections
<azonenberg> to*
<Zevv> the current impl looks nice and acts friendly
<Zevv> i like the shoving
<azonenberg> yeah there's still things i want to improve
<azonenberg> but compared to the past its a vast improvement
<azonenberg> e.g. i would like to eventually have lines autoroute around nodes rather than crossing through them
<azonenberg> we currently have collision physics between nodes, but not lines and nodes
<Zevv> graphviz
<azonenberg> that's a) a potential license issue, i'm pretty sure it's GPL which isn't compatible with our BSD license (only the other way around
<azonenberg> and b) not really meant for real time interactive use
<azonenberg> some of the algorithms they use might be possible to reimplement though
<Zevv> i know. and also with gv graphs tend to get messy when getting more compex
<azonenberg> yeah. it's also not really meant for things you're hand dragging
<azonenberg> it's entirely an auto layout
<azonenberg> i want fully manual node layout with collision physics, but also autorouting of lines around nodes rather than the simple splines we have now
<Zevv> that's the whole point. But they do have a way to route the graph edges around the nodes. but its pretty quirky at times.
<azonenberg> the low level graph widget is a third party lib we use that i may end up forking
<azonenberg> as it's not very frequently updated upstream
<Zevv> if it aint broken
<azonenberg> i think we soft-forked it already actually
<azonenberg> because upstream imgui made some breaking api changes and upstrream didn't sync
<azonenberg> upstream imgui-node-editor i mean
<azonenberg> so i had to fix the graph widget to use the new imgui fteatures
<Zevv> anyhow, there's a lot to like about all this. I'm an avid user of baudline even thought it's hopelessly outdated. This brings a lot of the same vibe and goodies.
<Zevv> would you be interested in having jack audio as a virtual instrument
<azonenberg> There is an open wishlist for audio interfacing as both a virtual scope and function generator
<azonenberg> using whatever platform dependendt or abtracted APIs
<azonenberg> details TBD
<Zevv> right
sgstair_ is now known as sgstair