Defines the reasons for panicing the client thread.
0 |
The Akn skin server has sent a bad request. |
2 |
The panic occurs when the skin server is not connected. |
3 |
The panic occurs when there is a missing notifying handler. |
4 |
The panic occurs because there is no active object to handle the notification events |
6 |
The panic occurs because the constructor cannot create the shared chunk. |
8 |
The panic occurs because |
10 |
The panic occurs because the connection to Fbs-server needed for server side bit-maps cannot be merged. |
12 |
The panic occurs because the shared chunk cannot adjust to the area allocated. |
14 |
The panic occurs because the thread has to handle too may items that are defined. |
16 |
The panic occurs because the server cannot restore to default. |
18 |
The panic occurs because CAknsSrvSession cannot notify the pending notifications. |
20 |
The panic occurs because CAknSkinSrvSession dispatches the message two times. |
22 |
The panic occurs because CAknsSrvBitmapStore has a invalid build configuration. |
24 |
The panic occurs because CAknsSrv::CheckAndCreateDRMHelper has a fatal DRMHELPER failure. |