Category: FBSCLI

Panics raised by clients of the Font and Bitmap Server.

1

No connection has been made to the Font and Bitmap Server.

2

Attempted to pass a command to the Font and Bitmap Server, but no connection has been made.

3

Unknown message.

4

There is an error with the Active Scheduler.

5

The startup of the Font and Bitmap Server failed.

6

Internal typeface store error: the list of accessed fonts (CTypefaceStore::iFontAccess()) is inconsistent with the font cache (CFbsTypefaceStore::iTwipsCache()).

7

The typeface store was unable to create a font due to a NULL font handle or address.

8

Attempted to access a NULL font pointer (debug builds only).

9

Invalid bitmap format (debug builds only).

10

Invalid bitmap display mode (TDisplayMode).

11

Invalid bitmap compression value (TBitmapfileCompression), or an unsupported operation was attempted on a compressed bitmap.

12

Bitmap decompression error (debug builds only).

13

Memory addressing error.

14

Either the display mode of the destination bitmap is not EColor256, or the two bitmaps are different sizes in CFbsColor256BitmapUtil::CopyBitmap().

15

An error occurred when constructing a hardware bitmap (debug builds only).

16

Bitmap not supported for compression.

17

Memory alignment error in a bitmap loaded from ROM.

18

Invalid Scan Line pointer.

19

New display mode not supported by CBitwiseBitmap::ChangeDisplayMode() (debug builds only).

20

New display mode not supported by CBitwiseBitmap::ChangeDisplayMode() (debug builds only).

21

When swapping a bitmap's width and height, the size of the new bitmap would exceed the amount of memory allocated.

22

CFbsBitmap::LockHeap() has been called on a bitmap by more than one thread (debug builds only). See Heap Locking in the Font & Bitmap Server for more information.

23

FbsShaper not yet called.

24

FbsShaper has invalid arguments.

25

Invalid compression threshold. Value needs to be 0 or greater, and less than 256.

26

Typeface index out of range. Index needs to be 0 or greater.

27

Problem copying bitmap data.

28

The panic occurs when the bitmap is read only.

29

The panic occurs when the bitmap type is invalid.