Currently, this property gets the job done:
<property name="net.sf.jasperreports.export.xls.font.size.fix.enabled" value="false"/>
But this is equivalent to an aircraft setting auto pilot on as follows:
<property name="boing.flight.deck.auto.pilot.enabled" value="false"/>
This is the opposite of what is desired.
The FAA would never authorize such nonsense, leading to crashes.
As this property is in legacy code, it can't be corrected directly.
The suggestion is to create yet another property:
<property name="net.sf.jasperreports.export.xls.font.size.fix.enabled.for.real" value="true"/>
This property would override the prior property and be consistent with the truth.
If Microsoft required this code to enable a button, they would be laughed at.
<Button enable="false">Fire Missiles</Button>
Would Bill Gates approve such a thing?
And ALL new reports should have this line added to code in Source tab.
After all, why should NEW reports with no need for legacy protection start in an error state rather than fixed state?
Thank you so much for your idea. We will consider it as a future requirement.
Attachments Open full size