Oh right. Sometimes I store the previous value of a variable and compare the current value against the previous value (with a trigger once). That works as well because it keeps triggering as the value changes back and forth. Many ways to do it, but sounds like you've got it sorted.

Why not use an 'on collision' event instead?

If Sprite1 has a Text instance variable Variable1, then

Sprite1.Variable1 gives you the string in an expression

e.g. System | Sprite1.Variable1 = "test"

Yeah it's a bit more involved I guess but a lot of us are using the XDK. Trying with a new project is useful, I've solved lots of issues that way.

Hello,

I've installed the R198 version and discovered something strange with my positioned sounds, like if there was a dopller effect on them. (but I don't use that effect)

And I see in the patch note that the doppler effect is no longer supported and has been removed.

So I'm wondering what is going on with my sounds. Is that a bug ?

Anyone noticed that too ?

EDIT : Here is a video to show the effect on the saw sound.

After upgrading C2 I also got bad results with positional audio in an existing project (delay, distortion), so I changed them all to non-positional.. lucky for my project it's not a big deal.

edit: this was in preview in Chrome, but it previously worked fine in preview

If you want people to answer more quickly, you should post the capx, or create a minimal example capx that shows the problem.

Sorry for a rant.

But what I really dislike about C2 is the text object editor. Why are we limited to the text field? It is extremely inconvenient. Adding/editing even a paragraph of text takes longer time than it should

Yes it is inconvenient. For large blocks of text I do a 'set text' on start of layout. Then you get a text edit box that sizes to the amount of text you enter, and you can see all your text at once in the event sheet. I'm sure the new C3 editor will address this

Just keep a counter variable with initial value 1, and loop through the array keeping track of the 'current' and 'previous' array values. If current=previous, add 1 to the counter otherwise stop the loop. You should have your count.

BTW your descriptions are a little ambiguous but I'm going with what I think you're asking for.

I haven't tried it, but none of Name, Product, UserAgent or Vendor (or a combination) will do the job?

My question is how will you do TDD when you don't directly write code in C2? Also TDD does not replace manual testing.

I tested before and after the XDK update... same result :/ weird

So if I made a .capx file of my project, you could see what I was doing wrong?

Possibly Then we can open it in C2 and see your events. But without it we cannot. If you don't want to reveal a possibly advanced project, strip out everything but what causes the issue or make a separate one.