IE 11 Mouse\Touch Objects Bug

Link to .capx file (required!):

capx

The capx demonstrates a conflict when using both the Mouse and Touch objects in IE 11. The demo simply changes the mouse cursor from pointer to hand when over the boxes. When the white box is clicked it increases in size. When the black box is clicked the white box returns to its original size.

Steps to reproduce:

1. Run the app in chrome - it works fine

2. Then run it in IE 11 - it fails

3.

Observed result:

All works fine in chrome.

In IE 11:

The cursors fail to change as expected and clicking the boxes does nothing.

But if you delete the Touch object from the project it works

Expected result:

All should work as described in IE 11, without having to delete the touch object from the project

Browsers affected:

Chrome: no

Firefox: don't know

Internet Explorer: yes

Operating system & service pack:

Windows 8.1

Construct 2 version:

R150

IE11 on Windows 8.1 seems to set the cursor just fine for me. The other issue with click events not firing should be fixed in the next build.

Ashley

Thanks for your reply.

Please note:

The purpose of this post and the example capx was to show a bug related to mouse cursor when previewing with IE 11. The bug remains when the app is exported as a Windows 8 app.

As noted, I also am using the final release of Windows 8.1, and all completely up to date.

I spent considerable time tracing the CURSOR problem.

I came across this problem putting the final touches to a game while implementing cursors for when the mouse hovers over buttons - a simple procedure. The game has both touch and mouse input as is required by any Win8 app, and in this situation the mouse click events (apparently not firing as you stated) are not a problem in the game - all works as expected - BUT cursor changes do not.

In the game I am using the cursors plugin developed by thehen so I tested to see if it was the same for the C2's built-in mouse\cursor support - and it is.

When you run the example capx the cursors do change as expected, UNTIL you click something - any thing, after that the cursor will remain in its current state.

Hopefully it is some how related to the bug with the mouse objects firing problem, so I eagerly await the next release.

Kind Regards....

With the fix, the cursor seems to change just fine on IE11 (Windows 8.1 here as well) even after clicking on a bunch of things, so hopefully it won't be a problem any more.

Hi ASHLEY.

Just installed R151, and while the example capx works now, it has completely broken the Win8 game I am working on - now no clicks are registered at all but mouse cursor works fine.

It is definitely IE11 related, as every thing - as usual - works perfect in Chrome.

I spent the whole morning trying to trace it today but I really do not have the time to try to pin point the problem at the moment.

So I think I will save much more time if I roll back to last stable release for now, and forgo having WebGL in the Win8 app.

When I get time I will pursue the problems further....

Thanks for your efforts....

michael - I can't reproduce any issue with touch events running a Windows 8.0 app (although running it on Windows 8.1), and I've double-checked the code and it looks like it ought to work fine on both IE11 and IE10. Can you post a new bug report following the guidelines?

ASHLEY. Yeah actually I logged in today to say you should close this post, which you have done already. (Sorry for taking few days to get back to you)

I've tried to find out what the problem is my end, but no success.

I decided rolling back was not an option - too many cool features added to C2! And since the game was just one level (with the intent to add more levels after publishing) I decided to start from scratch.

The game uses a global HUD approach, and while there is still much to do, so far the cursors problem is not a problem at all!

So it was most likely something I am doing that I am just too stupid to spot! I just can't for the life of me see why it worked in Chrome and not in IE. urrgggg. <img src="smileys/smiley7.gif" border="0" align="middle" /> <img src="smileys/smiley1.gif" border="0" align="middle" />

This time since the cursor feature is implemented from the start, I can keep any eye on what - if anything - causes it to malfunction.

So with all that said, if I find anything I will get back, if not the bug is myself. <img src="smileys/smiley29.gif" border="0" align="middle" />

Sorry for wasting your time on this.

Thanks for great software! <img src="smileys/smiley20.gif" border="0" align="middle" />