Finds the correct shared memory chunk based on window group id.

This is used for performing first phase of hit testing.

Finds window server client's connection handle based on given window group identifier.

This is used for finding correct shared memory chunk based on window group identifier.

Handles connection requests from client application. This has to be called for every application that connects to the click plugin.

Area registry immediately tries to connect to the chunk created by client application. This function leaves with Standard Symbian OS error codes in case connection fails.

Handles disconnect request from client application. This has to be called for every application that disconnects from the click plugin.

Clears stored information about a window group that is closed.

This function has to be called when click plugin receives a notification about closed window group.

Records information about a newly created window group.

This function has to be called when click plugin receives a notification about created window group.

This function is used for hit testing one chunk.

It is assumed that the given chunk is the chunk of that application, where pointer event shall be delivered.

Does hit testing of given pointer event against area registry content.

Hit testing is done in three phases:

1. First this function uses window group identifier for finding the application, which shall receive the pointer event (registry contents has to be grouped by applicaitons because window identifiers are only unique inside one application)

2. Window handle is used for finding those registry entries, which are registered to the same window where pointer event hit now (coordinates are window -relative).

3. Window's registry entries are hit tested one by one against the given pointer event, and in case a match is found, then corresponding registry entries feedback type is returned.

This function checks whether given pointer event and area registry entry match, and sets feedback type accordingly in case they match.

It is assumed that pointer event shall hit that window, where given area is registered (as coordinates are window-relative).

Notice that feedback is actually returned in reference parameter aFeedback, and the main return value of the function tells whether hit testing should be continued on next possible area or not. This is because feedback can be "None" even if pointer event hit the feedback area (because "None" is a valid type for feedback areas)

Array of chunk handles and identifying window group identifiers. Each entry in the array represents one application and its registered feedback areas.

Information about last received pen down event. This can be used for determining whether pen up event should produde feedback or not.

Handle to the global semaphore, which is used for mutual exclusion when accessing shared memory chunks.

Here we store the information about created window groups. For each group we also store the connection handle, so that we can know into which application newly created window groups belong.