Anonymous | Login | Signup for a new account | 2019-02-19 19:10 CET |
Main | My View | View Issues | Change Log | Roadmap | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0006564 | [JEDI VCL] 00 JVCL Components | major | always | 2017-04-09 11:42 | 2018-07-26 11:07 | |||||||
Reporter | sender | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | normal | Resolution | open | |||||||||
Status | acknowledged | Product Version | Daily / GIT | |||||||||
Summary | 0006564: JvDBImage shows "Bitmap image is not valid" to some kind of jpeg image. | |||||||||||
Description | Some kind of jpeg image does not has the "JFIF" or "Exif" signature at stream offset 6 as procedure GraphicSignaturesNeeded expected. | |||||||||||
Additional Information |
Simple workaround is to add: RegisterGraphicSignature([$FF, $D8], 0 , TJPEGImage); to procedure GraphicSignaturesNeeded; But I think we should add file ending signature examination since a valid jpeg file is always ended with 0xFF, 0xD9. (According to https://en.wikipedia.org/wiki/JPEG) [^] |
|||||||||||
Tags | No tags attached. | |||||||||||
Attached Files |
![]() ![]() ![]() |
|||||||||||
|
Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group |