1 <h1>ViewSrv</h1>

     2 <p>

     3 The table below lists the View Server panics.</p>

     4 <code>1</code>

     5 <p>

     6 View Server creation failed. 

     7 </p>

     8 <code>3</code>

     9 <p>

    10 A bad client call was made - i.e. the opcode sent by the client was

    11 one not defined in <code>TVwsRequestOpcode</code>. 

    12 </p>

    13 <code>6</code>

    14 <p>

    15 The view that View Server is trying to remove has not been found. 

    16 </p>

    17 <code>7</code>

    18 <p>

    19 An application tried to add a view with an application UID other

    20 than its own. 

    21 </p>

    22 <code>8</code>

    23 <p>

    24 The custom message sent along with a view activation request was

    25 not copied across to the server properly. 

    26 </p>

    27 <code>9</code>

    28 <p>

    29 An attempt was made to remove the currently active view. 

    30 </p>

    31 <code>10</code>

    32 <p>

    33 A client has requested a view event even though it still has an

    34 outstanding request open. 

    35 </p>

    36 <code>11</code>

    37 <p>

    38 The most common panic. A view has taken too long to complete its

    39 implementation of <code>ViewActivatedL()</code> and must, therefore, be

    40 panicked to stop it from blocking the entire OS. 

    41 </p>

    42 <code>13</code>

    43 <p>

    44 An attempt was made to activate a view that does not support the

    45 current screenmode. 

    46 </p>