Archive for March, 2014

SnapCode Update March 28

March 28, 2014

This week added some less visible but useful improvements:

– Support for cut, copy, paste, delete of pieces
– Support for double-click to add piece
– Refactoring to support more Java statement types
– Added piece foreground shape for better rendering of selected and DragOver states
– Changed rendering of pieces to use Lighting effect

The new piece lighting effect replaces the old style and makes the pieces look smoother. The old style was just 4 copies of the background at different offsets and shades – what NeXT Computer used to call 2.5D rendering. Below is an image of the new rendering.

NewPieceEffect

SnapCode Play Sound

March 15, 2014

This week we released an update that included a new playSound() method for the Scene and Actor classes. With this, any actor can simply call the method like this:

playSound(“MySound.wav”);

Just like with all other Scene and Actor methods, this can simply be dragged in as a puzzle piece. This goes great with SnapCodes ability to simply create a new file of type “Sound File” and record a sound on demand.

Here is a demo video that shows adding some simple sounds to an interactive key driven animation:

SoundPlay

SnapCode Play Sound Demo

SnapCode Pen Drawing

March 7, 2014

SnapCode gained another new feature this week – the actor class now has new pen methods:

penDown()
penUp()
setPenColor(name)
setPenWidth(value)

Now when an actor performs a move, it is easy to leave a trail behind it, which can be used to create interesting designs. Check out the pen drawing at the end of this video on Mouse and Keyboard sensing:

Thumbnail

SnapCode Mouse and Keyboard Sensing

March 7, 2014

This week we added a number of new features to SnapCode. The first is that the scene and actor classes now have methods to determine if the mouse has been clicked or if the mouse is being continuously held down:

isMouseClicked()
isMousePressed()

These can be used inside of “if” statement conditionals to perform operations only when the mouse is clicked (or continuously held down).

Similarly, the scene and actor classes now have keyboard sensing methods:

isKeyClicked(“name”)
isKeyPressed(“name”)

Where the name is just the key character, like “a”, “b”. Arrow keys can be specified with “right”, “left”, “up”, “down”.

Check out this video to see the new mouse keyboard sensing methods in action:

Mouse Keyboard Sensing

Thumbnail