Active Topics

 



Notices


Reply
Thread Tools
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#481
New build: Pull down to refresh just feels more intuitive.
No more refresh buttons. Pull down and refresh contacts and inbox.
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#482
New build:
-> qgvdial can now detect if the user's GV account has not been correctly setup.
-> The message box for errors has been improved. Looks less childish.
-> Font improvements for the pull down to refresh, as well as a bugfix for Maemo.
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
Posts: 61 | Thanked: 27 times | Joined on Jul 2010
#483
Its great that the pull-down refresh is working.

...please don't shoot me when I tell you that it 'refreshes' too easily...

I see two small problems with the pull-down refresh:
  • While you are scrolling up and down through your CONTACTS or INBOX; you do not know that you have reached the top until you scroll into the blank area.
    Which means you have a good chance of triggering the refresh.
  • Doing a flicking action, scrolling continues after the user has stopped touching it, and this can also accidentally cause a refresh.

For the first, we need some kind of TOP-OF-LIST marker.

For the second, I'm hoping 'Flickable.DragOverBounds' is the answer.
I did some Googling and found:
The boundsBehavior can be one of:
  • Flickable.StopAtBounds - the contents can not be dragged beyond the boundary of the flickable, and flicks will not overshoot.
  • Flickable.DragOverBounds - the contents can be dragged beyond the boundary of the Flickable, but flicks will not overshoot.
  • Flickable.DragAndOvershootBounds (default) - the contents can be dragged beyond the boundary of the Flickable, and can overshoot the boundary when flicked.
Addendum:
In regards to the top-of-list marker, I would suggest an extra list item, like:
[Pull Me Down To REFRESH]
If it is possible, use a different background color {to drawn your attention} and very small font and small height {as to not waste space}.

I assume you decided on this pull-down method so that you would not waste any screen space.
But you will need something to let your users know its there.

Last edited by kbyork; 2012-03-05 at 12:32.
 
Posts: 61 | Thanked: 27 times | Joined on Jul 2010
#484
Once upon a time, I posted a suggestion for the OPTIONS menu (in landscape mode)....
When opening a sub-window that has scrolling, scroll its parent to the top of screen so that the sub-window can use most of the screen.
Recent mods to the OPTIONS menu has made this suggestion nearly useless.
Currently, only the Logs sub-window still has this problem.

Probably the quickest fix to this is to put Logs first in the OPTIONS menu.
i.e. so its always in the perfect position.

Last edited by kbyork; 2012-03-05 at 04:03.
 
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#485
Originally Posted by kbyork View Post
Its great that the pull-down refresh is working.

...please don't shoot me when I tell you that it 'refreshes' too easily...

I see two small problems with the pull-down refresh:
  • While you are scrolling up and down through your CONTACTS or INBOX; you do not know that you have reached the top until you scroll into the blank area.
    Which means you have a good chance of triggering the refresh.
  • Doing a flicking action, scrolling continues after the user has stopped touching it, and this can also accidentally cause a refresh.

For the first, we need some kind of TOP-OF-LIST marker.

For the second, I'm hoping 'Flickable.DragOverBounds' is the answer.
I did some Googling and found:
The boundsBehavior can be one of:
  • Flickable.StopAtBounds - the contents can not be dragged beyond the boundary of the flickable, and flicks will not overshoot.
  • Flickable.DragOverBounds - the contents can be dragged beyond the boundary of the Flickable, but flicks will not overshoot.
  • Flickable.DragAndOvershootBounds (default) - the contents can be dragged beyond the boundary of the Flickable, and can overshoot the boundary when flicked.
Hmm... I see your point.
Would it be simpler if I were to not refresh unless the list is kept pulled down for more than one second?
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
Posts: 58 | Thanked: 73 times | Joined on Jan 2012 @ Argentina
#486
I tried this application long ago, and got a "User login failure" messageas soon as I try to log in. I though it might have been some issue at the time, and I'd retry at a later release.

I downloaded qgvdial today, and still get the same issue.
Also, for some reason, .qgvdial/qgvdial.log is empty, so there's no log to provide.

Any hints on what the issue might be?
 
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#487
Originally Posted by hobarrera View Post
I tried this application long ago, and got a "User login failure" messageas soon as I try to log in. I though it might have been some issue at the time, and I'd retry at a later release.

I downloaded qgvdial today, and still get the same issue.
Also, for some reason, .qgvdial/qgvdial.log is empty, so there's no log to provide.

Any hints on what the issue might be?
On the settings page, click on Logs to expand it, then click "Send Logs" to send me the logs. Much simpler that way.
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
Posts: 61 | Thanked: 27 times | Joined on Jul 2010
#488
Yeah, that would work for me. But how do you tell all your users?

I'm guessing that only a small number of them are reading this blog.... or you certainly would have been voted into EXTRAS.

see amended post 483

Last edited by kbyork; 2012-03-05 at 12:45.
 
medri's Avatar
Posts: 50 | Thanked: 22 times | Joined on Dec 2009 @ Stuttgart, Germany
#489
I sent you an email with my logs as I still cannot log in ...
Hope it helps you in any way.
If you didn't get one from
manuel [at] fam kimmerle
, let me know and I'll send it again.
__________________
greetz

medri
 
Posts: 16 | Thanked: 8 times | Joined on Feb 2012
#490
i can not log in either.
 

The Following User Says Thank You to psycon For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 08:20.