[ Show ]
Support VoyForums
[ Shrink ]
VoyForums Announcement: Programming and providing support for this service has been a labor of love since 1997. We are one of the few services online who values our users' privacy, and have never sold your information. We have even fought hard to defend your privacy in legal cases; however, we've done it with almost no financial support -- paying out of pocket to continue providing the service. Due to the issues imposed on us by advertisers, we also stopped hosting most ads on the forums many years ago. We hope you appreciate our efforts.

Show your support by donating any amount. (Note: We are still technically a for-profit company, so your contribution is not tax-deductible.) PayPal Acct: Feedback:

Donate to VoyForums (PayPal):

Login ] [ Contact Forum Admin ] [ Main index ] [ Post a new message ] [ Search | Check update time | Archives: 12345[6]78910 ]

[ Next Thread | Previous Thread | Next Message | Previous Message ]

Date Posted: 08:50:44 02/13/02 Wed
Author: glup
Subject: Re: Fax TIFF in Fine Mode
In reply to: Michel 's message, "Re: Fax TIFF in Fine Mode" on 20:00:35 02/11/02 Mon

>>2. Everytime the TDibGraphic has to draw itself into a
>>Cavas where the aspect ratio is different than the the
>>own, it changes the aspect ratio "on-the-fly" with
>>StretchBlt resp. StretchDIBits.

>Solution 2 would compensate without you knowing, so if
>you do a SaveToStream/File the dimensions of you image
>would have changed.

Why does SaveToStream/File draw the image into a new canvas that does have another aspect ratio than the original?

>Sometimes a user wants to work in pixels, but when
>sending output to a printer, the resolution is
>important (where Envision does not handle different
>x/y resolutions).

I understand that Delphi likes working with pixels, so the "rest" should support this. But why should the "user" (here developer) care when using a device independent graphic about the device aspect ratio and the device resolution? This I see as a nice implizit task for the component.

>Solution 1 would not interfere with any existing code
>which I think is important. The TAspectRatioTransform
>is actually just a TResizeTransform with the proper

I'm using this solution currently.

>Does that sound good?

As I said I work with this, but think that some work could be done by the component implicit.

[ Next Thread | Previous Thread | Next Message | Previous Message ]


[ Contact Forum Admin ]

Forum timezone: GMT-5
VF Version: 3.00b, ConfDB:
Before posting please read our privacy policy.
VoyForums(tm) is a Free Service from Voyager Info-Systems.
Copyright © 1998-2019 Voyager Info-Systems. All Rights Reserved.