On Tue, 17 Sep 2024 21:04:38 +0200
ichthyo <p...@ichthyostega.de> wrote:
>> Another possibility that might be practical is to use the switch setting to
>> enable/disable the timing code. That way, the only overhead would be a
>> couple of bool tests.
DOH!
Just actually looked at the code. The switch is already there! I've just
modified it slightly so it encloses both the initial time call, as well as the
comparison, so I've made it permanently active and removed the build option.
Running a quite hardworking project that always gives three Xruns when the
buffer size is only 64 frames, still gives the same whether or not note
reporting is included.
>Another tiny observation: in the "Main Settings" tab of the settings dialog,
>the drop-down list at bottom "Mixer Pannel Layout" is empty, even while the
>actual setting (one row with 16 strips) is retained correctly. Is this the
>case also on your system? maybe my default configuration is not up-to-date.
>I could find the callback where changes to this selection are forwarded to
>the core, but I could not find the code which processes and sets the current
>state. Maybe you can recall the place where this happens?
I'm not seeing this here. However, if you just nudge the mixer window size, does
it then correctly show? If so, it's an FLTK redraw timeout. We've had this in
other places, and the solution was to make {window}Rtext() to repeat several
times on 'show()'
--
Will J Godfrey
_______________________________________________
Yoshimi-devel mailing list
Yoshimi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
