You have to be careful about the transparency, though. After doing this conversion with transparency, I found that some of our pictures in the picture library (and static pictures on forms) need white in some areas to be meaningful. So we had to carefully look at each one to be sure that transparency conversion didn’t take anything away and redesign the ones that needed white put back in certain areas.
Randy ---------------------------------------------------------------------- Randy Jaynes Senior Programmer and Customer Support http://printpoint.com <http://printpoint.com/> • 845.687.3741 • PrintPoint, Inc • 57 Ludlow Lane • Palisades, NY 10964 Please send all email contacts to [email protected] <mailto:[email protected]> > On Mar 9, 2019, at 9:35 PM, Charles Miller via 4D_Tech <[email protected] > <mailto:[email protected]>> wrote: > > You need to do convert in 32 bit and make sure to take care of transparency > Chuck > > On Sat, Mar 9, 2019 at 2:17 PM Wayne Stewart via 4D_Tech < > [email protected] <mailto:[email protected]>> wrote: > >> Are you running the code in 32 bit mode on a computer with QuickTime >> installed? >> >> On Sat, 9 Mar 2019 at 19:27, David Garrard via 4D_Tech < >> [email protected] <mailto:[email protected]>> >> wrote: >> >>> I have some legacy pictures fields with .PICT pictures in them in my >>> Windows database that I am converting to v17 64 bit. Here is my code to >>> convert the pictures to JPG format. >>> >>> ALL RECORDS([DOCC_Document]) >>> For ($i;1;Records in selection([DOCC_Document])) >>> GOTO SELECTED RECORD([DOCC_Document];$i) >>> GET PICTURE FORMATS([DOCC_Document]Document_Icon;$aTPictureFormats) >>> CONVERT PICTURE([DOCC_Document]Document_Icon;".jpg") >>> SAVE RECORD([DOCC_Document]) >>> End for >>> >>> The documentation suggests that this would convert the pictures in the >>> database to jpg format and they would lose the "ugly big cross on PICT" >>> replacement icon. But I see no changes. >>> >>> I must be doing something fundamentally wrong... Any ideas? >>> >>> David Garrard >>> ********************************************************************** >>> 4D Internet Users Group (4D iNUG) >>> Archive: http://lists.4d.com/archives.html >>> <http://lists.4d.com/archives.html> >>> Options: https://lists.4d.com/mailman/options/4d_tech >>> <https://lists.4d.com/mailman/options/4d_tech> >>> Unsub: mailto:[email protected] >>> <mailto:[email protected]> >>> ********************************************************************** >> >> -- >> >> Regards, >> >> Wayne >> ********************************************************************** >> 4D Internet Users Group (4D iNUG) >> Archive: http://lists.4d.com/archives.html >> <http://lists.4d.com/archives.html> >> Options: https://lists.4d.com/mailman/options/4d_tech >> <https://lists.4d.com/mailman/options/4d_tech> >> Unsub: mailto:[email protected] >> <mailto:[email protected]> >> ********************************************************************** > > -- > ----------------------------------------------------------------------------------------- > Chuck Miller Voice: (617) 739-0306 Fax: (617) 232-1064 > Informed Solutions, Inc. > Brookline, MA 02446 USA Registered 4D Developer > Providers of 4D, Sybase & SQL Server connectivity > http://www.informed-solutions.com > <http://www.informed-solutions.com/> > ----------------------------------------------------------------------------------------- > This message and any attached documents contain information which may be > confidential, subject to privilege or exempt from disclosure under > applicable law. These materials are intended only for the use of the > intended recipient. If you are not the intended recipient of this > transmission, you are hereby notified that any distribution, disclosure, > printing, copying, storage, modification or the taking of any action in > reliance upon this transmission is strictly prohibited. Delivery of this > message to any person other than the intended recipient shall not > compromise or waive such confidentiality, privilege or exemption > from disclosure as to this communication. > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > <http://lists.4d.com/archives.html> > Options: https://lists.4d.com/mailman/options/4d_tech > <https://lists.4d.com/mailman/options/4d_tech> > Unsub: mailto:[email protected] > <mailto:[email protected]> > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
