On 6/28/07, Graeme Geldenhuys <[EMAIL PROTECTED]> wrote:
'fpcanvas' references 'fpimage' in the uses clause.
I wanted to make it clear that fpimage doesn't use fpcanvas =) It
seams I didn't express it correctly.
--
Felipe Monteiro de Carvalho
___
fpc
On 28/06/07, Felipe Monteiro de Carvalho
<[EMAIL PROTECTED]> wrote:
On 6/28/07, Graeme Geldenhuys <[EMAIL PROTECTED]> wrote:
> 'fpcanvas' references 'fpimage' in the uses clause.
I wanted to make it clear that fpimage doesn't use fpcanvas =) It
seams I didn't express it correctly.
Ah yes, read
On 28/06/07, Felipe Monteiro de Carvalho
<[EMAIL PROTECTED]> wrote:
They are used together with TFPCustomImage from fpimage.pp file. AFAIK
they are not directly related to TFPCustomCanvas, and you don't need
to use it in order to use those units.
'fpcanvas' references 'fpimage' in the uses cla
On 6/28/07, Graeme Geldenhuys <[EMAIL PROTECTED]> wrote:
In the fcl-image directory is a lot of fpreadXXX and fpwriteXXX units.
Those are low-level image reading and writing (to disk or stream)
routines. They implement the TFPCustomImageReader (or Writer) class.
They are used together with TFP
Hi,
In the fcl-image directory is a lot of fpreadXXX and fpwriteXXX units.
Are those full implementations or are they abstract classes like
TFPCustomFont, TFPCustomCanvas, etc?
In other words, do I still need to implement parts of them to be able
to use them?
Regards,
- Graeme -
___
