# TKE_Dictionary

## Opcode

ASCII | D
Hexadecimal | 44
Decimal | 68

## Operands

Byte format
[Word pause_count],
[(pause_count)xLong pause_offsets]
Long count,
(count)x{
Long index,
Byte presence,
(number of bits set in presence)xLong item_offset,
[Byte item_options],
[Point bounds_min, Point bounds_max]
}
[Long first_pause_offset]
Long dictionary_offset

## Notes

A dictionary is a lookup table, providing the file offsets to specified items and their variations.

An application might, for instance, only read the first part of an appropriated created HSF file to get the basic layout and coarse representations of the scene (low level of detail representations). It could then use the dictionary to locate and read specific items to “sweeten” them on demand.

The dictionary will commonly be placed at the end of the file, so that by stepping back from the end the location of the dictionary can be found. A `TKE_Dictionary_Locater` may be used instead at the end of the file if it is useful to place the dictionary itself elsewhere in the file.

Conversation saved
HOOPSY BETA

### Hello! I'm HOOPSY

Your Docs generative AI assistant. Ask me anything about HOOPS Visualize 3DF or choose a sample question below to start a conversation:

What is HOOPS Visualize 3DF?
What are the latest release notes for HOOPS Visualize 3DF?
How do I start evaluating HOOPS Visualize 3DF?
How do I write my first sample application?
How can I get assistance?

HOOPSY may store conversations according to OpenAI's policy. Responses may not always be accurate.

HOOPSY is thinking...