 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Randy Guest
|
Posted: Fri Feb 24, 2006 4:05 pm Post subject: Workaround TMetafile |
|
|
I'm having a problem with a *.WMF graphic not rendering the same under
BCB6 as it did under BCB3. I've spotted one big difference in vcl source
graphics.pas in the ReadWMFStream procedure. The newer version calls the
win api SetWinMetaFileBits with the bottom right coordinates inserted
into the emf header....BCB3 didn't do that.
I'm looking for the best way to work around this addition and render it
the old way, but I'm not sure of the best way to suppress borlands
impementation. Is it possible to derive a component from TMetaFile and
implement my own ReadWMFStream method? Or would rendering it into a
(bitmap?, memory array?, whatever) using the windows API be a better
approach?
I fumbled around a bit with deriving a component, but when I try to
manipulate existing properties like FImage I get accessibility errors.
Thanks for any help you can offer |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|