DipToCurrent() question

[milehi]

I am seeing problem where the DipToCurrent() value in my app changes. When the app starts, DipToCurrent(100) = 150 (my device is a HTC Evo Shift). After the app runs, and is suspended for a long duration, and then resumes, the value changes. A call to DipToCurrent(100) returns 100. Thoughts?

 

[Erel]

First note that you can write:

100dip

Instead of:

DipToCurrent(100)

How is your program resumes? From a service?

 

[milehi]

The problem occurs when the app is left running in background and not displayed, or after a long duration (overnight) - the phone screen dims but the app is still displayed. When the app is resumed again by the user, the dip value changes. My app includes a background service that uses CallSub to push data to the main activity, perhaps that is related to the issue.

 

[Erel]

I believe that I know what is causing it and it will be fixed in the next version. If you like send me an email to [email protected] and I'll send you the required fix.

 

[agraham]

That's an intriguing effect! For interest can you tell us the cause - something clobbering BA.density somehow?

 

[Erel]

It is caused when the Service starts the process (after the process was destroyed) and there is a call to one of the "common keywords" before any activity start. In that case Common.Density is initialized with the wrong value.

 

[dealsmonkey]

I've seen this aswell ! I have a listview on the main activity that was has smaller text after been the phone has dimmed. Close the app and restart and all is well.

I just thought it was my old eyes (43) playing up again !!!

 

[milehi]

Thank you Erel, I will send an email for the fix soon. Did I forget to mention you have a excellent product... keep up the great work. :sign0098: