|
|
|
|
|
1.PNG (39,556 bytes) |
|
|
2.PNG (52,011 bytes) |
|
|
So it did not work in Lazarus 1.4.4 and works in Lazarus 1.6.0? What is the point of this bug report then? Note that Lazarus 1.4 series is not supported anymore. |
|
|
Lazarus 1.6 will not display generated by the Report Lazarus 1.4 |
|
|
Updated summary. @wsoft-hu: always fill in the summary of your report please! |
|
|
Well, sadly I have to say, we did it again... While LazReport was at binary format version=28 (or 27 don't know for sure) was active, a feature "ParagraphGap" was added without first increasing version to 29, because of that, some reports with version=28 (produced with Lazarus 1.4.4 for example) do not add or check for ParagraphGap but some other version=28 reports where saved with check for ParagraphGap. The result is that there is no way to distinguish which version=28 binary reports need to consume or ignore the ParagraphGap feature. In the same way when v25 reports were broken, I solved the problem by adding a global variable LRE_OLDV28_FRF_READ which if set to true will allow LazReport to read those original version=28 reports, default is false. Additionally instead of showing a Access Violation dialog I added a message explaining the problem. Also by default, saving a prepared report will bring it's binary structure version up to the current version. Please test. |
- Anonymous
