On 05/07/13 23:25, Yonit Halperin wrote:
rhbz#968050
In contrast to Microsoft Msdn documentation, the iUniq of a SURFOBJ doesn't
always change when the surface changes. However, it seems that the
iUniq of the associated color_trans (XLATEOBJ) changes, while its
flXlate=XO_TRIVIAL. Since we tried
On 07/05/2013 06:25 PM, Yonit Halperin wrote:
rhbz#968050
In contrast to Microsoft Msdn documentation, the iUniq of a SURFOBJ doesn't
always change when the surface changes. However, it seems that the
iUniq of the associated color_trans (XLATEOBJ) changes, while its
flXlate=XO_TRIVIAL. Since we
On Fri, 2013-07-05 at 11:25 -0400, Yonit Halperin wrote:
> rhbz#968050
Looks great to me, ACK.
>
> In contrast to Microsoft Msdn documentation, the iUniq of a SURFOBJ doesn't
> always change when the surface changes. However, it seems that the
> iUniq of the associated color_trans (XLATEOBJ) cha
rhbz#968050
In contrast to Microsoft Msdn documentation, the iUniq of a SURFOBJ doesn't
always change when the surface changes. However, it seems that the
iUniq of the associated color_trans (XLATEOBJ) changes, while its
flXlate=XO_TRIVIAL. Since we tried to retrieve the alpha bitmap key
only by t