Closed GoogleCodeExporter closed 8 years ago
Dieter,
Thanks for the detailed report! The error message is for sure not related to
the roast logging as this is caused by some code that creates/opens the Roast
Properties dialog, but I don't understand what went wrong there. Why the drop
was not recognized remains unclear (those other 5%?). I once also was quite
sure that I pressed the CHARGE button, just to discover at FC START that the
charge was not logged and until I understood the situation, FC was almost over
and I basically missed most events. I recreated them later using the Roast
Properties dialog by making an educated guess.
I conjuncture that in some situations (during communication with the meter?)
some button press events are missed by the program. Or the button was not
pressed properly!?
Hm,
Marko
Original comment by luther.m...@gmail.com
on 27 Jan 2011 at 7:28
It could be that I didn't press the button properly or was moving the mouse
when I did or something. Those 5% like you say! I will keep an extra eye when
pressing the buttons in the future and make sure I take notes if it should
happen again...
Original comment by Diete...@gmail.com
on 28 Jan 2011 at 11:19
Original comment by luther.m...@gmail.com
on 28 Jan 2011 at 7:26
Original issue reported on code.google.com by
Diete...@gmail.com
on 27 Jan 2011 at 6:44Attachments: