Lisa,

I get the impression that you are in narrow contact with the vfpt. For example, you write about a 'tremendous amount of effort' that was required to (my words/interpretation) replace the old preview routine. In my opinion that effort was not really successful, at least in some aspects. Two arguments regarding the design of the zoomlevel functionality:

- The 'fit to window' zoomlevel should never have been given the number 10. Instead, a negative number would have been better.
- Instead of 1-9, values 10-500 (for the time being) is better. So, a percentage. If there's a practical problem with certain percentages/values, the internal routine can easily round up or down, again, for the time being.

Also, there should be internal support for ctrl+scrollwheel, rather than let 'us' manually program it.

The vfpt should pay a visit to the wordt. Can't be too far away on the campus.


>---
>
>What is interesting is that the ZoomLevel = 10 compute a percent to fit the window. So it really shouldn't be that difficult for the VFPT to let us access any zoom level we want.
>
>----
>
>VFPT *has* let you do what you want to do. What you're saying here is that the shipping Xbase preview component (REPORTPREVIEW.APP) does not happen to provide this ability.
>
>
>----
>
>Let's hope they will change that for the final release.
>
>----
>
>It's certainly possible, but not likely.
>
>A tremendous amount of effort, both native and Xbase, was required in this development cycle to break out the preview and other rendering elements from the engine and to provide appropriate Xbase ways for you to do this type of thing. And, as I've stated on other threads, to make all the aspects of the reporting process that were broken out from the engine follow the same OOP paradigm you use in other parts of VFP.
>
>This was the goal, and this goal has been accomplished.
>
>IOW, the point of the shipping _REPORTPREVIEW was to provide access to these features, not be "THE VFP preview".
>
>Somebody else asked me for examples in this d/l. _REPORTPREVIEW and the listener classes you'll find in FFC\_reportlistener.vcx *are* actually examples of the kinds of things you would like to do and they show you how much is possible.
>
>They are very sophisticated examples, but even so you are not limited by them.
>
>>L<