Say you have an in-app purchase called "removeAds." You will want to make a boolean attribute called removeAds.

it still initializes when you click back on it. so what I'm trying to do is have a drop target (another actor). so when I drag and drop the main actor, I want it to kill it's ability to be dragged whe

I didn't see the column1 or column2 attributes used anywhere, they are probably not there on purpose.

I tried what you suggested by changing the game.Row attribute from Integer 0 to Integer 1 (so the Table would have a row to read from). This worked, but unfortunately this only read row 1. I then ch

if touch is pressed add IAP change attribute show ads to false and change attribute unlock levels to true

I tried that, so when I drag an object it uses an integer and drop it. so my thinking is that when I drop it on the drop actor it would kill the drag attribute of the actor. didn't work. every time I

if I want to kill the ability for an object to be dragged, is there a way to disable it once it's dropped on another actor? or anyone know a good workaround?

I'd keep it simple, just have a switch (an attribute) that when off stops the actor from being able to be moved.

and you created self attribute column1,column2 but not used any where

with the help of a great member here I'm thinking i'd use an attribute (boolean) on an object. when the boolean goes true it execute a drag, and when false use a drop (constrain behavior x/y). So a mo

ok so I think I have it. I have the attribute set to true and it allows the drag, when false it sets the x and y to be self. So it stays in place. A mouse down and up change the value of the boolean.

ok so I have a double condition rule, with the mouse down triggering and the attribute changing to true. so that works. Now in the cancellation process, rule would be something like mouse up, boolean

(Quote)

You need to constrain it's position once it can no longer be moved and block out the rule that allows it to be moved with touch.

I see you add an attribute to the actor in the properties panel, and make it a boolean. So if I create a rule that has the constraint aspects to drag, how do I connect the boolean to it? is it another

change attribute -> self.Difference TO game.touches.touch1.X - scene.camera.origin.X

Yes, I ve tried. But it doesn't answer properly. Don't really know why. Thanks for the answer, and thanks for the suggestion with "constrain".

(Quote)

Yes. In the Move behavior, use an angle attribute in the Direction expression and then change that attribute's value from your control button actors.

Give the actor a self attribute, let's call it 'X'