[AD] [alleg:bugs] #349 Projection transform should be a bitmap local sta

I still think it's a good idea to do. We have since removed the problematic call to al_set_target_bitmap in the ttf addon (although I see a new one was added in the font addon in create_builtin_font_sheet).

The reason to keep it separate from the normal transformation is for convenience... it'd be annoying to have to reinstate the ortho transform every time you want to make a new transformation with the A5.0 semantics.

[bugs:#349] Projection transform should be a bitmap local state

Status: open
Labels: Core Library
Created: Sun Feb 05, 2012 05:16 AM UTC by SiegeLord
Last Updated: Thu Dec 05, 2013 12:36 PM UTC
Owner: nobody

Right now in 5.1 the projection transform is a display local state. This leads to unexpected behaviour when dealing with al_set_target_bitmap which modifies it. This is doubly an issue in calls where al_set_target_bitmap is used internally, such as in al_draw_text (in ttf addon). You might call al_draw_text and then find that your projection matrix has been irrevocably lost without warning.

I propose that the projection transform should be bitmap local, just like the standard transform is. al_set_target_bitmap will then simply set the transformation stored inside the bitmap, like it does right now with the standard transform. The bitmap transform will be initialized using al_ortho_transform upon bitmap creation.

Sent from sourceforge.net because alleg-developers@xxxxxxxxxx is subscribed to https://sourceforge.net/p/alleg/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alleg/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.