same here http://www.ludumdare.com/compo/ludum-dare-24/?action=preview&uid=5046

in extremis

Every ticks -> set speed to startSpeed + floor(points/100) * 10

the speed with increase by 10 every 100 points

I think as far as the tutorial goes you can put all the action described in a start of layout condition as there doesn't seem to be any interactive stuff (no input from the player) and no evolution in time (no animation or movement)

andreyin

yep thanks for the screen that's exactly the bug (:

Hi Ash,

New version looks cool. I was trying my website menu on r100 to check for visual changes.

Although it's visually the same (which is great) I found a quite weird but.

When I click on one of the link and go back to the page with the back button of the browser, the page gets dramatically scaled (didn't notice it was scaling until I mousovered some blurry pixels)

Here you can try it

https://dl.dropbox.com/u/23551572/C2-Games/menu/index.html

The one exported with r99 is here

http://yanngranjon.com

I'm in fullscreen crop mode

and this bug only appears in chrome (didn't test ie or safari)

In firefox though, it's weird when I go back the layout appear in the same state as when I clicked on it. It doesn't seem to restart the layout. (same with r99 and r100)

tell me if you need the capx

Ashley I managed to request a picasa feed just with AJAX.

The astuce was to use yql (yahoo query language)

It seems query.yahooapis.com allows cross domain requests

you use it by requesting an url like that:

http://query.yahooapis.com/v1/public/yql?q=select * from xml where url="https://picasaweb.google.com/data/feed/base/user/112730361158490336509?alt=rss&kind=album&hl=en_US&imgmax=1600"

looks like an SQL query (:

I managed to make this prototype

https://dl.dropbox.com/u/23551572/C2-Games/Picasa/index.html

Depending on my motivation I might make an entire picasa viewer.

The only issue I had it that the xml object really don't like namespaces. It makes the XPath query fail.

I had to cleanup the xml and remove all the namespaced markup and attribute before loading it in the XML object.

I think I read that IE xml parser doesn't know how to deal with namespace, that might be why it's not yet implemented in C2 (?) but it would be great if at least there was a temporary action that would cleanup the namespace on load.

Anyway I managed to make it work (:

Yeah two collision polygon side to side will register as overlapped.

As educated guess, I'd say that it comes from how overlapping is calculated. and basically when two collision polygon are excactly side to side they share the same segment so in a sens they touchs each other.

If you're curious about how it is mathematically calculated, you can have a sneak peek at the source in the exporter folder in common_prelude.js around line 810.

Anyway, if your tiles are precisely aligned on a grid you can do something way simpler by checking position instead of collision polygon

+foreach tile
  Local number x=0
  Local number y=O
  Local number surrounding = 0
  +system: every ticks
    -> set x to tile.x
    -> set y to tile.y
  +system: pick all tile
  +repeat 4 times
  +tile: X = x+round(cos(loopindex*90))*cellsize
  +tile: Y = y+round(sin(loopindex*90))*cellsize
    -> add (loopindex+1)^2 to surrounding
  +system: every ticks
    -> tile: set frame to surrounding

clamp(value,minimum,maximum)

nearestFindableUnderRadius.capx

Be carefull I edited my last post (:

use the same object and put the graphics of "on" and "off" state in frame 0 and 1

on click on button -> set frame to 1-self.frame

Also, layers are only a way to organise your sprite and another way of controlling z-ordering and also isolate some effects.

In the end, as far as interaction and collision detection goes, it's just as if everything was in one layer.

I usually simply use either a text or a textbox (type textarea) object and put some "set text to" action where you would put print() with other languages.

I used to use the debug panel plugin from rex, but I often forget to delete it before export and as it opens another browser window, I often lose it behind my window so it's a pain. That's why I don't use it too much now.

Maybe Ashley could add the ability to prevent some plugin from being exported as a plugin setting or an object property.

Anyway, at some point I'd like to have a real debugger which displays any object values (no need to add tones of actions).

Maybe a chrome and firefox plugin could do the trick.