Rails spinoffs - Feb 2006 - cancelling droppable if draggable dropped on different droppable

I''m writing a web app in which I have several
''windows'' in which the
   user can perform given functionality.

   So for example I have one window which manages images on a server (drag 
   an image into a folder and the file physically moved on the server via 
   ajax ) These images can also be dragged into another window to create a 
   slideshow.

   My problem occurs if my image manager window is positioned over my 
   slideshow window. When I try to drag an image into a new folder and the 
   folder icon (which is a droppable) is located above the slideshow window 
   (again a droppable) both dcroppables receive the event.

   How can I ensure that the droppable with the greatest zindex receives 
   the drop first and then how can I ensure that the event is not passed to 
   the droppable below?

Or alternatively how can I ensure that a droppable is only activated if my
dragable is dropped out side of my image manager window?

   Many thanks
   Rob


-- 
e: rob-05GizLXov0i9FHfhHBbuYA@public.gmane.org
w: www.pollen-8.co.uk
t uk: 0871 218 0278
t fr: 00 33 (0) 5 46 34 31 20
skype: rob_clayburn

Rob Clayburn wrote:
>
>
> Or alternatively how can I ensure that a droppable is only activated 
> if my dragable is dropped out side of my image manager window?
>
>   Many thanks
>   Rob
>
>
To answer my own question I made each window a greedy droppable object.

Cheers
Rob

On 2/16/06, Rob Clayburn
<rob-M+duPSAH6l8PldudreuJTlpr/1R2p/CL@public.gmane.org>
wrote:
> Rob Clayburn wrote:
> >
> >
> > Or alternatively how can I ensure that a droppable is only activated
> > if my dragable is dropped out side of my image manager window?
> >
> >   Many thanks
> >   Rob
> >
> >
> To answer my own question I made each window a greedy droppable object.
>
Could you explain please ? I don''t really understand this greedy option
:/

>>     
>
> Could you explain please ? I don''t really understand this greedy
option :/
> _
>   
if a dropables greedy is set to true then any other dropable under it 
will not know that a dropable has been dropped on it.

For my case making the window a greedy dropable meant that you now have 
to drag the dragable outside its window for dropables underneath the 
window to react when to the drop.

On 2/16/06, Rob Clayburn
<rob-M+duPSAH6l8PldudreuJTlpr/1R2p/CL@public.gmane.org>
wrote:
>
> >>
> >
> > Could you explain please ? I don''t really understand this
greedy option :/
> > _
> >
> if a dropables greedy is set to true then any other dropable under it
> will not know that a dropable has been dropped on it.
>
> For my case making the window a greedy dropable meant that you now have
> to drag the dragable outside its window for dropables underneath the
> window to react when to the drop.
Thanks a lot for the explanation