iReports 1.3.3 bug

[jmbaker]

Hello,

 

I've found a bug with iReports 1.3.3 (and I noticed it in version 1.3.2, too). The "Ignore pagination" tick box doesn't get persisted correctly when the report is saved. In fact, it actually writes the wrong value to the XML. If you tick the box and press save, the 'isFloatColumnFooter' set to true. If I untick "Ignore pagination" then the isFloatColumnFooter flag is removed from the XML.

 

I bet it's a 2 minute fix but worth resolving!

 

It would be lovely to set this property at runtime but that's a jasper reports change request, I guess!

 

 

John

[Giulio Toffoli]

Hi John. Thanks for your post.

 

It is not a bug.

 

There are two ways to set "ignore pagination". The first one is done at design time (Report properties -> ignore pagination). And it is correctly persisted in the jrxml.

 

The second one is done at run time, adding the special parameter "IS_IGNORE_PAGINATION" to your parameters map, with value TRUE. This can be performed in iReport checking the menu item Build -> Ignore pagination.

This menu selection is not persisted and is not written in the jrxml.

 

Example of using ignore pagination at run time:

 

Code:

myHashMap.put("IS_IGNORE_PAGINATION",  Boolean.TRUE );

 

Hope it helps

 

Giulio

[emi030480]

Sorry to say, but John is right.

 

Under iReport 1.3.2, if you check "Ignore Pagination" the property isFloatColumnFooter, while ignoringParameter is created only when the "isFloatColumnFooter" under iReport gets checked.

 

It is just an iReport issue, but still annoying.

 

Emiliano