| Anonymous | Login | Signup for a new account | 2019-02-22 04:39 UTC |  |
| Main | My View | View Issues | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0000939 | Firmware | Decoders | public | 2015-06-14 04:20 | 2015-06-14 04:20 | ||||||
| Reporter | Fred | ||||||||||
| Assigned To | Fred | ||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||
| Status | assigned | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 0.2.0-SNAPSHOT | ||||||||||
| Target Version | 0.2.0 | Fixed in Version | |||||||||
| Summary | 0000939: State flags and variables not separated correctly | ||||||||||
| Description | Some assumptions are made in some decoders about the validity of various variables which could result in desync due to using data that is zero when it's assumed to be something else. Specifically, at least, the last period flag is used to denote the lastTicksPerDegree to be valid. This is an optimisation, actually, as sometimes it's possible to calculate the last ticks value after-the-fact. And frequently this field is not valid when it's being set in the block at the end of most/some decoders. | ||||||||||
| Tags | No tags attached. | ||||||||||
| FirmwareVersion | 6dd79320ca05d0a764cba2f6f17c241b6779fec9 | ||||||||||
| Issue Type | Improvement | ||||||||||
| Risk of Breakage | medium | ||||||||||
| Attached Files | |||||||||||
 Relationships |
 Notes |
|
| There are no notes attached to this issue. |
|
Notes |
| Copyright © 2000 - 2011 MantisBT Group |
 |