I tried to debug the problem of the clock not updating immediately after
a resume from suspended state (http://shr-project.org/trac/ticket/1240).
I didn't succeed, but here is what I managed to work out.
The updating code is simple Embryo script in one of Illume's .edj files.
Exactly the same code (duplicated) is used in the .edj file for SHR's
lock screen. This code uses the 'timer' function, which I assume maps
onto ecore_timer_add, which is implemented in the obvious way as a
select timeout.
I wondered how select behaves when the phone is suspended, left for a
while, and then resumed. As an attempted approximation to this, I
tried:
- using edje_player with a file containing the update code
- Ctrl-Z to suspend the program
- after a while, and between minute boundaries, resuming with 'fg'.
Result was that the time always updated immediately following the
resume. (Both on the phone, with current SHR-T, and on my Ubuntu
laptop.)
So it isn't as simple as that. The next ideas and questions that occur
to me are:
- How is suspending and resuming the whole phone different from how it
is for a single program?
- Could it be that the timer is running immediately after resume, but
something blocks the visual effect of it from being seen?
- Could the problem depend on multiple timers running? There's code in
ecore_timer.c involving the second timer on the list, which I don't
yet understand.
Hoping this may trigger a thought somewhere, or otherwise be of use...
Neil
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
