ubuntu-phone team mailing list archive

[Andrea Cimitan <andrea.cimitan@xxxxxxxxxxxxx>]

On 02/10/14 18:56, Christian Dywan wrote:
> On 02.10.2014 17:36, Andrea Cimitan wrote:
> > On 02/10/14 16:02, Marco Trevisan wrote:
> > > Il 02/10/2014 16:55, Andrea Cimitan ha scritto:
> > > > We can change values per app (I have a branch for unity that will get
> > > > reviewed soon), but globally is not possible.
> > > > Proper solution must be done inside qt itself... there is no workaround
> > > > we can do in our sdk unfortunately.
> > > Not sure doing this per app is scalable, wouldn't be patching Qt a
> > > better solution for now?
> > Isn't that exactly what I said? :)
> > Unfortunately, it is not trivial... it's in the works, but won't be
> > any time soon I think
> > https://bugreports.qt-project.org/browse/QTBUG-35608
> >
> > Patching app is easier for now
> Do we have a specified amount based on gu or dp that would be a sane
> default?
>
> It looks to me that patching qquickflickable.cpp would be a trivial
> patch, taking GRID_UNIT_PX and multiplying it by whatever is preferrable.
>
> ciao,
>      Christian
The change I did in shell was:

flickDeceleration: 1500 * units.gridUnit / 8
maximumFlickVelocity: 2500 * units.gridUnit / 8

Default qt values, scaled for units.gridUnit / 8 (reference to normal 
screen dpi)

https://code.launchpad.net/~unity-team/unity8/flickables-speed-workaround/+merge/234298

ciao