• Bugfix: COMPLEMENT draw mode with antialiased fonts no more leaves trashes when done twice at the same place. It allows for using COMPLEMENT mode as an easy way to make moving text brushes. Works as well combined with INVERSVID and transparency. Bug reported by Marcin Kwiatkowski.
  
• Bugfix: Missing render mode initialization in TT_TextExtent(). Glyph bitmaps were not cached if TT_TextExtent() was called before any TT_Text() or TT_TextLegnth() on this rastport. It caused significant slowdown of TT_TextExtent(). Bug reported by Darius Brewka.
  
• Bugfix: If temporary RastPort was used with NULL BitMap, this NULL pointer was passed to GetCyberMapAttr(). It might lead to Enforcer read hits. Now if RastPort's BitMap is NULL, antialiased render mode is assumed and GetCyberMapAttr() is not called.
  
• Fixed "DetachedRastPort" example code to work on RGB screens. Color 1 in colormap of a window opened on Workbench is usually black. Rendering black text on black (BMF_CLEAR) bitmap usually results just in black window contents... Changed text color to 2 (usually white). Why it worked on planar or LUT bitmaps? Clearing such bitmap does not clear to black but to background color (gray on most setups).

Im' happy to see that such good quality libs are still in development and are continuously improved!

Now the 'Must-to-be-asked' question: Any planning for a native AOne-OS4 port?

_________________
God created Paula so that Allister Brimble and Dave Whittaker could do music

Check my Amiga gameplays (ITA)!

No need, OS4 has FT2Engine built in.

Forgot it!

Well, good thing, then!

_________________
God created Paula so that Allister Brimble and Dave Whittaker could do music

Check my Amiga gameplays (ITA)!

How do the two rendering engines compare? (in terms of speed, output quality, supported font types, etc)

Quote:

No need, OS4 has FT2Engine built in.

Just as MorphOS. Yet, a native version is still faster than an emulated one, so a native one would be nice.

Huh ? You said that MorphOS has a native version so why do you say "a native one would be nice" ???

Anyway, it's good to see that now we can use whatever font (ttf, pfb..) !

_________________
Philippe 'Elwood' Ferrucci
Sam460 1.10 Ghz
AmigaOS 4 betatester
Amiga Translator Organisation

Quote:

Poster: elwood Date: 6-May-2004 9:33:43 Huh ? You said that MorphOS has a native version so why do you say "a native one would be nice" ??? Anyway, it's good to see that now we can use whatever font (ttf, pfb..) !

I believe he means a native OS4 version would be nice rather than using the 68K version. However since FT2 is built into OS4, it will be native anyway, just as he implied it already was with MorphOS.

_________________
Test sig

TT is SLOW and boring but nice to look at..

its fun to use on a PPC os but not on an 68k one....thats my op anyway.

tony

_________________
See my blog and collection website! . https://www.blog.amigaguru.com

@_Steve_

Quote:

...just as he implied it already was with MorphOS.

He just said it's built-in (not necessarily native). At least that's how I read it.

Quote:

I believe he means a native OS4 version would be nice rather than using the 68K version. However since FT2 is built into OS4, it will be native anyway, just as he implied it already was with MorphOS.

But if the application is using ttengine.library? 68k apps are not necessarily OS4 aware and have no idea how to use built-in FT2Engine.

Quote:

itix: But if the application is using ttengine.library? 68k apps are not necessarily OS4 aware and have no idea how to use built-in FT2Engine.

Good point. In that regard, a native port of the ttengine.library would be useful. However in principal, the changes needed to recompile the 68k version for OS4 should be minimal, so creating an OS4 native port ought not to be very hard at all.

But again, this would only rely on programs using the ttengine.library explicity. If the OS has built in functionality for TT fonts, but still the way you called it would have been the same as opening a font under OS3.x, then in theory at least you would have no need for a separate library for handling TT fonts as your old program would do it transparently via the new font libraries.

_________________
Test sig