|
CartoType iOS API 8.12-19-g3f49c29ef
for development in Swift and Objective C for iOS and Mac OS
|
Go to the source code of this file.
Typedefs | |
| typedef CtError | CartoTypeError |
| typedef uint32_t | CtResult |
Functions | |
| typedef | NS_ENUM (NSInteger, CtError) |
CartoType result codes and the result type.
| typedef CtError CartoTypeError |
A synonym of CtError.
| typedef uint32_t CtResult |
A result code typed as an integer.
| typedef NS_ENUM | ( | NSInteger | , |
| CtError | |||
| ) |
CartoType error codes. CartoType functions actually return integers typed as CtResult, which may be compared with these values.
No error, a successful result.
CtErrorGeneral is used where an error has occurred but no other CartoType error is applicable. For example, this error code can be used when FreeType returns an error code for illegal TrueType hinting instructions.
Use CtErrorNoMemory when an attempted memory allocation fails.
CtErrorEndOfData is returned by iterators and streams when no more data is available. It may be treated as an error or not depending on the circumstances.
CtErrorTextUnmodifiable is returned when an attempt is made to modify an unmodifiable string.
CtErrorTextTruncated is returned when text inserted into a string is too long for a fixed-size buffer.
CtErrorNotFound is returned whenever a resource like a file is not found, or a search fails. It may be treated as an error or not depending on the circumstances.
The code CtErrorUnimplemented is used for functions that have not yet been implemented, or for circumstances or options within functions that remain unimplemented because they are deemed to be either rarely or never useful.
If the graphics system detects an invalid outline, such as one that starts with a cubic control point, it returns CtErrorInvalidOutline.
The code CtErrorIo should be used for unexpected read or write errors on files or other data streams. This is for where you attempt to read data that should be there, but the OS says it's unavailable (e.g., someone has taken the CD out of the drive or the network is down).
CtErrorCorrupt is returned when illegal values are found when reading data from a file or other serialized form.
This error is returned by database accessors, typeface accessors, etc., to indicate that this data format is unknown to a particular accessor. It is not really an error but tells the caller to try the next accessor in the list.
This error is returned by transformation inversion if the transformation has no inverse.
This error is returned by the projection system if the projection causes overflow.
The code CtErrorCancel is returned to cancel an asynchronous operation that uses callbacks. The callback or virtual function returns this code. the caller must terminate further processing on receipt of any error, but this one indicates that there has been no actual error, but the handler has canceled the operation.
This error is returned when an invalid argument has been given to a function.
This error is returned by a data reader when it can not deal with the data version.
This error is returned by the base library when reading data or calculations result in overflow.
The error code returned by line intersection algorithms when the lines are parallel.
An attempt was made to draw a bitmap needing a color palette but no palette was provided.
An attempt was made to insert a duplicate object into a collection class that does not allow duplicates.
The projection for converting latitude and longitude to map coordinates is unknown or unavailable.
A palette is full and no new entries can be added.
The dash array for drawing strokes is invalid.
The central-path system failed to create a usable path.
A route was needed by the navigation system but no route was available.
There was an attempt to zoom beyond the legal zoom limits for a map.
There was an attempt to project a map object that had already been projected.
Conditions are too deeply nested in the style sheet.
There was an attempt to use a null font for drawing text.
An attempt to read data from the internet failed.
Division by zero in an interpreted expression.
A transform failed because an argument or result was out of range.
Reading a bitmap from PNG format failed.
Reading a bitmap from JPG format failed.
An object did not intersect a specified region.
An operation was interrupted, for example by another thread writing to a shared flag.
There was an attempt to use map databases of incompatible point format, datum or axis orientations to draw a map or find objects in a map.
A key supplied for encryption was too short.
No encryption key has been set.
A code for standard emergency messages.
A code for standard alert messages.
A code for standard critical messages.
A code for standard error messages.
A code for standard warning messages.
A code for standard notice messages.
A code for standard information messages.
A code for standard debug messages.
A function has been called which is available only when navigating.
The global framework object does not exist.
The global framework object already exists.
A string was not transliterable.
Writing a bitmap to PNG format failed.
There was an attempt to write to a read-only map database.
There was an error in the PROJ.4 projection library error other than a projection overflow.
No route could be created because there were no roads near the start point of a route section.
No route could be created because there were no roads near the end point of a route section.
No route could be created because the start and end point were not connected.
An unsupported feature was requested from the XML parser.
A map file was not found.
A font file was not found.
A style sheet was not found.
An attempt was made to set a route attribute on a feature info object that is not a route.
An attempt was made to set a non-route attribute on a feature info object that is a route.
No route data is available.
Too many fonts are used in a style sheet.
Too many box styles are used in a style sheet.
No road or other routable segment was found near one or more route points when calculating a route.
An attempt was made to use a route which is outside the current map.
The start of the range of errors in XML parsing or in the style sheet format, such as a syntactically incorrect dimension or color. The top byte is 0x10 for style sheet errors, or in the range 0x11 to 0x2A for Expat XML parser error codes.
The low three bytes give the error location: one byte for the column number (clamped to 0...255) two bytes for the line number (clamped to 0...65535).
The end of the range of errors in XML parsing or in the style sheet format.
The base of error codes for returning SQLite errors. The SQLite error code is placed in the lower two bytes.
1.9.3