02:01 <d1b2> <azonenberg> Ok done with work for the day. So, agenda for tonight is to check out the specan stream browser stuff

02:01 <d1b2> <azonenberg> then try the new imgui patch workaround to see if it solves our issue

02:43 <d1b2> <vipqualitypost> I’m using brew, not sure how similar that is to macports. My issue was related to installing x86_64 somehow over the arm64 one I think.

03:02 <_whitenotifier-4> [scopehal-apps] azonenberg closed pull request #799: Specan fixes - https://github.com/ngscopeclient/scopehal-apps/pull/799

03:02 <_whitenotifier-4> [scopehal-apps] azonenberg pushed 5 commits to master [+0/-0/±10] https://github.com/ngscopeclient/scopehal-apps/compare/2d15f099f598...e789cb278c3b

03:02 <_whitenotifier-4> [scopehal-apps] azonenberg e789cb2 - Merge pull request #799 from fredzo/specans-fixes Specan fixes

03:36 <_whitenotifier-4> [scopehal-apps] azonenberg commented on issue #798: Migrate from GLFW to SDL - https://github.com/ngscopeclient/scopehal-apps/issues/798#issuecomment-2456161930

03:37 <d1b2> <azonenberg> woo good news

03:38 <d1b2> <azonenberg> i just tested a fix from Omar and it looks like our drag and drop issues on Linux should be fixed. this also will eliminate the need for a bunch of ugly workarounds we have for tooltips and stuff

03:38 <d1b2> <azonenberg> root cause is an upstream GLFW bug or at least quirk of the data model (somewhat arguable if it's a bug or bad design working as intended)

03:38 <d1b2> <azonenberg> but either way we shouldnt have to worry about it anymore

03:39 <d1b2> <azonenberg> it's not merged yet, but should be shortly

07:49 <d1b2> <fredzo_72653> That's great news! Congrats!

08:09 <_whitenotifier-4> [scopehal-apps] bvernoux commented on issue #800: Compile fails on Windows (Could not find a package configuration file provided by "yaml-cpp") - https://github.com/ngscopeclient/scopehal-apps/issues/800#issuecomment-2456495405

08:11 <_whitenotifier-4> [scopehal-apps] bvernoux edited a comment on issue #800: Compile fails on Windows (Could not find a package configuration file provided by "yaml-cpp") - https://github.com/ngscopeclient/scopehal-apps/issues/800#issuecomment-2456495405

12:50 <_whitenotifier-4> [scopehal-apps] fredzo opened pull request #801: Stream browser filter rendering - https://github.com/ngscopeclient/scopehal-apps/pull/801

12:53 <d1b2> <fredzo_72653> @azonenberg this one is for Filter rendering in StreamBrowserDialog: https://github.com/ngscopeclient/scopehal-apps/pull/801

12:53 <d1b2> <fredzo_72653> https://cdn.discordapp.com/attachments/776941750291267595/1303341430210691122/Capture.PNG?ex=672b66cb&is=672a154b&hm=58ed496c6e5f5a80505a3ef140f945e5f30cac38fa415dfaffb395b0b16c9efb&

12:54 <d1b2> <fredzo_72653> Just basic coloring / properties display + link to filter properties dialog

15:47 <d1b2> <azonenberg> Looks good as a starting point, we'll definitely want to improve on it

15:47 <d1b2> <azonenberg> but better than what we had

15:51 <d1b2> <azonenberg> One thing i need to spend some time on is figuring out the best balance for defaults

15:52 <d1b2> <azonenberg> of what tree nodes we expand vs what we don't

15:52 <d1b2> <azonenberg> making it so details are visible where important but we dont make people scroll through ten screens of information on more complex setups

15:52 <d1b2> <azonenberg> It may have to be adaptive, where once the number of nodes exceeds some amonut they stop opening by default or something

15:52 <d1b2> <azonenberg> idk yet

15:52 <d1b2> <azonenberg> i just see it as an area we can improve on

15:53 <_whitenotifier-4> [scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±1] https://github.com/ngscopeclient/scopehal-apps/compare/e789cb278c3b...195162a376d3

15:53 <_whitenotifier-4> [scopehal-apps] azonenberg 195162a - Sync with upstream imgui

17:24 <d1b2> <fredzo_72653> Yes I was thinking the same, like for the 16 digital channels of a scope, it doesn't make sense to have them shown by default, especially if they are disabled, BUT it would be nice to have the DISABLED badge act as an on/off toggle. Decision decision... Maybe we should create a parent "Digital" node for digital channels, and make it collapsed by default if the channels are disabled ?

17:26 <d1b2> <fredzo_72653> BTW Digital channels are already collapsed (properties hidden) by default vs. analog channels are expanded, but even collapses, that's 16 lines in the window.

17:40 <d1b2> <azonenberg> Yeah. I dont have all the answers yet

17:40 <d1b2> <azonenberg> I just want to pay attention to scalability of the GUI in general

17:40 <d1b2> <azonenberg> as far as being able to work well with complex setups that have a lot of channels and not be difficult to navigate