TTL signal release read as response by SuperLab; "ignore key release" is on

We have a TTL signal being sent from a simulation program in one computer to the receiving computer that has SuperLab running.
SuperLab is reading the release of the pulse signal as a response even though “ignore key release” has been checked; this throws off the sequence of events and the corresponding responses. (The Data to Save tab does have “record whether key was pressed or released” checked)

How can I keep SuperLab from reading the release of the TTL signal as a response?


I’ve opened a bug report in our internal case tracking system regarding this issue.