FIRMWARE ISSUE ?? iEikonEnv->InfoMsg(lBuf)

Login to reply to this topic.
Mon, 2007-12-24 13:18
parisnlc
Joined: 2003-09-15
 Forum posts: 165

[iEikonEnv->InfoMsg(sCurrentTime)]

I have been using this label display msg for the last couple
of weeks to quickly display the current time in my app.

I know it didn't work on 2nd Edition devices but assumed that
it must have been fixed for 3rd Edition. (I'm using N73).

It's a great little message box as it is discreet and non-intrusive.
I know there are other temporary popup windows but compared to this
label they are big and obtrusive so I chose not to use them.

Now, today I realised that I haven't seen my time string it for a while
it just didn't work anymore. So, I started going back through my app revisions/source code control to find the last place where it did work.
(I figured I must have done/added something to stop it working).

This is the weird part - it doesn't work in ANY of my previous versions
right back to version 0.0??!!

I also tried restoring backups of my N73 phone that I used for testing each revision. The label doesn't show in those previous backup versions either!!

What's going on?

The only coincidental/suspicious thing I can think of is that
last week I did a cold format *#7370# (for the first time since getting
my N73 from Vodafone) to clean the drive.
Not sure if it is related but seems that since then InfoMsg hasn't
been working.

Could this be a firmware issue?
Did *#7370# reset my N73 to some other vanilla setting that was
different to what was factory installed for/from Vodafone?

If so, does this imply that InfoMsg is very unstable and may/may not work
depending on device firmware version?

If so, that suggests it shouldn't be used at all!

I am glad I found this out now before shipping but it is
rather frustrating revelation.

I have always read loads of posts about people who just can't get InfoMsg
to work. I thought I was one of the lucky/clever ones, but
It seems I was neither clever or luck ..but pure fluke.

Please Nokia Experts comment on this so we know the score
once and for all. If there is documentation describing this anomaly
please post link.

Thanks.

~~~~

Fri, 2007-12-28 11:16
paul
Joined: 2004-09-14
 Forum posts: 140
Re: FIRMWARE ISSUE ?? iEikonEnv->InfoMsg(lBuf)

Its not a bug or anomoly, you need to enable extended error logging to get it to display.

Paul Todd

 
Sat, 2007-12-29 03:34
parisnlc
Joined: 2003-09-15
 Forum posts: 165
Re: FIRMWARE ISSUE ?? iEikonEnv->InfoMsg(lBuf)

Hi Paul

>Its not a bug or anomoly, you need to enable extended error logging to get it to display.

Very interesting point!

After I formatted my phone I didn't put back the Errd file that I had put on my phone folder.
Is that actually the root/fix to all of this?

I haven't tried it yet as I decide not to use InfoMsg(lBuf) in the end - but it makes sense
now that you pointed it out, so thanks for the tip Paul!

~~~~

 
Thu, 2008-01-03 13:00
parisnlc
Joined: 2003-09-15
 Forum posts: 165
Re: FIRMWARE ISSUE ?? iEikonEnv->InfoMsg(lBuf)

Just to confirm/update that putting 'errd' back into c:\resources
does indeed enable the InfoMsg [blue label] functionality on the
target device (N73 in my case).

Is InfoMsg really only meant for debugging?
It's a nice subtle feature for providing regular
feedback to user rather than massive Dialog boxes
that takes up a 3rd of the screen.

Is it possible to enable InfoMsg() without having to put
errd into c:\resources?

I'd like to use this blue label but don't want to force users to
install errrd in order for it to work (in case - like me, they
format their device and loose the errrd).

Can InfoMsg() be (safely) turned on by default so it is always
available without the presence of errrd?

~~~~

 
  • Login to reply to this topic.