> On Dec 29, 2015, at 11:36 AM, Miika Turkia <[email protected]> wrote:
>
> On Tue, Dec 29, 2015 at 8:34 PM, Dirk Hohndel <[email protected]
> <mailto:[email protected]>> wrote:
>
>> On Dec 29, 2015, at 10:28 AM, Dirk Hohndel <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> .519 should make it to the Google Play store soon - the release .apk that
>> you can simply upgrade to is also available in the daily downloads folder.
>>
>> The splash screen looks great - thanks Miika and Rick! It's awesome to see
>> more people contribute to the mobile app.
>
>
> Yeah, thanks Rick, you did something that I wasted two days on with no
> success :D
I feel that way all the time. Think about it this way - if you hadn't done all
the hard work up front, Rick wouldn't have been inspired to do his part.
I repeat, thanks to both of you!
>> 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 :-(
> 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".
/D_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
