在Eclipse DDMS模拟器控制可能的错误？ [英] Possible bug in Eclipse DDMS emulator control?

问题描述

我刚刚升级到Eclipse 3.6。我救的Eclipse 3.5，并提出了原工作区的副本。

我现在发现我的GPS /绘图应用程序，它在3.5工作正常的错误，当我从使用模拟器控制选项卡中的DDMS透视图发送位置。我有一个标准的监听器：

onLocationChanged（位置定位）{...}

如果我打破了这个行头，已经发送了纬度/经度对53.5 / -3.0，那么mLatitude / mLongitude的位置参数已更改为53.508833 / -3.005000（12月6日的地方才会显示）。 如果我重复与Eclipse 3.5在其原来的工作区原来的项目工作，那么这正是一直到最小的小数位。这是完全一样的code在两个工作区。

Android的SDK是在这两个2.2和目标是谷歌的API 7级。

你会说，这是在Eclipse 3.6中的错误或SDK或插件？

我不认为这可能是我的一部分了错误，但我很乐意被证明是错误的。一定程度的0.005听起来可能不是很多，但它在一个大圆0.3海里。

解决方案

Android的使用没有与ADT插件推荐日食3.6。从的Eclipse ADT

 注意：有已知问题与ADT插件运行
 

     

的Eclipse 3.6。请停留在3.5至   另行通知。

所以，我不会感到惊讶，如果有与任何一个错误。

I've just upgraded to Eclipse 3.6. I saved Eclipse 3.5 and made a copy of the original workspace.

I now notice an error in my GPS/mapping application which worked fine in 3.5, when I send a location from the DDMS perspective using the emulator control tab. I have a standard listener:

onLocationChanged(Location location){...}

If I break on the first line of this, having sent the lat/lon pair of 53.5/-3.0, then the mLatitude/mLongitude in the location argument have changed to 53.508833/-3.005000 (6 dec places only shown). If I repeat with Eclipse 3.5 operating on the original project in its original workspace, then it's exactly right down to the smallest decimal place. It's exactly the same code in both workspaces.

The Android SDK is 2.2 in both and the target is Google APIs level 7.

Would you say this is a bug in the Eclipse 3.6 or the SDK or the plugin?

I don't think it can be an error on my part, but I'd be happy to be proved wrong. 0.005 of a degree may not sound much but it's 0.3 nautical mile on a great circle.

解决方案

Android recommends not using eclipse 3.6 with the ADT plugin. From Eclipse ADT

Caution: There are known issues with the ADT plugin running with

Eclipse 3.6. Please stay on 3.5 until further notice.

So I wouldn't be surprised if there was a bug with either.

这篇关于在Eclipse DDMS模拟器控制可能的错误？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！