![]() |
2012-03-03
, 20:30
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#482
|
![]() |
2012-03-05
, 02:15
|
Posts: 61 |
Thanked: 27 times |
Joined on Jul 2010
|
#483
|
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.
![]() |
2012-03-05
, 03:59
|
Posts: 61 |
Thanked: 27 times |
Joined on Jul 2010
|
#484
|
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.
![]() |
2012-03-05
, 06:11
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#485
|
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.
![]() |
2012-03-05
, 07:28
|
Posts: 58 |
Thanked: 73 times |
Joined on Jan 2012
@ Argentina
|
#486
|
![]() |
2012-03-05
, 07:50
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#487
|
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?
![]() |
2012-03-05
, 12:21
|
Posts: 61 |
Thanked: 27 times |
Joined on Jul 2010
|
#488
|
![]() |
2012-03-05
, 15:00
|
|
Posts: 50 |
Thanked: 22 times |
Joined on Dec 2009
@ Stuttgart, Germany
|
#489
|
manuel [at] fam kimmerle
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.