USER 23 Panic on startup from AppUi in 3rd Edition

Login to reply to this topic.
Thu, 2006-12-14 22:30
euroq
Joined: 2004-05-29
 Forum posts: 149
We have all probably gotten obscure error messages which have nothing to do with the problem which caused the error at one time or another while doing Symbian OS programming.  Probably 50 times.   Angry

Anyways, for anyone out there getting a User 23 Panic during the BaseConstructL() method of your AppUi (CAknViewAppUi) in Symbian 9 (3rd edition) which wasn't there in the 2nd edition (8 or below), I tracked the cause down to the fact that there either no EIK_APP_INFO or there was a blank EIK_APP_INFO resource in the .RSS file, i.e.

Code:
// In the .RSS file...
RESOURCE EIK_APP_INFO
    {
    }

This worked in the 2nd Edition, as I set the menus dynamically.  To avoid it, I've added the line cba = R_AVKON_SOFTKEYS_OPTIONS_EXIT; to the EIK_APP_INFO, but then the view is always set to that CBA.

Another side effect that I've noticed is that the following no longer works in the 3rd edition:
Code:
CEikButtonGroupContainer* cba = Cba();
if (!cba) {
cba = CEikButtonGroupContainer::Current();
}

if (cba)
{
TRAPD(err,
cba->SetCommandSetL(iBoolVar ?
R_AVKON_SOFTKEYS_OPTIONS_EXIT : R_AVKON_SOFTKEYS_OPTIONS_BACK);

);
cba->DrawDeferred();
}

If anyone's had any luck changing the CBA in the 3rd edition, I'd love to hear about it.

-euroq

Fri, 2006-12-15 13:20
Symbian_Neil
Forum Nokia Champion
Joined: 2006-10-12
 Forum posts: 463
Re: USER 23 Panic on startup from AppUi in 3rd Edition
Docs says
Quote
This panic is raised when any operation that moves or copies data to an 8 bit variant descriptor, causes the length of that descriptor to exceed its maximum length.

It may be caused by any of the copying, appending or formatting member functions and, specifically, by the Insert(), Replace(), Fill(), Fillz() and ZeroTerminate() descriptor member functions. It can also be caused by the SetLength() function. See TDes8.

Guess you can find the relevance inyour code

Good luck and cheers
 
  • Login to reply to this topic.