{"id":287,"date":"2026-04-17T12:00:53","date_gmt":"2026-04-17T12:00:53","guid":{"rendered":"https:\/\/togo-lab.io\/?p=287"},"modified":"2026-04-20T12:54:56","modified_gmt":"2026-04-20T12:54:56","slug":"project-0003-sdg2042x-gui-v0-2-first-patch-round-and-tracker-setup","status":"publish","type":"post","link":"https:\/\/togo-lab.io\/?p=287","title":{"rendered":"Project 0003: SDG2042X GUI v0.2.* \u2014 first patch round and bug tracker setup"},"content":{"rendered":"

The current work on my Linux GUI for the Siglent SDG2042X<\/a> is about findig bugs before piling more features on top.<\/p>\n

Version 0.1<\/a> already did the basics: Waveform control, burst and sweep settings, ARB handling, presets, a small SCPI console, and screenshot support. But no software without bugs. So besides the first code fixes, I also set up a proper issue tracker<\/a> for the project in Gitea (this was also a point in my gitea learning 2Do List). The repository now has labels, issue templates, a small board workflow, and the first full review list entered as issues. For this first round, I started with the items that looked most worth fixing immediately: #1<\/code>, #2<\/code>, & #12<\/code>. I also did #6<\/code> as it was a little bit annoing thing. <\/p>\n

The code side for those is already done in v0.2<\/a> in this git. What is still open is real verification against the actual SDG hardware before I close them.<\/p>\n

Current issue list<\/h4>\n

Find this in the Gitea: https:\/\/gitea.togo-lab.io\/tgohle\/0003-SDG2042X-PyQt-GUI-for-Linux\/issues<\/a><\/p>\n

Status of the project is now (18.04.2026):<\/h4>\n

I wrote and ran a small test script for issues #1, #2, #6, and #12, plus a final hardware check on the SDG itself:\nhttps:\/\/gitea.togo-lab.io\/tgohle\/0003-SDG2042X-PyQt-GUI-for-Linux\/src\/branch\/master\/script\/archive\/V0.2<\/a>\nThat gives me enough confidence to close all four issues and move this first bug-fix round a step further toward done.<\/p>\n