04-25-2023, 08:58 PM
Yeah. We cannot do this using ELEMENTSIZE alone. And I too agree that passing 0x18 in TYPE is not a satisfactory solution as those are related to the sizes of QB64 base data type.
I did not really pay attention to the note:
But I notice that TYPE is an _OFFSET and the remaining bits above 16 are unused.
So, we can use say bit 17 like:
This is kinda like what bit 11 is doing.
The idea of just adding a new _SND command is tempting. We did talk about it before, but I too do not remember the outcome.
I think we decided to use the ELEMENTSIZE and TYPE fields then. Not sure.
I did not really pay attention to the note:
Quote:If a future integer, float or other type doesn't have a size that is 1,2,4,8,16,32,64,128 or 256 it won't have a size-bit set.
But I notice that TYPE is an _OFFSET and the remaining bits above 16 are unused.
So, we can use say bit 17 like:
- [bit 17] 131072 = 24-bit audio data usually from _MEMSOUND and _SNDNEW
This is kinda like what bit 11 is doing.
The idea of just adding a new _SND command is tempting. We did talk about it before, but I too do not remember the outcome.
I think we decided to use the ELEMENTSIZE and TYPE fields then. Not sure.