Layer menu displayed without calling it
-
Hi,
On iPhone, using the app to go to route laboratory to edit a route, after setting a couple of points, layer menu appears without no cause.
Sometimes just after setting Waypoint name, others when scrolling map.On a little screen like iPhone, this is very annoying.
iPhone 17 updated to latest IOS and last app version
A video with error follows:
Regards
-
Hi,
On iPhone, using the app to go to route laboratory to edit a route, after setting a couple of points, layer menu appears without no cause.
Sometimes just after setting Waypoint name, others when scrolling map.On a little screen like iPhone, this is very annoying.
iPhone 17 updated to latest IOS and last app version
A video with error follows:
Regards
@Lluis-Arasanz It’s always annoying to have to create a route on such a small screen like your phone. Through this link, you’ll be taken to the web version of the Routeplanner and will leave the app. Since the website is being completely revamped this year, I wonder if any effort is still being put into improving the issue you mentioned.
Have you, on the other hand, tried the in-app planner yet? -
@Rob-Verhoeff
I know but the problem is that this behavior is not shown on iPad (portrait or landscape) nor on Android.I only reproduce on iPhone.
And yes, I tried other functions of app, but this post is done for a colleague that does not have English knowledge and can’t send the post.
I don’t know when web planner will be revamped, but, meanwhile, users can use it in the way they know. Also, even in-app planner is good, it’s not so good as web planner, which is more known for users.
Regards
-
Also…. Using web route planner from Safari does not shows this behavior, while in-app navigator does.
Regards
-
Also…. Using web route planner from Safari does not shows this behavior, while in-app navigator does.
Regards
@Lluis-Arasanz Thanks again, Lluís, for reporting what isn't working correctly and not trying to hide it by explaining what is. We're here to improve the product, not to conceal its flaws. Keep it up!
-
@Lluis-Arasanz Thanks again, Lluís, for reporting what isn't working correctly and not trying to hide it by explaining what is. We're here to improve the product, not to conceal its flaws. Keep it up!
@b0hd1, we are also here to see if it really is a flaw, or for example ghost-touch by a dirt or defective screen, or any other reason. Since this is the first question like this in many years, I cannot imagine it is induced by the app itself. One way to test is to try to reproduce this on other devices. The fact that it does not do that in Safari is good to know, but not a definitive reason to call it bug or being induced by the app itself, since the tap location can be slightly different. Of course you can also submit a support ticket. But what @Rob-Verhoeff says is correct, not much development will be done on the current web planner, especially not for one single person having a problem with it, that can be solved otherwise.
-
@b0hd1, we are also here to see if it really is a flaw, or for example ghost-touch by a dirt or defective screen, or any other reason. Since this is the first question like this in many years, I cannot imagine it is induced by the app itself. One way to test is to try to reproduce this on other devices. The fact that it does not do that in Safari is good to know, but not a definitive reason to call it bug or being induced by the app itself, since the tap location can be slightly different. Of course you can also submit a support ticket. But what @Rob-Verhoeff says is correct, not much development will be done on the current web planner, especially not for one single person having a problem with it, that can be solved otherwise.
This has been verified on, at least, 2 different devices.
First, a team mate with iPhone 17
Second, on my iphone 14.I can't reproduce on Android phone (the one I use on Bike) nor in iPad (also with IOS 26.2)
I used In-App Web planner before and do not noted this behavior.
Perhaps is not a bug, is only a missfunction o a ghost touch, but I think this is rare o two different same brand, different model phones used by 2 different people.
Also, is not first time that any programmer can install a bug (new or old) on a new software version. I do not say this is the problem, bun no one has the True.
After that, perhaps development team can make a test on other iphone also.
Best Regards
-
This has been verified on, at least, 2 different devices.
First, a team mate with iPhone 17
Second, on my iphone 14.I can't reproduce on Android phone (the one I use on Bike) nor in iPad (also with IOS 26.2)
I used In-App Web planner before and do not noted this behavior.
Perhaps is not a bug, is only a missfunction o a ghost touch, but I think this is rare o two different same brand, different model phones used by 2 different people.
Also, is not first time that any programmer can install a bug (new or old) on a new software version. I do not say this is the problem, bun no one has the True.
After that, perhaps development team can make a test on other iphone also.
Best Regards
@Lluis-Arasanz, yes it is good to know that it is reproducible, at least on two very different iPhones. I cannot help there, since I have no iPhone
. If it is really cumbersome you can submit a support ticket of course. -
@Lluis-Arasanz Can I suggest that in the toolkit you turn off Ask for waypoint name then there are fewer interactions with the screen. I have tested by making several routes using my iPhone 11 iOS 26.2 and I cannot reproduce your problem. Test video
-
@Lluis-Arasanz Can I suggest that in the toolkit you turn off Ask for waypoint name then there are fewer interactions with the screen. I have tested by making several routes using my iPhone 11 iOS 26.2 and I cannot reproduce your problem. Test video
Yes, this is a good point of view. Both of us will try and post results here.
Thank's!!!
-
@Lluis-Arasanz Can I suggest that in the toolkit you turn off Ask for waypoint name then there are fewer interactions with the screen. I have tested by making several routes using my iPhone 11 iOS 26.2 and I cannot reproduce your problem. Test video
We check it:
- With Toolkit option "Ask for waypoint name" on, Layer selecton menu appears "randomly even not touching near button icon.
- Deactivating "Ask for waypoint name", all works as expected.
Have you tested with this option on? At least, to see if it's a global behavior or not.
Thanks for suggest!
-
We check it:
- With Toolkit option "Ask for waypoint name" on, Layer selecton menu appears "randomly even not touching near button icon.
- Deactivating "Ask for waypoint name", all works as expected.
Have you tested with this option on? At least, to see if it's a global behavior or not.
Thanks for suggest!
@Lluis-Arasanz, that's a good find!
-
We check it:
- With Toolkit option "Ask for waypoint name" on, Layer selecton menu appears "randomly even not touching near button icon.
- Deactivating "Ask for waypoint name", all works as expected.
Have you tested with this option on? At least, to see if it's a global behavior or not.
Thanks for suggest!
@Lluis-Arasanz Yes I have tested. I believe it happens because of the position of the close button for the waypoint name X is over where the open button X is for the overlay maps.