Thanks Ross C - I saw that before
The misinterpretation was caused by the fact, that I created a Texture with CreateTexture(x,y,4). So I believed that setting the maskflag would make clear to Blitz that 0,0,0 is the mask (as its stated in the docu) and that its Blitzs turn to do the right thing. Otherwise what is it worth to set a Flag if it has no effect? And the effect appears only when you LoadTexture? If it can do it while Loading why can't it doing it at Creating?
This causes irritation!
Loading a 24Bit colored Texture creates the mask automatic if the Flag is set - Creating a 24Bit colored Texture does it not although the Flag is set.
Maybe or obviously the Flag is only a signal to display it masked... but one still expects that rather the same action causes the same behavior - in this case ORs $ff000000 to a created Texture as its done to a loaded one.
(Edited) And this shows again, that Blitz3D urgently needs a major update - some little things here - some bigger things there!
For instance to solve problems like the one above: Color r,g,b[,a] ClsColor r,g,b[,a] and so on and on and 100s of other things out of the 1000s that have been suggested...
BMax killed B3D ;-(
(Correction) It didn't kill it - it's still alive - but its starving and gets isolated without attention ;-|
The misinterpretation was caused by the fact, that I created a Texture with CreateTexture(x,y,4). So I believed that setting the maskflag would make clear to Blitz that 0,0,0 is the mask (as its stated in the docu) and that its Blitzs turn to do the right thing. Otherwise what is it worth to set a Flag if it has no effect? And the effect appears only when you LoadTexture? If it can do it while Loading why can't it doing it at Creating?
This causes irritation!
Loading a 24Bit colored Texture creates the mask automatic if the Flag is set - Creating a 24Bit colored Texture does it not although the Flag is set.
Maybe or obviously the Flag is only a signal to display it masked... but one still expects that rather the same action causes the same behavior - in this case ORs $ff000000 to a created Texture as its done to a loaded one.
(Edited) And this shows again, that Blitz3D urgently needs a major update - some little things here - some bigger things there!
For instance to solve problems like the one above: Color r,g,b[,a] ClsColor r,g,b[,a] and so on and on and 100s of other things out of the 1000s that have been suggested...
BMax killed B3D ;-(
(Correction) It didn't kill it - it's still alive - but its starving and gets isolated without attention ;-|