latest Android apk

[Rick Walsh]

On 30 December 2015 at 06:54, Dirk Hohndel <dirk at hohndel.org> wrote:

> The profile is... "interesting".
>>
>> So on one of my devices (the Samsung Galaxy S 3) I now get a reasonably
>> well scaled profile that appears clipped at about 90% in the x direction.
>> Neither the beige background nor the profile extend into the last 10%
>> horizontally of the drawing area.
>> On the old 2012 Nexus 7 I also get the 90% clip, but the scaling off, I'm
>> missing the x axes with the minute marks and the things below.
>> And on two other devices (Nexus 6P and Nexus 10) all I get is the beige
>> background (still, clipped at 90% in the x direction).
>>
>> This is so much fun! I haven't had this much fun since the Gtk days,
>> trying to make shit draw on the screen...
>> </sarcasm>
>>
>>
>> Here's a screen shot of my other 7in device, this one an Intel based
>> SurfTab - you can see that the profile is rendered beautifully - except
>> that it doesn't fill the complete area and is too tall to fit...
>>
>
> I have the same problem with the profile. The deepest point is cut as well
> as the end of the dive.
>
>
> So these are two different problems. The deepest point issue is
> mis-scaling. Which is driving me bonkers. I do exactly what the
> documentation says I should do - take the size of the
> contentsBoundingRect() and scale to that. Yet on some devices this works
> and on others it doesn't.
>
> The other one is that weird clip on the right. That's even stranger -
> nothing I could find in the documentation would explain this :-(
>
> I'm getting unpleasant scaling/cropping of the profile too.  I've played
around with the profile transformation, and am getting nowhere.  I really
have no clue about qml, qt, or even C++, so it's all just trial and error
(at least as much error as trial) and a bit of googling.

Prior to adding the margin (7e2898d QML UI: scale profile to allow for some
visible separation), the profile was better (but not ideal).


> More over, I get a crash when attempting to open the details of the latest
> dive.
>
> ---8<---
> 12-29 21:34:48.837   685  2326 I WindowState: WIN DEATH: Window{720d529 u0
> SurfaceView}
> 12-29 21:34:48.837   685  8545 D GraphicsStats: Buffer count: 7
> 12-29 21:34:48.842   685  8545 I WindowState: WIN DEATH: Window{2759cd6 u0
> org.subsurfacedivelog.mobile/org.qtproject.qt5.android.bindings.QtActivity}
> 12-29 21:34:48.897   214   214 I Zygote  : Process 15084 exited cleanly (1)
> 12-29 21:34:48.937   685 23669 I ActivityManager: Process
> org.subsurfacedivelog.mobile (pid 15084) has died
> 12-29 21:34:48.937   685 23669 W ActivityManager: Force removing
> ActivityRecord{d02da67 u0
> org.subsurfacedivelog.mobile/org.qtproject.qt5.android.bindings.QtActivity
> t1072}: app died, no saved state
> 12-29 21:34:49.052   685  2323 W InputMethodManagerService: Got
> RemoteException sending setActive(false) notification to pid 15084 uid 10174
> 12-29 21:34:49.640  3073  3341 W OpenGLRenderer: Incorrectly called
> buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
> 12-29 21:34:49.640  3073  3341 W OpenGLRenderer: Incorrectly called
> buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
> ---8<---
>
>
> Sadly no useful information here. WIN DEATH basically means "he's dead,
> Jim".
>
>
I've found if I install Subsurface-mobile over a previous installation,
sometimes I get a crash on opening a dive.  If I uninstall the app before
reinstalling it, I don't get a crash.  Can you repeat the crash if you
uninstall first?

Rick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20151230/6388d238/attachment.html>