On 05/11/2025 17:51, Will Godfrey wrote:
I've been trying to produce a slimmed down but runnable Master window. It's proving to be surprisingly difficult, and could take some time :(
The code of the UI is quite large, and so I am asking myself what would be a good approach to strip it down, without requiring a massive amount of work on our side. We know that the sound output is not involved, because the crash also happens when Yoshimi was started with --null Furthermore, the crash happens before any sound was produced. Thus, in theory, we could take the whole synth engine out of the picture. But the practical problem is that the UI code gets the synth pointer. When looking through the code of MasterUI::make_window() I noticed that a lot of the buttons and controls do set an initial value, and trigger some communication for that. Do you think it might be feasible to go through make_window() and just comment all those calls out. And we might also go through all cb_*() functions in MasterUI.fl and remove any code from the body of those callbacks. What do you think? could that be a feasible approach to strip away as much of actual functionality in a first step? -- Hermann _______________________________________________ Yoshimi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
