[ 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: 1234[5]678910 ]

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

Date Posted: 07:26:38 10/17/02 Thu
Author: Michel
Subject: Re: Regarding an earlier reply from you
In reply to: Dave Bracken 's message, "Regarding an earlier reply from you" on 13:30:02 10/16/02 Wed

Hi Dave,

>1. I am not scanning my tiffs multipage, they are all
>single page tiffs. So if i create the ttiffgraphic
>outside the scan call, will it just keep growing in
>memory while my software is pulling in images and
>saving them out as singlepage tiffs?

It may only make a small difference in speed. There should not be any memory leak, as long as you create/destroy only once. Assign a new image to an TTiffGraphic already created is fine; the previous image is released.

>2. The above is why i am creating it and destroying it
>after each image is pulled in and then saved out.
>Memory usage is a big problem here.

The only drawback if it is created "outside" the scan, is that you alway have one image loaded between scans. You could also use TTiffGraphic.Clear after saving your image.

>4. This is the reason why i have it setup right now to
>use the imageformattransform to set the image format
>to ifBlackWhite in the beforesave event of the
>imagescrollbox control. Is this necessary? The image
>files seem to tend to be smaller with this code in
>place, but i wonder if it is at the cost of memory. Is
>there any way to specify that all images are to be
>saved in the ifBlackWhite format, so i do not have to
>use a transform before saving each individual image? I
>believe that might help on the memory issues as well.
>And along the same note, is there a way to also
>specify the compression for all files, to avoid
>setting the compression for every file in the
>beforesave event of the imagescrollbox component?

If your ISIS scanning returns your images in black and white, there should be no need to do an image format conversion. After assigning the TTiffGraphic the image received from the scanner, check the ImageFormat to see if the image format is black and white.

Best regards,


>Hello Michel,
>In an earlier post regarding memory slowdowns of my
>software you suggested making the call to create a
>TTiffGraphic outside of the scan call, so as to avoid
>the create and destroy every time. That got me to
>3. I also thought i should mention this time, that i
>am not using Envision to scan. I am using the Pegasus
>ISIS scanning control to aquire my images.
>Thanks in advance for any help you can give,

[ 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.