Richard Munn

Another use case is having a CI that pushes out regular "unstable" builds - I'd like a human testing process before a build is pushed into the live game So...

Yup, that sounds perfect to me. As you say, there's never any issue about "skipping" builds, as the branches would always just have a live build at the top

I'm seeing the same issue as the OP This is my launch json ``` { "version": "0.2.0", "configurations": [ { "name" : "Attach to Prism", "type" : "duk", "request" :...

The debug string option seems best to me, as other than the debug lines, it wouldn't need any other code changes. Some use cases I can imagine: - start and...

Would that be smart enough to switch between GPS and cell location if the user turns gps on and off whilst the app is running, or would we need to...

Yeah - put simply it currently just uses the extra-course cell location provider, which fails entirely on devices that don't have cell radios (e.g. Nexus 7). What we really want...

It already does check for the most recent update when it does a weather refresh, in case the OS has a newer location than the one it was last notified...

Yeah, we don't even need a particularly accurate fix (we're just trying to get weather for the current town/city, after all) - so really we just need a simple way...

That stuff all happens within Monitors.java https://github.com/benjymous/MWM-for-Android/blob/master/src/org/metawatch/manager/Monitors.java

Yeah, looks good so far. I wouldn't worry too much about adding new functionality for pre-gingerbread, as long as the network location still works - the main issue is location...