Maptips issue with handheld and tablet
I may have discovered a bug (GE 4.9.0, HTML5 2.10.0) with maptips running on Handhelds and Tablets. I can successfully bring up a maptip when I click on the map. When I click on a different feature, it highlights it for moment, then unselects it and no results appear. When I click on it again, it works... after the next click is doesn't againt ...then it works ...then not... the pattern continues.
Is anybody else running into this?
Mike
0
-
I see the same behavour on my handheld, using the chrome browser. 0 -
BTW... Until this is addressed, I wrote a JavaScript module that runs the idenfity tool instead: /* BTS.MapTipFixModules This is a workaround to fix a bug in Geocortex (version 4.6.2 and 4.9.0). The MapTips for handheld and tablets don't allow the user to click continuously from feature to feature. Instead it works for every other mouse click. Logic: - The constructor runs a test to determine if the "shell" is not the "Desktop". For the Desktop shell, the mapTips work fine and this workaround isn't applied - When the Site is initialized, the code keeps track of the MapMouseDownEvent. - When the user clicks on the map, the code runs the Identify command, passing in the user's mouse click point geometry. - When the user activates a different tool, it releases control of the MapMouseDownEvent. Steps to add this to a viewer: 1) Open the Tablet.json.js and Handheld.json.js files... and (optional) ignore the Desktop.json.js file 2) Copy/paste this code as another entry into the libraries section. Hint: The libraries section is at the very top (starting about line 10) , { "id": "MapTipFixModules", "uri": "Resources/DNR_Customized/BTS_SEC/MapTipFixModules.js" } 3) Copy/paste this code as another entry into the modules section. Hint: do a text search for the module "Alert". Place this code following it. , { "moduleType": "BTS.MapTipFixModules", "libraryId": "MapTipFixModules" } */ dojo.declare("BTS.MapTipFixModules", geocortex.framework.application.ModuleBase, { constructor: function (app, id) { if (this.app.shellName!="Desktop"){ //this only applies to Handheld and Tablet this.app.eventRegistry.event("SiteInitializedEvent").subscribe(this, this.onSiteInitializedEvent); } }, onSiteInitializedEvent: function(site) { this.app.command("DisableMapTips").execute(); this.MD = this.app.eventRegistry.event("MapMouseDownEvent").subscribe(this, this.onMapMouseDownEvent); this.app.eventRegistry.event("ActiveToolChangedEvent").subscribe(this, this.onActiveToolChangedEvent); }, onMapMouseDownEvent: function(args) { this.app.command("Identify").execute(args.mapPoint); }, onActiveToolChangedEvent: function(args) { this.app.eventRegistry.event("MapMouseDownEvent").unsubscribe(this.MD); } }); geocortex.framework.notifyLibraryDownload("MapTipFixModules");0 -
Hi Everyone,
We may have fixed this issue with the 2.11.1 release of GVH:
BUG 20102: Map tip sometimes does not appear on handheld shell
Regards,
-Malcolm0 -
Hi,
This issue seems to have made a comeback.
I never had maptip problems on a tablet before but with GVH 4.12 after upgrade to ios13 there is no reaction whatsoever on a map tap.
Patricia Bongaerts0 -
indeed, in Chrome the maptips still work fine. Thanks for your quick and useful response. 0 -
Hi Patricia,
Tablet devices are using iPadOS instead of iOS 13, which we did find issues with in 4.12.2, These have been fixed and will be available for 4.13, due to be release some time in March 2020.
Thanks, Stefan
0 -
I'm seeing this bug as well. We upgraded to Essentials version 4.12. Now, on iPad running iOS 13 and with Safari, map tips and some other interactions that involved tapping the map, don't work. Sounds like this is expected until the release of 4.13?
Props to Mike BTW for the custom module.0 -
Also seeing this behavior, will try out 4.13 when it comes out. Just adding another thing that isn't working in Safari but is in Chrome on an iPad running iOS 13: Capture Geometry within a workflow. 0 -
Following... 0 -
So I just had my field crew try out an app in GE/GVH 4.13.1, and they're having the same issues as before. Did the fix make it into 4.13? 0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
10 kommentarer