>
> >> Well, simply follow the documentation, i.e., set `pitch' to
> >>
> >> w + 7) / 8) + 1) / 2) * 2
> >>
> >> (but with some better C code :-) and use this value for creating
> >> the bitmap.
> >
> > Ok, I did change the value of pitch (6) and tried to draw `a', it is
> > giving a wrong
>> Well, simply follow the documentation, i.e., set `pitch' to
>>
>> w + 7) / 8) + 1) / 2) * 2
>>
>> (but with some better C code :-) and use this value for creating
>> the bitmap.
>
> Ok, I did change the value of pitch (6) and tried to draw `a', it is
> giving a wrong glyph, then I
>
> > [...] I still have a doubt about pitch value, currently it is set to
> > (w+7) / 8 (w: glyph width ). The documentation says `For the B/W
> > rasterizer, ‘pitch’ is always an even number.' but this is also
> > returning odd values. Is there any problem in this?
>
> Well, simply follow the
> [...] I still have a doubt about pitch value, currently it is set to
> (w+7) / 8 (w: glyph width ). The documentation says `For the B/W
> rasterizer, ‘pitch’ is always an even number.' but this is also
> returning odd values. Is there any problem in this?
Well, simply follow the
>
> > I have removed all the memory leak errors in the gf driver. But now
> > when I run `ftview', it is still not loading the glyphs.
>
> Before delving into this issue: Does your `ftexample' now work
> correctly?
>
Yes, I can't say for sure as I didn't draw every glyph by the gdb
method (It
> I have removed all the memory leak errors in the gf driver. But now
> when I run `ftview', it is still not loading the glyphs.
Before delving into this issue: Does your `ftexample' now work
correctly?
> ==11084== Invalid read of size 1
> ==11084==at 0x10E758: my_face_requester
Hi all,
I have removed all the memory leak errors in the gf
driver. But now when I run `ftview', it is still not loading
the glyphs. I did `valgrind ftview 20 /home/parth/cmr10
.600gf' and it is showing invalid reads in the `FTC...'
functions.
I am not able to understand the problem. Please help.
