WackyToaster's Recent Forum Activity

  • Update: I'm an idiot, I can just use the mouse plugin lmao

    Though I'm a little confused then what the point of the mousedown event in the runtime is.

  • You absolutely can. If snap to grid is turned off, you can (or rather should be able to) move the tilemap at whatever increments you wish. You can also try Alt+Drag which will disable snapping in general (even if snap to grid is turned on)

    Unless you're asking to draw individual tiles off-grid? That doesn't even make sense really, that's the whole point of tilemaps.

  • When in doubt

    supportoyi@construct.net

  • I'm setting up the mousedown event like this

    	runtime.addEventListener("mousedown", (ev) => doThing(ev));
    

    This works as expected for both right- & leftclick until I attempt to hold one and click the other. This should return ev.buttons = 3 except the event is not fired in the first place

    developer.mozilla.org/en-US/docs/Web/API/MouseEvent/buttons

    Using pointerdown doesn't work either. Is this a bug or am I doing something wrong?

    Basically I wanna do is

    	onLeftClick() {
    		if(rightButtonDown) doThing()
    		else doOtherThing()
    	}
    
  • You can update bundled addons by right-clicking the project name in the Project Bar, selecting Tools -> View used addons, and right-clicking the bundled addon. If you have a newer version of the same addon installed, there should be an option to update it.

    That's new to me :D, guess it isn't exactly something you can easily stumble upon by chance. Good to know!

  • That is for sure an interesting project. I don't think drawing pixel by pixel on sprites is gonna work out.

    Have you looked into this example project?

    editor.construct.net

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I found jquery is weird to implement. I never could get it to work by putting it into scripts or source files. It allegedly supports ES6 imports but alas it never works.

    But this addon works like a charm, add it to the project and you should be done. construct.net/en/make-games/addons/162/jquery-plugin

  • Do you have bundle addons active?

    I remember I had a similar issue and the reason was that the bundled addons would "overwrite" the installed addons even if they are an older version. This makes sense I think for compatibility.

    To update, I think you can simply disable bundle addons, close & reopen project, enable bundle addons again. You need to make sure all addons you had bundled are installed otherwise you won't be able to open the project with a missing addon. And just in case, make a backup, you never know when things are going to implode.

  • But the game works on web and desktop too.

    Haha ok, that makes sense. I guess you can't use the debugger when testing that specific case. Not sure if it's really worth to file it as a bug report but it can't hurt

    github.com/Scirra/Construct-bugs/issues

  • Just wanted to update here now that it's in beta:

    Collision cells now perform roughly 1.5-3x better than rBush depending on the test (tested with size 50 x 50). Big improvement, really awesome!

    I do hope though that this beta cycle will also add this to scripting and SDK. I mean we can now do this in javascript "IRuntime.setCollisionCellSize()" but technically it's pretty much entirely useless, unless I do my collision checks with Events which I'd rather want to avoid.

  • 1. That appears to only happen with debug view, since with a regular preview you can detect touch way outside of the window, even returning negative touch coordinates

    2. It's relatively safe to assume that since a regular preview works fine, it will also work fine after export. In that case you can probably just check along the lines of "if touch.X < 0 OR touch.X > viewportWidth OR touch.Y < 0 OR touch.Y > viewportHeight

    3. If you think of any touch device like a phone... how would you ever touch something that's not on screen?

    The only question is why this behaves differently in debug view, but it has probably something to do with the interface of the debugger.

  • If you're styling with CSS you can try to use CSS resets/normalize.

    necolas.github.io/normalize.css

    There's a bunch of different versions of CSS resets out there if you google, but the point is exactly to ensure that everything looks the same across different browsers. Adding it now will likely break most of your alignments and stylings initially, but the hope is that it would at least be consistently broken and subsequently consistently fixed across all browsers.

WackyToaster's avatar

WackyToaster

Member since 18 Feb, 2014

Twitter
WackyToaster has 26 followers

Connect with WackyToaster

Blogs