spacedoubt's Forum Posts

  • functions are triggers. which means they only run once. you could call the function every 5 seconds instead.

  • How will that button avoid having to learn another program to paint with and switch between? Kids can handle saving and opening files (if not, then how are they going to learn programming?).

    I've been giving my 7-year-old C2 lessons for a little bit now and for image editing, it's best to have something simple. kids just want a paintbrush and colour choices, and maybe a fill bucket. they're not going to be digging in to the advanced functionality anyhow (and if they are, then I suspect they can figure out how to switch between two programs.)

  • how big are your music files? my browser told me something about it using 50mb. that seems pretty high.

  • just a little bumpity bump for the composers...

  • eli0s No idea how I missed that. heh.. Good to know!

  • Something that was introduced relatively recently is the ability to link and update image files. So, if a png (for example) image is open in lets say Photoshop, when you save it and hit update in C2's Image Editor it will also change.

    I had heard talk, but did not realize this had been implemented. Guess I missed that. Cool!

  • that's not quite how containers work.

    shuffle is not too difficult to program with events. do some research on it. search the forums/tutorials. I'm sure you'll find something.

    Also, I suspect there is already a 3rd party plugin that does this.

  • The image editor is meant to just be a basic image editor, because there are plenty of powerful (free, even) image editors you can use and so the C2 developers can focus on making C2 better instead of remaking photoshop.

    There's not an all-in-one button for it, but you can save your image and then, of course, open it in whatever program you like.

    The manual also states that "the image editor is currently a work-in-progress and is not yet feature complete."

    Yes, it could be better, but priorities and all that..

  • tulamide I love dumb stuff like this. heh..

    I'm American, I say CONstruct as well.

    I think of it as a noun just because it's software. conSTRUCT would seem really weird to me.

  • use a container. and/or an on created command that pins em there. 1 line of code would do it.

    give the turrets greater range.

    or, to differentiate between smaller and larger targets, use two turrets on top of each other, one with larger objects for targets and a bigger range to make up the difference.

    there are a lot of not that difficult ways to fix this.

    but maybe you're right. maybe there is a better way. but it seems, to me, at least, that checking for one point, on what would presumably be a good number of targets, is going to run a lot better than checking the whole collision box for all of them. That's just my best guess as to why it is that way.

    Whether it's a bug or not, I'm just letting you know, it's not that difficult to deal with.

  • you mean you don't want it to move on the y axis?

    change touch.y to self.y

    EDIT: Are you trying to accomplish the same thing with the second one, or something different?

  • try scrollto: X: lerp(scrollx, mouse.X, 0.3*dt) Y: lerp(scrolly, mouse.Y, 0.3*dt)

  • Families?

  • There's no difference...

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • This is not a bug. There are a number of way to deal with this. Off the top of my head, you could set an invisible target pinned to the corners of your big objects.