Page 2 of 2

Re: OpenScreen & OpenScreenTags ... Why do they don't work ?

PostPosted: Sat Dec 15, 2018 10:36 pm
by AmiDARK
thomasrapp :
Once again, thanks for your knowledge ...
What I found odd, is that this information is available nowhere in the autodoc concerning graphics library and BestModeID, and Intuition OpenScreen, etc...

EDIT : Tested by replacing 32 with 24 inside the OpenScreen method (to keep 32 in the displayCore structure for my needs.
It works perfectly now.
But how can I be sure that detph will really be 24 + 8 alpha bits instead of 24 without alpha ?

Regards,

Re: OpenScreen & OpenScreenTags ... Why do they don't work ?

PostPosted: Sun Dec 16, 2018 4:40 am
by broadblues
But how can I be sure that detph will really be 24 + 8 alpha bits instead of 24 without alpha ?


There are no 24 bit without alpha modes.

Re: OpenScreen & OpenScreenTags ... Why do they don't work ?

PostPosted: Sun Dec 16, 2018 6:19 pm
by broadblues
Just as a further thought.

If you want bitmaps with alpha channels for your applications usage, you do not need to have a screen with 32bit pixels. You merely want to allocate bitmaps with the correct format ( PIXF_A8R8G8B8 for example) do your alpha based rendering, then blit the contents of your temp bitmap into the windows rastport. Whilst at first glance it may seem more efficient if the window has the 32bit format too, as the alpha part is not used (composited windows with alpha maps have a seperate alpha clip), the loss is not a significant as you might think, especially if you do a fair ammount of rendering before blitting the result inot the window.

This approach enables your app to be run windowed on a 16bit workbench screen on lower end hardware. (Sam440 EP for example!).

Re: OpenScreen & OpenScreenTags ... Why do they don't work ?

PostPosted: Mon Dec 17, 2018 10:55 pm
by AmiDARK
broadblues : Thank you for your answer, but I'm not sure to really understand what you explained.