影响推杆的破碎的道路标签 [英] Broken road labels affecting pushins

查看:68
本文介绍了影响推杆的破碎的道路标签的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好,

道路标签在路上影响图钉时似乎存在问题。有时,在初始化映射之后,道路标签不会出现在缩放级别12周围,而这似乎是导致该行为的原因。放大11& zoom 13似乎是
罚款。 

It seems like there is an issue with road labels while in road that is affecting pushpins. Sometimes the road labels will not appear around zoom level 12 after initializing the map which seems to be causing the behavior. Zoom 11 & zoom 13 seem to be fine. 

我没有设置"allowHidingLabelsOfRoad"在创建地图对象时,它应该默认为false。

I am not setting the "allowHidingLabelsOfRoad" when creating the map object, so it should be defaulting to false.

当标签似乎卡住而不是渲染时,有一个未被捕获的JavaScript异常"Uncaught tt {}"来自mapcontrol发布分支。 "掷n"在
尝试与道路中的任何图钉交互时,以下代码片段的底部似乎是源代码:

When the labels seem to be stuck not rendering, there is an uncaught JavaScript exception "Uncaught tt {}" coming from the mapcontrol release branch. The "throw n" at the bottom of the following code snippet seems to be the source when trying to interact with any pushpins in road:

 t.prototype.logCriticalError = function(n, i, r) {
            var f = mapsNamespace.GlobalConfig, h = mapsNamespace.Internal._CoreConfig().mapcontrolVersion, u = i && i.data && i.data.url, o;
            if (u = u && u.toLowerCase(),
            f.isMapsVertical || f.isMapsAnswer || !u || u.indexOf("virtualearth.net") > -1 || u.indexOf("bing.com") > -1 || u.indexOf("microsoft.com") > -1 || u.indexOf("live.com") > -1 || u.indexOf("bingapis.com") > -1) {
                u && (i.data.url = this._cleanUrl(u));
                o = n ? n.stack : u ? u : "";
                i && i.data && i.data.stack && (o += ";" + i.data.stack);
                (f.isMapsVertical || f.isMapsAnswer) && r && (o += ";" + window.location.href);
                var s = !n && u
                  , e = {
                    T: s ? t.MapsWarning : t.MapsError,
                    feature: "SDK",
                    action: i ? i.action : "",
                    data: i ? i.data : "",
                    partner: "Maps",
                    horizontal: f.isMapsVertical ? "Vertical" : f.isMapsAnswer ? "MapSerp" : "SDK" + h,
                    Name: s ? "MapsNetwork" : "JSError",
                    Text: n ? n.message : i ? this._serializeData(i.data) : "",
                    Stack: o
                }
                  , c = n ? "unhandledEx:" : u ? "network:" : "handledEx:";
                if (e.Text = e.horizontal + ";" + c + e.Text,
                n && (f.isMapsVertical || f.isMapsAnswer)) {
                    n.message = e.Text;
                    throw n;
                } else
                    ++this._exceptionCount <= 16 && (this.logObject(e, f.dynamicProperties.mapsIG),
                    this.flush())
            }
            if (n)
                throw n;

我已经能够切换到天线,这允许我与图钉交互并且不会抛出任何错误,但当我切换回道路时,错误再次开始,任何图钉变得不稳定并开始投掷上面的JavaScript错误。

I have been able to switch to aerial which allows me to interact with pushpins and does not throw any errors, but when i switch back to road, the error begins again and any pushpins become erratic and start throwing the above JavaScript error.

我已经能够在密西西比州的DeSoto国家森林周围一直复制这种行为,在道路上的缩放级别为12。

I have been able to replicate this behavior consistently around DeSoto national forest in Mississippi around zoom level 12 while in road.

该应用程序已经使用Bing地图几年了,所以这似乎是相对较新的行为。

The application has been utilizing the Bing map for a couple of years now, so this seems to be relatively new behavior.

如果您需要任何其他信息,请告诉我。

Let me know if you need any other information.

推荐答案

更新:

看起来如果在liteMode:true中初始化地图,则此错误消失。鉴于这一事实,看起来可能存在矢量标签冲突的错误。

It looks like if you initialize the map in liteMode: true, this error goes away. Given that fact, it looks like there may be a bug with vector label collision .


这篇关于影响推杆的破碎的道路标签的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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