Topic: Report Selector Orientation (Portrait, Landscape) implmented in FA 2.4

The Report Selector Orientation (Portrait, Landscape) is now implemented in Report Centre for all Reports in FA Release 2.4 (unstable).

If Landscape is selected, the column offsets are recalculated with the new page width.

In config.default.config.php (config.php) a flag for this orientation is added

    /* default print orientation. 0 = Portrait, 1 = Landscape */
    $def_print_orientation = 0;

/Joe

Re: Report Selector Orientation (Portrait, Landscape) implmented in FA 2.4

Cool!  That will be useful for some of the reports that have lots of columns (e.g. Annual Expense Breakdown, etc.).  I look forward to checking it out when v2.4 is released.

Btw, just out of curiosity...  when is v2.4 scheduled to be released?

Thanks!

Regards,

Chris

Re: Report Selector Orientation (Portrait, Landscape) implmented in FA 2.4

I guess we are close, but I am not the only one to decide this. A realistic guess would be one or two months.

/Joe

Re: Report Selector Orientation (Portrait, Landscape) implmented in FA 2.4

Sounds like it's going to have some great new features!  I'm looking forward to it coming out!

Thanks for the info...

Regards,

Chris

Re: Report Selector Orientation (Portrait, Landscape) implmented in FA 2.4

Any chance of porting the reports to the stable branch or are they directly usable with the stable branch?

Re: Report Selector Orientation (Portrait, Landscape) implmented in FA 2.4

No, they require some smaller changes in recalculating column offsets.
Due to the huge amount of file changes, I have decided to let it go into release 2.4.

Just another reason to upgrade, when we are through the testing period after release of 2.4 RC.
I would guess that this release is going to be in a month or two.

Joe

Re: Report Selector Orientation (Portrait, Landscape) implmented in FA 2.4

Then a synch of essential changes from 2.3 into 2.4 is overdue.

Re: Report Selector Orientation (Portrait, Landscape) implmented in FA 2.4

Hope the recent sync of v2.3.21 to v2.4 unstable does this.