On Thu, Jul 9, 2009 at 5:37 PM, Vikas Saurabh <[email protected]>wrote:
> > > > This way is more subtle and actually works. Second of all, you wouldn't > want > > a refresh to happen while you are using the app, at least not in my pov. > > > Agreed it would be a bad UI that just changes in front of your eyes > when you are about to select something. > What I was wondering was, can there be a way in which I can just keep > this process running continuously not have to wait even 7-8(2 tab > switches to refresh the current tab) seconds to see the missed call? > > --Vikas > That's an interesting request :) Actually there are two approaches to this issue, the first (more correct in my opinion) find out why it takes so much time to populate a screen and then fix it. (this way switching back and forth would be quick) Second approach would be just adding a way to refresh the screen, but this is a problem as I don't think there's more room in the GUI for another button :) So I guess I'll just have to improve the data retrieval even more (actually it's not the data retrieval but the population of the gtk list, time to remove legacy support) Tom.
_______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
