The table below lists the View Server panics.
1
|
View Server creation failed.
|
3
|
A bad client call was made - i.e. the opcode sent by the client was
one not defined in TVwsRequestOpcode .
|
6
|
The view that View Server is trying to remove has not been found.
|
7
|
An application tried to add a view with an application UID other
than its own.
|
8
|
The custom message sent along with a view activation request was
not copied across to the server properly.
|
9
|
An attempt was made to remove the currently active view.
|
10
|
A client has requested a view event even though it still has an
outstanding request open.
|
11
|
The most common panic. A view has taken too long to complete its
implementation of ViewActivatedL() and must, therefore, be
panicked to stop it from blocking the entire OS.
|
13
|
An attempt was made to activate a view that does not support the
current screenmode.
|
|