LXEdge 1.2.1.30 Full Release Notes
Question Last Updated on: 5/19/2025
Released: May 19, 2025
Warning- Polygraph Files (PFs) collected in LXEdge 1.2 and later will NOT open on older versions of LXEdge. PFs collected on earlier versions of LXEdge will be able to be opened and reviewed in LXEdge 1.2 and later.
Major Updates
Minor Updates
- In Scoresheet “Scoring Result” dropdown, changed “Reactions” to “Response”.
- Added “Scoring Result” and “Countermeasures” to the Scoresheet PDF printout.
- Disabled adding notes during question onset. Adding notes at this time could prevent Onset button from being re-enabled or cause the Onset shading for the question to persist through the duration of the chart while running.
- Enable stripping by default when adding new fields to Personal History or Series templates.
Bug Fixes
- When quickly navigating in PF, last change to Personal History or Series information could be lost. Would sometimes lead to unexpected messages related to incomplete Personal History when starting chart.
- When reviewing a chart with more than 7 minutes and 9 seconds of data, sensor data after this time would not be displayed. The data are still present in existing charts and will appear when opening in this release.
- When reviewing a PF created on PC set to a different time zone, no values would appear for the RLE and PPG PA tools.
- A chart would fail to appear when navigating back to the chart after navigating elsewhere in the PF and then back to the same chart.
- On some systems, adding notes to a chart after confirming “end chart” would occasionally cause all sensor data to be lost.
- Issues when language set to Spanish
- Examinee names did not appear in the PF grid on Home Page
- NCCA import failed
- In rare cases, archiving a PF that had been converted from 1.1 to 1.2 would cause LXEdge to shut down without warning.
- In rare cases, when combining charts created in earlier versions of LXEdge some sensor data from one chart would push back the data from the next chart.
- Running a chart without traces appearing would cause a crash and subsequent inability to load this chart.
- PF conversion would fail for a PF containing a completely empty chart.
