MobileRead Forums - View Single Post

CoolDragon · 08-26-2010, 03:17 PM

A little improvement:

If I replace the code in statusbar_timeout_clock() from:

Code:

     sprintf(now_str, "<big>%2.2d:%2.2d</big>", local->tm_hour, local->tm_min);
     gtk_label_set_markup(GTK_LABEL(label), now_str);

to

Code:

     sprintf(now_str, "%2.2d:%2.2d", local->tm_hour, local->tm_min);
     gtk_button_set_label(GTK_BUTTON(g_menu_button), _(now_str));

There is a better chance that turning pages will trigger an update of the clock. I don't know why, somebody else can explain?

Also, there is something true with regard to Mackx's "suspend" theory: turning pages does NOT ALWAYS re-draw the clock if the time between page turning is long enough (like several minutes), but if you turn pages fast enough (maybe less than 5 seconds

, thus disables the 5-second suspend timeout), it is very likely to re-draw the clock.

08-26-2010, 03:17 PM	#40
CoolDragon Addict Posts: 244 Karma: 124 Join Date: Feb 2010 Device: none	A little improvement: If I replace the code in statusbar_timeout_clock() from: Code: sprintf(now_str, "<big>%2.2d:%2.2d</big>", local->tm_hour, local->tm_min); gtk_label_set_markup(GTK_LABEL(label), now_str); to Code: sprintf(now_str, "%2.2d:%2.2d", local->tm_hour, local->tm_min); gtk_button_set_label(GTK_BUTTON(g_menu_button), _(now_str)); There is a better chance that turning pages will trigger an update of the clock. I don't know why, somebody else can explain? Also, there is something true with regard to Mackx's "suspend" theory: turning pages does NOT ALWAYS re-draw the clock if the time between page turning is long enough (like several minutes), but if you turn pages fast enough (maybe less than 5 seconds , thus disables the 5-second suspend timeout), it is very likely to re-draw the clock. Last edited by CoolDragon; 08-26-2010 at 04:20 PM.