devel-docs: update a reference to 32-bit pointers.
Though the description of the POINTER type clearly tells of the new type
size, it was still refered as 32-bit only in this introductory text.
Let's fix this.
(cherry picked from commit 35f55ef07a
)
This commit is contained in:
@ -197,11 +197,14 @@ the very beginning of the file, and that the tile data blocks for each drawable
|
|||||||
must follow each other directly.
|
must follow each other directly.
|
||||||
|
|
||||||
References _between_ structures in the XCF file take the form of
|
References _between_ structures in the XCF file take the form of
|
||||||
32-bit "pointers" that count the number of bytes between the beginning of
|
"pointers" that count the number of bytes between the beginning
|
||||||
the XCF file and the beginning of the target structure. Note that therefore
|
of the XCF file and the beginning of the target structure.
|
||||||
the maximum address of a layer, channel, hierarchy or tile set is 2^32 - 1,
|
Pointers used to be 32-bit data. Since the maximum address of a layer,
|
||||||
i.e. at 4 GB. Everything after will be lost. Currently this doesn't play a
|
channel, hierarchy or tile set was 2^32 - 1, i.e. at 4 GB, the maximum
|
||||||
role yet.
|
size for XCF images before GIMP 2.10.0 was quite limited.
|
||||||
|
Now pointers can be 64-bit, allowing files big enough for any image
|
||||||
|
produced by current technology. See the chapter "Basic data types" for
|
||||||
|
description of the POINTER type.
|
||||||
|
|
||||||
Each structure is designed to be written and read sequentially; many
|
Each structure is designed to be written and read sequentially; many
|
||||||
contain items of variable length and the concept of an offset _within_
|
contain items of variable length and the concept of an offset _within_
|
||||||
|
Reference in New Issue
Block a user