latest Windows binary crashes

[Dirk Hohndel]

> On Jul 3, 2017, at 2:49 PM, Lubomir I. Ivanov <neolit123 at gmail.com> wrote:
> 
> On 4 July 2017 at 00:37, Dirk Hohndel <dirk at hohndel.org> wrote:
>> 
>>> On Jul 3, 2017, at 2:34 PM, Linus Torvalds <torvalds at linux-foundation.org> wrote:
>>> 
>>> On Mon, Jul 3, 2017 at 2:21 PM, Lubomir I. Ivanov <neolit123 at gmail.com> wrote:
>>>> 
>>>> Marble - we probably should start using a 2D map of sorts
>>> 
>>> Note that it's not just "2D map of sorts".
>>> 
>>> It needs to be something with good satellite imagery. Which presumably
>>> means "google maps" in practice.
>>> 
>>> I absolutely depend on seeing the actual reefs and shoreline features
>>> when I check (and occasionally fix) the location. At some point we
>>> tried some other map thing (I think the marine version of
>>> openstreetmaps) and it may have been acceptable for boating navigation
>>> needs, but certainly not for placing dive dites.
>> 
>> Correct. That's the main reason I'm loath to move away from Marble.
>> QtLocation is cute, but has maps, not satellite imagery. Not useful.
>> Same goes for openstreetmaps based stuff. It's got to be Bing or Google
>> satellite images.
>> 
> 
> i suggested this mid-june:
> http://lists.subsurface-divelog.org/pipermail/subsurface/2017-June/028642.html
> 
> simply a web page with google maps and some javascript that can be
> called from c++.
> 
> but instead of WebEngine use WebKit (for now)
> 

I could have sworn that I responded... but can't find it in the archive.

The challenge is "how do we place the dive site markers on that web page"?

We can't use this on mobile (but we don't have Marble there, anyway, so no
loss). But if you can work around that and have a POC, I'd love that.

/D