After changing a thermal application’s image mode, check the saved and reopened result rather than assuming it contains the same information as the previous mode. The live screen and the file delivered to a report are separate checkpoints.
Build a mode-to-file check
| Checkpoint | What to record |
|---|---|
| Before capture | Exact mode name and required output information |
| Save action | Which documented command creates the file |
| Gallery review | What view and information are available when reopened |
| Export | Which format and options are selected |
| Receiving application | What the reviewer can actually open and inspect |
For its Ex Pro series, FLIR documents different saved information by image mode. That is a model-specific example of why file behavior needs confirmation. It does not establish the same modes, file structure or editing capabilities in a Phonemax app.
Assess the delivered version
On an authorized sample, use a harmless scene and a test job. Check each mode required by the workflow and label its output. Include the app version in the acceptance record so a later software change can be reviewed without assuming the old result still applies.
If the live presentation appears correct but the export lacks required information, record the gap. Do not describe a mode as accepted merely because the file opens or looks similar. Ask the supplier and report owner to resolve the requirement before deployment.
The P20 Pro listing confirms integrated thermal imaging but does not specify this mode-to-file behavior. No mode-switching or export test is reported here. Use the original-output checklist and ask Phonemax for app-specific instructions.
Оставить комментарий
Все комментарии перед публикацией проверяются.
Этот веб-сайт защищается hCaptcha. Применяются Политика конфиденциальности и Условия использования hCaptcha.