Yeah, not nearly as complex as a full game, but still! Gotta give you props. <img src="smileys/smiley17.gif" border="0" align="middle" />

It's a black screen in Chrome, but it works fine in Firefox 10.0.1. (Except, for some reason, it's aligned to the top left of the screen rather than the center, did you do that on purpose?)

I can't really help any more than letting you know that much... Good luck getting it working. <img src="smileys/smiley5.gif" border="0" align="middle" />

List your system specs. Operating system, graphics card, which browser, the whole shebang.

One thing you need to remember is that Ashley is just one guy, and there's a looooooottt of different computers out there. The update obviously works for many people, if not most; there's no way he can ensure it works for absolutely EVERYBODY. But if you tell him what system you're running, it'll be that much easier to diagnose.

That's pretty great. I always figured programming chess would have to be incredibly tedious... Was it as bad as it sounds?

Either way, it's really fun. I suck at it, though, so maybe I'll leave it up to everyone else to thoroughly test it. <img src="smileys/smiley36.gif" border="0" align="middle" />

I whipped up a small example to test a solution for you. It looks like it works, so hopefully it's what you're looking for. <img src="smileys/smiley1.gif" border="0" align="middle" />

db.tt/FmppZj3f

I placed a bunch of invisible squares around the smiley, each with a private variable called "Visible". When the TouchPoint object overlaps each square, its variable gets set to 1 -- meaning it's now visible -- and added to a global variable keeping track of how many can be seen. When it's over a certain number (right now it's set to 22, out of 24 squares total I think), you can say that the smiley itself is now almost completely uncovered.

Of course, the finer details are up for adjustment. You can change the number of invisible squares, or their placement, or how many need to be uncovered before you declare the smiley itself visible. Lemme know if I didn't explain it well enough. <img src="smileys/smiley5.gif" border="0" align="middle" />

A "replace ____ with ____" feature is on the to-do list from what I remember. If all you have to change is graphics, why change the object at all? You can just swap out the sprite for the current object and spare yourself the trouble.

Maybe they don't want to tackle a big game because features like that aren't in place yet... I'm partially in that boat, myself. No rush though!

In the object's list of animations, click the animation you want to change and then look at the property bar all the way to the left. You'll see some settings to change there, including animation speed. Change that to 12 and you're good to go!

If there was a possibility of exporting a capx to Classic, there would be no problem and all problems would cease to exist.

If you're suggesting that this should actually be made, I hope you realize how utterly impossible that is. It'd be like being able to convert C++ code to Java -- they're too different languages, despite their similarities. You simply can't switch between them like that.

Ashley to the rescue! Brilliant work, mate, absolutely brilliant...

And thanks to you too sqiddster, who knows when this would've gotten fixed if not for your campaign to make it happen? <img src="smileys/smiley36.gif" border="0" align="middle" />

One of my future projects was going to experiment with this, so I'm looking forward to seeing what you come up with. Good luck! <img src="smileys/smiley1.gif" border="0" align="middle" />

So it does indeed work! The tough thing here is... I don't really understand that stuff. <img src="smileys/smiley36.gif" border="0" align="middle" /> I'll be using these techniques for a lot more than just walking animations, and I'd rather stick to what I'm comfortable with for all that.

If it's literally impossible to do it the previous way, I'll force myself to learn how to effectively use lerp and sin and all that good stuff, but if it is possible I'd rather use that.