To make it even clearer for the upstream developer, it's a data
synchronisation issue between the instances of qjackctlSetupForm and
qjackctlMainForm. When the Frames/Period setting is changed, yes jackd
is notified. But the new setting isn't stored in the qjackctlSetup
object that both forms share a reference to. As well as the change not
being written to disk, the main form is unaware of the fact that a
change has even happened. So press stop and play on the main form and
the new instance of jackd uses the old, incorrect values. The patch I've
written corrects that issue. It doesn't force an additional, unnecessary
restart on the jack server.
Likewise, when cancel is hit on the form, the old (and correct) values
stored in m_pSetup aren't written back to the user interface. (Because
the existing instance of the form is used, and it's not reinitialised.)
Cheers,
Aaron
On 27/3/20 08:57, Debian Bug Tracking System wrote:
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
If you wish to submit further information on this problem, please
send it to 954...@bugs.debian.org.
Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.
