TppRegion.Visible + Stretch works different on Rb11

rbuser

Hi,


Upgrading from 7.04 to 11.05 (Delphi 2006)


We have some layouts which behave different in RbPro 11.05

In a summary band of a subreport i have the following

DbText DbText
+-Region------------------------+
| DbText DbText |
+----------------------------------+
====== ======


Printing of the region is optional (by setting Region.Visible). I want the
lines the move up if the region is not printed. So Region.Stretch is True
and the summary band is set to dynamic height. The lines had ShiftWithParent
set to True, this correctly converted to Anchors = [atLeft, atBottom]
This worked OK in RbPro 7, but in RbPro 11 the height of the summary band is
not adjusted if the region is not visible.

How can I get this working again?

Thanks,

Max Paay
Quadrant Software bv.
The Netherlands.








__________ Information from ESET NOD32 Antivirus, version of virus signature database 4373 (20090827) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

nicocizik

Hi Max,

Thanks for pointing this out. I was able to recreate the behavior you
mention and we are in the process of researching a solution. I will post
any updates to this thread. Thanks for your patience.

--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com

nicocizik

Hi Max,

Upon further research, we were unable to provide this functionality without
damaging other reports. If you take a look at the ppCtrls.pas file inside
the TppCustomComponent.CalcPrintPosition routine, you will see some
commented out code near the bottom. Uncommenting this code along with the
few other lines commented out above will get you the closest to the effect
you are after.

--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com

rbuser

Hi Nico,

Thanks,

Tried that and it works OK. But i also had to change

{check whether space used > 0 or we're out of space}
if (lMaxStretchable <> nil) and ((lMaxStretchable.SpaceUsed > 0) or
(lMaxStretchable.OutOfSpace)) then

to
if (lMaxStretchable <> nil) then

so actualy this proc is now back to RbPro 7.


So our "damaged" reports are OK now. But can you explain why it was
changed? And what are the problems i can encounter with other reports now?



Regards,


Max Paay
Quadrant Software bv.
The Netherlands.