wow, i did not expect a response to every point
I would need some context to make any sense of that comment.
on some measurements i get a "very low signal level on measured" pop-up
which contradicts itself by stating that the input is just -6.4 dBFS, but should be above -35 dBFS
(as far as i understand it, -6.4dBFS is above -35dBFS)
a hopefully clarifying screenshot
on some occasions i have gotten 2 different pop-ups stating essentially the same thing on a single measurement
I don't understand that comment.
filling in a note and checking the "keep for next measurement" box saves the note for the next measurements
on a subsequent measurement, changing the text of the note, uses that new text for the subsequent measurement
on a third measurement, the first note is used (unless you uncheck "keep for next measurement" (this wipes the note) re-enter the note, and check the "keep" box again)
checking the box acts as a button that saves the note as the default text for subsequent measurements, you have to do it again if you want to changed the saved note
this means you can check the box on an empty note, fill in the note, and the next measurement will have a blank note
where the expected behaviour is that the note that is seen on this measurement will be seen on the next measurement
and when you fill in a note, then disable the "keep" functionality, you lose the note
last clicked measurement name stays selection highlighted
this isn't about trace views, i suspect it's also standard java text box behaviour
i mean that "test" here stays highlighted despite me having my cursor in the next test's note
with this highlighting i expect a backspace to erase test 4's name field, but it'll erase in test 5's note
on an out of memory pop-up, i get a button "Exit REW", it does not exit REW
i'll make a separate topic for my questions tomorrow, but thanks for answering most of them already!
Thread starter
John Mulcahy
