Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JasperPHP + iReport 5.6 Error #44

Open
onoboaits opened this issue Jul 29, 2020 · 3 comments
Open

JasperPHP + iReport 5.6 Error #44

onoboaits opened this issue Jul 29, 2020 · 3 comments

Comments

@onoboaits
Copy link

Grettings,

I have a iReport file with 3 pages wich contains some fields and controls but when i test the report in pdf generation this shows the fields with another position, i make a video for a better explain, this is the link https://youtu.be/yKdgeFYh7dI.

I hope, you can help me because i'm workin in this project some weeks and i need finish this work.

Thakns,

Omar

@onoboaits
Copy link
Author

Grettings,

I can fix the problem about the control position, when you design the report, must considerate the follows advaices:

1.- Don't put a control over another control. the superposition generate error, don't display in pdf.
2.- Don't use static text and rectangle, this constrols no shows in pdf.
Use TextField and lines. Rectangle only shows without borders.

Now i get another error, my report have 3 pages, i use 3 details section, in the preview jasperReport i show the controls of the second page, but when i generate pdf with JasperPHP the controls of the second page are mounted in the first page. The process only shows one page.

Plase your help about this.

Best regards,

Omar Noboa

@Rctnet
Copy link
Member

Rctnet commented Aug 5, 2020

Helo, @onoboaits , i consider about our coment.
about your problem with multiple details, review split type property on those bands, will be stretch or prevent.

thank´s for your patience

@onoboaits
Copy link
Author

Thanks for your answer, effectively there are the error in the second detail, have a nice day.

Best regards,

Omar Noboa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants