Hey all,

First of all a request to the administrator, could you remove the thread named ‘TOUCHLIBRARY EXAMPLE 3 : PuzzleGame (Version 1)’ thanks.
Today I got some feedback on my puzzlegame and it motivated me to create and release the final version (unless any weird bugs occure).

Application
#Title:
PuzzleGame Version 2 (Final)

#(Short) Description:
A standard puzzle game.

#Used library:
(My own) TouchLibrary

#How to:
- First make sure the global flash security settings link to the swf.
http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager04.html
- Run OSC.
- Run FLOSC.
- Run PuzzleGame.swf.
- Define the screen by touching the red crosses with one finger.
- Puzzle away!

#Options:
- Insert row; You can insert as many rows as you prefer.
- Insert column; You can insert as many columns as you prefer.
These options make it possible to create your own amount of puzzle pieces.
- Next puzzle; Creates the next puzzle by randomly picking an image from the imagelist.

#Imagelist:
In the images folder you can find the photo’s and an XML document. It’s possible to add your own photo’s. Just place a photo with a dimension of 400x300 in the images folder and add it to the XML document. Click as much on the Next Puzzle button till your photo appears.

All feedback is welcome.

The documentation for the Touch!Library will be located at http://www.crystalminds.net/multitouch/

Excellent Mark! I’ll try this as soon as I get home…

Hey Mark, just tried the app with the TUIO Simulator and it works very well here at work. I see you fixed the snap to grid problem as well. Well Done!

Yup :D Though it plays much better without the simulator, much more fun too.

You’re right, I just wanted to try it at work Once again Mark, well done and keep those apps coming!

Mark, I noticed while inserting 6 or more columns and/or 7 or more rows, the puzzle pieces do not ‘snap’ to the grid properly. Please see screen shots below.

Hope this helps

Hey Mark,

A quick note about your calibration methods in the beginning of the puzzle:

It does not work if you do not use “direct manipulation"… What I mean is I cannot see where I am touching… I only have a camera watching my hand… no image projection, so I am basically guessing where to touch after seeing my cursors on a typical LCD monitor.

Maybe you can make it optional somehow, cause its a really great idea.

The more calibration = better

Hi Mark,

your application is great and I like to play around with it but I do have three suggestions which you might consider in a future version of this cool program.
- Why is there this 400x300 limit when it comes to picture resolution? Especially on high quality projections, the images look very poor when scaled up.
- You are wasting a lot of space around the actual grid for the picture. I assume you wanted to have some spare space to temporarily store the pieces when you are actually solving the puzzle. Nonetheless, I think especially if you remove the limitation above, the grid should take more space than at the moment, or make it a least customizable.
- When one moves to the next puzzle, the application should retain the current row and column setting.

Great work, keep up ! The calibration feature is a perfect solution when you don’t want to run the application in fullscreen.

Wow these are all very good responds.

Ok first, Fairplane, that’s a nasty bug! I am currently with family in Boston so I can’t fix it right away and to be honost at the top of my head I wouldn’t know what would cause it as I remember the code would just put the piece at the xy of the beginning of the row/column. Will look into that if I get back.

Second, nuiman, to be clear “direct manipulation” is without the image being projected on the screen right? So you just do something with your hand on your device and look for the interaction occuring on the screen right? Wouldn’t the calibration then not be more suitable for you? I mean you can just select every top of your device and make that your screen. Else I guess I could make an option to skip the calibration procedure, wouldn’t be that hard.

Third, IRQ, this application was actually more a fun side project to see if I were able to design a flexible dynamic puzzlegame to test my touch library called MultiTouch!Library (wow that name is just amazing so original lol). I learned a lot from it. Anyhow I will take your suggestions in consideration. To answer your questions:
- Why 400x300? Because I expected to have more time designing this little puzzle game and I wanted to leave enough room for game elements like a timer, highscore, maybe even the full picture already showing stuff like that.
- Same reason for the grid space, thought it would be need to center it, but the space was meant for other elements. But it now functions as more space for your pieces.
- Yes, that’s a good idea.

I thought the calibration was a good solution too, it has been improved in a later version of my touch library which unfortunatly this puzzlegame doesn’t use yet.

The next game I will design, will be more complete and more in the shape of a board-game. I also have no idea what it eventualy is going to be like but I hope you bare with me

Hey Mark, That’s cool, just letting you know..

Ps. If there is enough animo for people wanting to see and maybe even use the code for the MultiTouch!Library I will release it’s source and documentation after I get back from America. To see a little sample of how the library works, look at this post: http://nuigroup.com/forums/viewreply/8876/.

Fairlane - 23 April 2008 10:34 PM

Hey Mark, That’s cool, just letting you know..

Lol fairlane that is one super fast reply! I wasn’t even done writing my ps! :D

HeHe! Just happened to be on at the right time