CreateImage(PB_Any)

[mestnyi]

It looks like it returns a descriptor, not an id.
PB 562 x(64)

Code: Select all

imgs(i) = CreateImage(#PB_Any, Width, Height)
    

[TI-994A]

It looks like it returns a descriptor, not an id.

That's the ID.

[mestnyi]

It looks like it returns a descriptor, not an id.

That's the ID.

What does this mean?
That's where I noticed it.
The following code gives an error.
On line 31 [ERROR] The specified #Image is Not initialised.
viewtopic.php?f=13&t=55683&hilit=pb_can ... ta#p419308

[DarkDragon]

It looks like it returns a descriptor, not an id.

That's the ID.

Well there is the ImageID(Number), which is basically the native image identifier of the operating system, and there is the PB Image Identifier.

CreateXyz(Number, ...) often returns the XyzID(Number) and the Number is the PB Image Identifier.
CreateXyz(#PB_Any, ...) always returns the PB Xyz Identifier.

The reason for this is historical: in former times there was no support for dynamic object creation with PB_Any. You always had to manage the numbers yourself. Also if you pass numbers >= 0 instead of #PB_Any (which is -1 IIRC), PureBasic will store the objects in an array list and this array list will be large enough to store the highest number as elements in it. So CreateImage(10000, ...) will ensure that the array is 10000 elements big.

[TI-994A]

The following code gives an error.
On line 31 [ERROR] The specified #Image is Not initialised.
viewtopic.php?f=13&t=55683&hilit=pb_can ... ta#p419308

That's not caused by the CreateImage() function or the #PB_Any directive. The error is caused by utilising a Long to hold the gadget numbers assigned by the 64bit compiler. Either compile the code with a 32bit compiler, or change the array to an Integer data type.

Essentially,

Code: Select all

Dim imgs.i(#NUMOFTILES)