机器人onLocationChanged从来不叫 [英] android onLocationChanged never called

查看:170
本文介绍了机器人onLocationChanged从来不叫的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我实现了code应该返回present位置。

I've implemented code that should return present location.

首先,code:

public static double[] getLocation(Context context) {
        double[] result;
        lm = (LocationManager)context.getSystemService(Context.LOCATION_SERVICE);
        MyLocationListener ll = new MyLocationListener();
        lm.requestLocationUpdates(LocationManager.GPS_PROVIDER, 0, 0, ll);

        while(!hasLocation) { }

        result = ll.getResult();

        return result;
    }

    private static class MyLocationListener implements LocationListener {
        double[] result = new double[2];

        public double[] getResult() {
            return result;
        }

        @Override
        public void onLocationChanged(Location location) {
            if(location.getAccuracy() != 0.0 && location.getAccuracy() < 100) {
                result[0] = location.getLatitude();
                result[1] = location.getLongitude();
                hasLocation = true;
                lm.removeUpdates(this);
            }
        }

        @Override
        public void onProviderDisabled(String provider) {}

        @Override
        public void onProviderEnabled(String provider) {}

        @Override
        public void onStatusChanged(String provider, int status, Bundle extras) {}
    }

的问题是,虽然'语句中的所有stopps。当我试图在onLocationChanged()没有任何反应的第一线调试这个设置断点,但logcat的是显示像一些日志:

The problem is that all stopps on 'while' statement. WHen I've tried to debug this setting breakpoint on the first line in onLocationChanged() nothing happens, but Logcat was showing some logs like:

loc_eng_report_position: vertical_accuracy = 64.000000
DEBUG/libloc(1292): date:2011-08-11, time:10:51:03.372, raw_sec=1313052663, raw_sec2=1313052663,raw_msec=1313052663372

任何想法?

推荐答案

在同时(!hasLocation){}从做任何事情阻止你的应用程序。你要么需要处理的位置,在回调onLocationChanged,或者你需要启动位置管理器早很多,希望你有一个结果,按你需要它的时候。你不能忙等待答案。

The while(!hasLocation) {} is blocking your application from doing anything. You'll either need to deal with the location in the callback onLocationChanged, or you'll need to start the location manager a lot earlier and hope that you have a result by the time you need it. You can't busy-wait for the answer.

这篇关于机器人onLocationChanged从来不叫的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆