Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Funky Preview Window
Message
De
19/11/2008 05:10:37
 
 
À
18/11/2008 22:19:37
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire de rapports & Rapports
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows XP SP2
Divers
Thread ID:
01362540
Message ID:
01362773
Vues:
14
As I'm still working through this, let me ask a couple of additional questions that are
probably related to the compressed preview pages:

(1) In passing the tnLeft parameter to Render, I assume I'm passing FRUs. For an 8-1/2-in.-wide page, does that
imply 0.000 corresponds to the left edge and 85000.000 corresponds to the right edge? Or do I
have to somehow figure in printer margin settings, etc., in setting/validating tnLeft? Or do I have to have tnLeft >= .001 to
be sure I'm within the physical page? (It appears as though, if tnLeft is less than the printer's left margin, the
rendering is truncated accordingly.)

(2) A head-scratcher I"m seeing with a simple test report form limited to two listener-processed report objects on the
same detail line. My listener (patterned after Doug's SFReportListener class) has calls to BeforeRender and AfterRender
in the Render method, which bracket the actual :: Render+NODEFAULT call that uses nAdjustLeft + tnLeft for the Left
parameter. BeforeRender is not being called for the first report object, but I do end up with
a rendered object. BeforeRender is being called for the second object, as expected. I can only figure that the'
first object's BeforeRender is being skipped because of an illegal parameter setting. Is there another possible
cause that I should be considering?

-mark

*********

>>Doug Hennig wrote:
>>In addition to the other suggestions, I've also seen compressed pages when an object is positioned or sized such that it's past the left or right edges of the page.

>>I write:
>Thank you all for the feedback. This listener does both resize and reposition report objects on the fly
>-- so, although I'm still looking for it, I think that this is the most likely culprit.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform