Ashley's Forum Posts

  • Yeah a lot of experts don't have very good things to say about w3schools - I'd find somewhere else to learn Javascript.

    Arsonide: there's no way around it, you pretty much have to rewrite plugins for each exporter anyway, because there's no one programming language which is ideal for *every* platform. That's why writing an exporter is a lot of work - because it's actually an exporter, runtime, and entire library of plugins!

  • Another small thing is I noticed a lot of semicolons missing - Javascript does automatically insert missing semicolons, but it's considered bad practice to miss them out - all your statements especially the 'acts["..."] = function () { ... };' should have that trailing semicolon too.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Don't forget to check the FAQ before asking!

    Mulkaccino: this is an open question, not sure about any specifics yet, this wasn't part of 0.x so it's not something we've planned in detail yet. It'll likely be that by default you only see options common to all platforms, but you can switch in to a mode where you can edit platform specific features.

    YetAnotherSuperhero: Yes, learning Javascript would be a great way to get in to scripting with C2! See extending C2 with javascript

  • You do not have permission to view this post

  • Arsonide: good tutorial but the expressions are wrong: the return value from expressions is ignored. You need to write PieExp like this: 

    exps["PieExp"] = function(ret) // all expressions take a 'ret' parameter
	{
		// Call set_string, set_int or set_float on the ret object to return a value
		// The value returned from this function is ignored!
		// If your expression has parameters, they follow on after 'ret', e.g.:
		// function(ret, x, y)
		ret.set_string("Pie");
	};[/code:2zaldcb6]

  • Not yet!

  • OK, I'll see if I can put together a quick template at some point.

  • I deliberately didn't split Vista/7 - it's just the split between XP and newer I'm interested in.

    Well, that's cool, mostly above XP then The global market share is still something like 50% for XP so I'm not going to stop supporting it any time soon, but it's nice to know the perks are being seen.

  • Yeah, reading through the definitions and comments in exporters\html5\edittime_prelude.js and common_prelude.js is a good way to get going quickly. All the flags are defined and commented (briefly) there, if you need more specific information, do ask!

  • Quick poll - just wondering how many of you are seeing the new Vista style Task Dialogs in the editor. XP doesn't support them, so XP users will be seeing old-fashioned messageboxes instead.

    This'd be handy to know anyway, because the Windows technology changed a fair bit with Vista, so a lot of new Windows features are "Vista and up".

    (Linux/Mac folks, sorry, no option for you )

  • It just means that HTML5 games can't have shader effects.

    ...unless WebGL takes off, but that requires Microsoft being on board.

  • If you know Javascript, writing plugins is actually very straightforward. I think that's a good alternative to scripting for now?

  • Ooh, appmobi looks interesting! We need a Touch input plugin really, but I don't have an iPhone or iPad which makes that tricky. It ought to just be a few javascript events. I could try "guessing" the code for it and put it here to see if it works.

  • I didn't mean to be defensive, it's just I don't want to end up in the situation where I'm doing a lot of work to get Wine compatibility or constraining the code to what Wine's idea of Windows is, rather than just writing the program itself. Becoming popular enough for Wine to notice us is another better solution!

    I guess Wine doesn't support the system 'edit' command, which is fair enough - it's an OS shell command. I think the best thing to do is just wait until there's a built in image editor.

  • It's just ordinary javascript accesses, so this.runtime.types["MySprite"] will return undefined if the object type with the name "MySprite" doesn't exist, and this.runtime.types["MySprite"].texture_img will also return undefined if there is an object type called "MySprite", but for some reason they gave that name to a non-Sprite object (e.g. text).