@Vanhapolle

Unless you really need low level functions the best thing to do is to stick to graphics.library functions. This simplifies your code and works from OS3 up and in the least OS4.0. The graphics.library can work with RTG and BOOPSI/Datatypes can be used to load images or other routines.

@mailman2

Quote:

x86 AROS is not Amiga OS compatible

How so? The API is compatible with AmigaOS 3.1.

if i stick graphics.library how i can use it blit truecolor chunky pixelarrays? and draw other things in truecolor ? and i mean OS4.1. i think i have some example using truecolor in MOS.
ps. 3.0 support is still thing what i bet needs some changes... at least 4.0 changes how reaction works etc...

@Vanhapolle

i found such source is very old but anyway. and dont tell how truecolour bitmaps are handled with graphics.library in MOS? and i this example is MOS not AOS4.1.

@Vanhapolle

Maybe some example could be found here :
http://os4coding.net/forums/graphics

_________________
A1200PPC / Sam440ep / Sam460ex / X1000 / X5000 OS4.1

@Vanhapolle

Old graphics.library calls (even on OS3) work just fine with true colour bitmaps. You just cant manipulate bitmaps directly because there is no way to lock down bitmaps and get pointer to raw data.

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook

@Hypex

data in Amiga OS 3.x are big endian.

No big endian means x86 AROS API is NOT compatible with AmigaOS 3.1.

@Vanhapolle

Quote:

if i stick graphics.library how i can use it blit truecolor chunky pixelarrays? and draw other things in truecolor ? and i mean OS4.1.

Historically graphics.library was just planar graphics, picasso96 was add-on that provided true color support, but things are changing more and more of library functions are being moved/copied from picasso96 into graphics.library

I'm not sure what you have in your current SDK or not, right now I think you should stick to picasso96.library at least until AmigaOS4.1 final and updated SDK.

Quote:

ps. 3.0 support is still thing what i bet needs some changes... at least 4.0 changes how reaction works etc.

If you wont to support 3.0 API, you will need to stick to Pens and Colors, most classic Amiga computers only have
AGA/ECS/OCS graphics, so no true color support.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

I loaded latest SDK for both. i mean AmigaOS4.1 and MorphOS3.7. and i must wait AmigaOS4.1 final edition beouse older versions are now unavailable what i heared (and i dont know when i have budget for MOS3.7 registered but i hope in next month). Is hard wait time when i can code but maybe before this i test if i understand few datatype realated things correctly as i allready sayed. palette based graphics for this idea is very complex. i dont simply know good way display truecolour graphics with OCS/ECS/AGA. i mean preview waylike Photogenics dithers all graphics fixed palette whem you use palette based mode.

@Vanhapolle

You need to use OS functions to load and create the BitMaps for you. Intuition and Datatypes is good for this. You could also decode RGB data yourself and pass it to the OS, that should work.

So then you just pass around an RTG BitMap and don't manipulate it directly. It also keeps your code cleaner this way. And avoids partitcular RTG libraries if you really don't need them.

@mailman2

Oh I see. Welll that really would be the ABI rather than the API. But of course x86 has data in different format. Which is funny as I was in a debate recently where it was argued that AmigaOS strutures are not in a big endian format.

But it is source compatible so sources can cross compile. And in portable code this would matter most.