Dragging Object To “Snap” to Grid

conclusion:
meh.. screw all that noise..

just found a JS script that did the job.
did it once on the X once on the Y. job done.

snapToGrip = function(val,gridSize){
    var snap_candidate = gridSize * Math.round(val/gridSize);
    if (Math.abs(val-snap_candidate) < 2) {
        return snap_candidate;
    }
    else {
        return null;
    }
};

it works great. can scale the gridSize var too.

yasse wrote:

Hello dear GlifTek.
I Hope you doing good please i have been playing with the snap to grid function but it didn’t worked as it was supposed to be, but I’m wondering if it worked for you ?
please could you check the screenshot of the execution which certainly a mistake I have made,
thank you so much

Hi Yasse.

First thing is that your JS Call puzzle should go AFTER your move puzzle, because it’s snapping your object to what info you give it, which would be the coords it gets after you dragged something, which i’ll show here…

So here’s what my basic setup is:
This is taking the x and y coordinates of your dragged object and then processing them through the script according to your grid size and whether snapping is on/off. (holding down the “z” key. (maybe make it a different key since that messes with undo sometimes)

My puzzles are like this:

And I’m using this in the (yourApp).js file’s prepareExternalInterface portion:

    app.ExternalInterface.snapToGrid = function(val,gridSize){
        var snap_candidate = gridSize * Math.round(val/gridSize);
        if (Math.abs(val-snap_candidate) < 2) {
            return snap_candidate;
        }
        else {
            return null;
        }
    };

Where I got that script from was using “griP” with a “p” so i made it a “d”. (you still have that “p” and that might cause unseen issues if you use “d” in the JS Call puzzle’s name, which you didn’t but I am, so just pointing that out.)

Note that i just copied the puzzles over to a different part of my screen to show you their basic arrangement, not all intertwined into my project, so they may be a bit more understandable, directly copying them may not work per your 3d app file etc.. but it’s a basic layout.

I found I had to use ’round’ twice, though i most likely will go over that and find away to make it back to only once. (was issues with how fast the user would interact)

I’ll post a zip file in tutorials with it all setup and working in it’s own app folder for people to make their own changes on in a few days, with some other very useful “database query”, “print to console toggle” and “dictionary factory” puzzle setups I’ve been meaning to share.

I hope this helps!
-GlifTek