# Mobile module - click event problem

**URL:** <https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644>\
**Category:** Ignition\
**Created:** [June 15, 2012, 3:35pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644 "2012-06-15T15:35:20Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![idelamer](https://avatars.discourse-cdn.com/v4/letter/i/e5b9ba/32.png) [@idelamer](https://forum.inductiveautomation.com/u/idelamer)\
**Post date:** [June 15, 2012, 3:35pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/1 "2012-06-15T15:35:20Z")

</div>

I noticed this problem on 7.4.3-beta1 and 7.5.0.

I’m using the Mobile Skeleton project. When in one of the “Main Windows”, clicking anywhere on the screen will cause the “Back” button to fire, and will return to the Navigation screen. Seems like the event coordinates are not matched to just the Back button.

This causes unwanted navigation actions when accidentally touching the screen, or e.g. attempting to click on a small component and missing.

Tested on Android 4.0, BlackBerry OS 6, and Firefox.

Cheers  
Ivan

---

<div class="post-metadata">

**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\
**Post date:** [June 15, 2012, 7:14pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/2 "2012-06-15T19:14:45Z")

</div>

Thanks for bringing this to our attention, this is confirmed to be a bug. I’m having a developer look at it and we will keep you posted.

---

<div class="post-metadata">

**Author:** ![idelamer](https://avatars.discourse-cdn.com/v4/letter/i/e5b9ba/32.png) [@idelamer](https://forum.inductiveautomation.com/u/idelamer)\
**Post date:** [June 15, 2012, 7:23pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/3 "2012-06-15T19:23:35Z")

</div>

Thanks James!

---

<div class="post-metadata">

**Author:** ![cire3621](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@cire3621](https://forum.inductiveautomation.com/u/cire3621)\
**Post date:** [August 30, 2012, 1:50pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/4 "2012-08-30T13:50:06Z")

</div>

Has this problem been fixed yet? We have spinners on some pages to adjust set point values in our mobile project but when pressing them on the iphone sometimes they work…and then all of the sudden if you press one it sends you back to the main Navigation Screen. So it’s hard to set a value when it is hit and miss on whether or not you can set your value before you are unintentionally brought back to the main navigation screen.

If we remove the home button and just use our own back buttons we created would this possibly remedy the problem?

---

<div class="post-metadata">

**Author:** ![Michael.Stofan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.stofan/32/3342_2.png) [@Michael.Stofan](https://forum.inductiveautomation.com/u/Michael.Stofan)\
**Post date:** [August 30, 2012, 5:51pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/5 "2012-08-30T17:51:15Z")

</div>

The fix for the issue this thread was originally opened for is still in progress. Did you use the skeleton project to build your mobile app?

---

<div class="post-metadata">

**Author:** ![cire3621](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@cire3621](https://forum.inductiveautomation.com/u/cire3621)\
**Post date:** [September 1, 2012, 6:32am UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/6 "2012-09-01T06:32:22Z")

</div>

Yes we did use the skeleton project…we liked the layout and just modified it for our application and look…but we dont understand while you may be pages in on a setpoints page for instance trying to change setpoints and then all the sudden you are are returned to the main screen when pressing a button that has no link associated with switching windows.

---

<div class="post-metadata">

**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\
**Post date:** [September 4, 2012, 7:23pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/7 "2012-09-04T19:23:54Z")

</div>

Can you upload your project so we can take a look at it? If you don’t feel comfortable attaching it to a post in the forum, you can e-mail it in to [support@inductiveautomation.com](mailto:support@inductiveautomation.com).

---

<div class="post-metadata">

**Author:** ![cire3621](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@cire3621](https://forum.inductiveautomation.com/u/cire3621)\
**Post date:** [September 4, 2012, 10:51pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/8 "2012-09-04T22:51:53Z")

</div>

Here is a copy of the mobile project file…  
[Endeavor\_Mobile\_2012-09-04\_1606.proj](https://us1.discourse-cdn.com/inductiveautomation/original/2X/b/bb31b62cabfb384dd80ee1aea34516a87f28b14a.proj) (272 KB)

---

<div class="post-metadata">

**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\
**Post date:** [September 4, 2012, 11:49pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/9 "2012-09-04T23:49:37Z")

</div>

Thanks for the upload, I will take a look at it and get back to you.

---

<div class="post-metadata">

**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\
**Post date:** [September 5, 2012, 10:39pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/10 "2012-09-05T22:39:10Z")

</div>

I have confirmed that this bug still exists. I will let the developers know about it.

---

<div class="post-metadata">

**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\
**Post date:** [September 5, 2012, 11:00pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/11 "2012-09-05T23:00:54Z")

</div>

For what it’s worth, I removed the home button from the skeleton project and replaced it with a label with a mouseClicked event (using “swapTo” to go back to the navigation screen) and it seems to fix the problem. Try removing that home button and replace it with some other component and see if that works for you.

---

<div class="post-metadata">

**Author:** ![cire3621](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@cire3621](https://forum.inductiveautomation.com/u/cire3621)\
**Post date:** [September 6, 2012, 2:01pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/12 "2012-09-06T14:01:34Z")

</div>

Thanks…yea we tried that and figured that might fix the problem before the post but wanted to be sure that is what it was that was causing the problem…and any updates on a reason or fix would be much appreciated…thanks for your time looking into this.

---

<div class="post-metadata">

**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\
**Post date:** [September 6, 2012, 3:23pm UTC](https://forum.inductiveautomation.com/t/mobile-module-click-event-problem/4644/13 "2012-09-06T15:23:24Z")

</div>

Glad you got it fixed. If there are any updates about this issue, they will be posted in this thread.
