Digital Workshop

I think these two situations are related.

First. How can I identify the objects dropped onto a drop zone? ( I'm not asking about the obj33.GetName() part itself)

Said differently, if I add a script to a Dropzone object, I want to get the names of all objects dropped on it. Or, if I use a script with the object being dragged, I want to get the name of the dropzone where it's dropped.

I hope not to have to code every possible 'pair' into somedropzone.IsObjectIntersecting(somedraggableobject)


Which leads to the 'Second' situation. Maybe Collisions and IsObjectIntersecting is a more generalized case for this? Same idea applies.... identify which objects.


I'd hoped it would be 'simple' to do. Now wonder if this is going to be a real task.

[edited] Add link. Here a recent topic with sample Drag/Drop IMP file that could be used as starter for this. viewtopic.php?t=2994

what's wrong with GetName()?

I think I did not ask the right questions.

I've started using GetName() when I know which object I'm looking at. Or know enough to use 'eval'... Nothing 'wrong' with GetName().

I'm assuming a situation where I'll have lots of variability. Many objects, say, to drop. Or collide for that matter. A certain amount of unpredictability maybe. Let me work up a sample Imp in next couple days.

Maybe though I just 'missed' something 'basic' in Opus actions or script? -- for what an "object dropped" trigger (on dropzone) can return as far as information about those objects dropped.

Mac,

Maybe I can pose the question more simply, at least to get started.

If I have a Drop Zone object and use a Dropped Object Removed All Objects trigger, how would I identify that one removed object in a script?

for example... whichobject.Rotate(100)

OK, I'm probably going to get things muddled here but here goes nothing:

You have a drozone frame with 10 objects dropped onto it. You remove one of the objects and this triggers a script event (IE calls a function) but you want to know which object has been removed to use it in the function?

If thats right then something like this.

create a function:

function rotateObject(name)
{
eval(name+'.Rotate(90)')

}

Add a script action to the trigger on the object, whether drop, click or remove and in the script add:

objectRotate(this.GetName())

Mack

Thanks, Mac. From your outline of the code, that's not quite it.

Your code does help me achieve 2 things. Sets up the trigger and function (passing_obj_name). And cleans it up over what I started playing with.

I will play with your "starter" over next few days. Holiday here. However, I think the original question still begs an answer.

It's about associating the draggables and the dropzones.

In the case you set up, I won't know which Dropzone (DZ) has freed-up this object. I want to get at was it DZ-A, DZ-B, DZ-C....

Or the flipside question when I start with focus on the DZ, which Draggable was dropped or removed.

I think it's a curious scripting challenge -- if only in that I was thinking such info would be easily within "arm's reach".

Keeping it simple...

Create a page / publication variable for dropping and removing and use the corresponding trigger simply assign the name of the object dropped or zone removed from to its corresponding variable.

This way you'll always have the last object dropped and the last zone removed from.

Use this inconjunction with the setting of properties to have quick access to the current information but also be able to access stored information.

Mack

P.S you may need that pesky wait command to ensure that the variables are updated before trying to execute a script using them.

I've taken the suggestion of using page variables. Despite some trial and error, I've either missed it or a solution will require more alchemy.

For purposes here, I'm focusing on 1/2 the situation. Simply track which objects dropped and/or removed from Dropzone viewpoint. (set aside other issue, which dropzone a particular object dropped on from draggable obj view.).

The sample pub illustrates the challenge.

What I am noticing is that actions triggered from Dropzone (drops or removes) LAG behind data captured off of a Dragged/Dropped object trigger.

Let me know if the task is futile. I'll 'drop' this approach.

Rather than trying to keep track of where stars are?? why not have a function which just checks where they are when you need to know---possibly a ticker??

Still use drag and drop, but have a function which checks where a star is. If the drop zones are static you can test to see if the star is in a drop zone. Flush the function through Create a matrix of possible combinations and store it as an array??, but I'm not sure what the aim of the application is.

Sandy

Rather than trying to keep track of where stars are?? why not have a function which just checks where they are when you need to know---possibly a ticker??

Still use drag and drop, but have a function which checks where a star is. If the drop zones are static you can test to see if the star is in a drop zone. Flush the function through Create a matrix of possible combinations and store it as an array??, but I'm not sure what the aim of the application is.

Sandy

sorry---am I repeating myself?? how did I do that????

Sandyn,

I've been away a bit... computer surgery.

I'll take a look at your suggestions in next few days.

As for my purposes. One layout I want to create is have users input ideas into ~8 text boxes. Then I'll have them drag and drop labels for each text-input to start arranging and prioritizing. There's more involved, so I wanted to set-up this "tracking" to then generate a set of action steps which varies depending on their input.

I was thinking the drag and drop with make it 'visual' for them.

Part of it is I am just trying to learn what Opus is capable of. And I did not want to have to anticipate/code all possible combinations and permutations in advance.

Back later.

sandyn wrote:


I guess I have some things to 'try'. That above. Or maybe keep track of stars' coordinates along-the-way, and run a check against dropzone locations at the end. I'm still learning arrays and will have to invent some tricks to populate these states and locations.

Hope to get this 'reduced' or 'abstracted' so it's easy to reuse. Back in awhile.