I can't find out the panic reason or description such as ETEXT 12 or FORM 800. It is not in API doc. I tried to find it in relative header file. It is not there either. So can somebody tell me where can I see the reason of such kind of panice?
Re: How to check Panic reason in some library such as ETEXT or F
There is no general place to find out panic codes.
If it is not published (in API docs or header), then you can't find out what it means without looking at the source, or asking the guy(s) implementing the specific part.
If you are lucky, nokia might have hidden the information in some pdf on their site, but I wouldn't bet on it...
Re: How to check Panic reason in some library such as ETEXT or F
I was suspecting something like you mentioned. But isn't it stupid that they provide api to use and while it panics, there is no way to see what is wrong with it?Â
Re: How to check Panic reason in some library such as ETEXT or F
Yes... Its stupid.
If just each API implementor added a list of any panics they define to the header, with a brief description of what it meant, life would be a lot more easy for many 3rd parties...
Re: How to check Panic reason in some library such as ETEXT or F
Its really annoying I am also getting an ETEXT 31 panic . I don't know where I am making mistake. I 've tried searching everywhere but with no sucess. If any one knows it please respond.
Re: How to check Panic reason in some library such as ETEXT or F
I don't see anything useful there. Those guys end up with no conclusion. It remains an open question yet. I think only nokia and symbian employees could have access to those highly confidential api reference and they donÂ’t want to share it with third party developer. By such kind of strategy may destroy the whole symbian community in future. In my point of view, developing symbain is full of frustration. And no third party freeware developer can continue with such frustration.
Forum posts: 1233
If it is not published (in API docs or header), then you can't find out what it means without looking at the source, or asking the guy(s) implementing the specific part.
If you are lucky, nokia might have hidden the information in some pdf on their site, but I wouldn't bet on it...
Forum posts: 68
Forum posts: 1233
If just each API implementor added a list of any panics they define to the header, with a brief description of what it meant, life would be a lot more easy for many 3rd parties...
Forum posts: 78
Forum posts: 56
http://forum.newlc.com/index.php/topic,12689.0.html
Forum posts: 68
Forum posts: 78