thanks, i misunderstood. droppable.id in the function is coming through as "undefined" it does have an id
> > On 7 Feb 2006, at 17:47, Louis Walch wrote: > >> umm... if i remove the function name how does it know which >> function to use? >> >> > > sorry, i meant remove ": function", or rather change it to: > > function dropAction(... > > Where are you defining the function? From what you've typed, it looks > like you're defining an anonymous function in a hash - if you just > want a global function definition for 'dropAction', use the syntax > above. > > tom > > ------------------------- > http://www.smallroomsoftware.com > > > >>> >>> On 7 Feb 2006, at 17:35, Louis Walch wrote: >>> >>>> thanks for the help but you were right it should work - i just had >>>> a typo :) >>>> >>>> next issue............ >>>> tying to get it to hit a function onDrop, but its not working >>>> correctly. i >>>> was given this way of doing it last week on this board. when i load >>>> the >>>> page w/ FF i get "dropAction is not defined" >>>> >>>> dropAction: function(draggable, droppable) { >>>> alert("DROPED:" + draggable.id +" ON " + droppable.id); >>>> } >>> >>> Try removing "dropAction:" from that first line. >>> >>> >>> ------------------------- >>> http://www.smallroomsoftware.com >>> >>> >>>> >>>> . . . >>>> >>>> Droppables.add("drop_List'",{hoverclass:"highlightField",accept: >>>> ["draggable"],onDrop:dropAction}); >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>>> >>>>> On 7 Feb 2006, at 16:38, Louis Walch wrote: >>>>> >>>>>> thanks that worked... >>>>>> >>>>>> another related question.... >>>>>> im also writing Droppables.add with the Ajax.Updater. and the drop >>>>>> area >>>>>> was written when the page was originally loaded (not the >>>>>> ajax.updater area >>>>>> of the page). will it still be droppable? >>>>>> >>>>> >>>>> Sounds like it should work - javascript functions defined in the >>>>> containing page should certainly be accessible from script elements >>>>> in the updated fragment. >>>>> >>>>> >>>>>> when i run updater, it writes the dragable items, and they are >>>>>> draggable >>>>>> but they do not do anything when dropped on the areas. >>>>>> >>>>>> also, the drop areas are TD's maybe that is it. >>>>>> >>>>> >>>>> Hmm, does your drop area work for draggables delared in the >>>>> surrounding page (not in the fragment)? Any javascript errors/ >>>>> warnings? >>>>> >>>>>> >>>>>> >>>>>> >>>>>>> Also, be careful about the problem described here: >>>>>>> >>>>>>> http://wrath.rubyonrails.org/pipermail/rails-spinoffs/2005- >>>>>>> December/ >>>>>>> 001615.html >>>>>>> >>>>>>> (which crashes all but the latest firefox, I think). Also, if you >>>>>>> surround your script elements with <!--//<![CDATA[ ... //]]>--> >>>>>>> you >>>>>>> might have to remove them or you'll get javascript syntax >>>>>>> errors on >>>>>>> IE. I'm not sure if this is a well known limitation with >>>>>>> prototype or >>>>>>> not - I only ran into it yesterday. Prototype should probably >>>>>>> strip >>>>>>> these kind of comment lines before calling eval(). >>>>>>> >>>>>>> tom >>>>>>> >>>>>>> ------------------------- >>>>>>> http://www.smallroomsoftware.com >>>>>>> >>>>>>> >>>>>>> On 7 Feb 2006, at 15:35, Tom Riley wrote: >>>>>>> >>>>>>>> Pass evalScripts: true in the options hash passed to >>>>>>>> Ajax.Updater. >>>>>>>> >>>>>>>> tom >>>>>>>> >>>>>>>> ------------------------- >>>>>>>> http://www.smallroomsoftware.com >>>>>>>> >>>>>>>> On 7 Feb 2006, at 15:28, Louis Walch wrote: >>>>>>>> >>>>>>>>> using Ajax.Updater to update a section of a page with a <ul> >>>>>>>>> also >>>>>>>>> want to >>>>>>>>> write some javascript into it (because im trying to make >>>>>>>>> each of >>>>>>>>> the <li> >>>>>>>>> draggable. but the <script..... > are not being written. is >>>>>>>>> this >>>>>>>>> not >>>>>>>>> possible? >>>>>>>>> _______________________________________________ >>>>>>>>> Rails-spinoffs mailing list >>>>>>>>> Rails-spinoffs@lists.rubyonrails.org >>>>>>>>> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Rails-spinoffs mailing list >>>>>>>> Rails-spinoffs@lists.rubyonrails.org >>>>>>>> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Rails-spinoffs mailing list >>>>>>> Rails-spinoffs@lists.rubyonrails.org >>>>>>> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Rails-spinoffs mailing list >>>>>> Rails-spinoffs@lists.rubyonrails.org >>>>>> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs >>>>> >>>>> _______________________________________________ >>>>> Rails-spinoffs mailing list >>>>> Rails-spinoffs@lists.rubyonrails.org >>>>> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs >>>>> >>>> >>>> _______________________________________________ >>>> Rails-spinoffs mailing list >>>> Rails-spinoffs@lists.rubyonrails.org >>>> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs >>> >>> _______________________________________________ >>> Rails-spinoffs mailing list >>> Rails-spinoffs@lists.rubyonrails.org >>> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs >>> >> >> _______________________________________________ >> Rails-spinoffs mailing list >> Rails-spinoffs@lists.rubyonrails.org >> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs > > _______________________________________________ > Rails-spinoffs mailing list > Rails-spinoffs@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs > _______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
