Does it stay hidden, or come back later?

Probably obvious, but if it stays hidden, try destroying it instead of hiding it.

Sorry that didn't work for you.

Mine changed layouts rather than get hidden, but that should not effect much.

Have you tried dropbox to host your capx file?

You may not be able to post a live link, but I think I read you can post a text link to your examples.

Good luck with it!

Sockratease every tick ? But the the mouse over object should be an event so why do I have to check every tick.

If it changed and stayed changed elsewhere ok, but it is specifically over the buttons that it is not the hand.

As I said, it doesn't seem to make sense, but it worked. So I went with it.

The only reason I can think of is that there is a "on mouseover" type command changing things, but no "on mouseout" command to change it back.

That also makes no sense, but I never claimed to understand why it fixed the issue for me, only that it did and I was satisfied since there was no noticeable hit on performance. Call it a brute force solution if you like. I'm too new to Construct 2 to say anything more...

Hello all.

I've been using Construct 2 and have a member of the forum for a little while, but never posted because I keep finding answers to all my questions during my pre-posting searches!

So I guess I'll post here and say thanks to all those who answer people's questions and make life easier for so many more than just the ones asking

I've been around the web for a long time making websites, running forums, and generally being annoying to those who are easily annoyed by naughty people enjoying silly things.

I used to make flash games and before that I was a big fan of Enterbrain's PlayStation2 game-making-game, RPGMaker 2. It's ways of doing things is actually similar to Construct 2, so that helps me a little bit.

Thanks again to all the helpful members and staff who answered all the questions I had and found by searching without needing to post

OOH!

One I can answer!

I had this problem too, and there is probably a better solution, but I got around it by using an "every tick" command constantly setting the cursor back to "Normal" (it stayed changed when over the button).

There has to be a better way, but that got me going and the page was extremely simple so there was no noticeable slowdown.

I hope a better answer comes along so I can implement it - but meanwhile, that worked for me when I had the identical issue.