Thanks for the input guys, I think I'll have a crack at WAVE-270 first as that seems to have some guiding information already, I have a look again at the delete functionality once the dust has settled.
Is there some way I can get the issue assigned to myself? or is that not something I need to worry about? I'll have a play with the code this weekend :) Regards On Fri, Dec 30, 2011 at 12:59 AM, Zachary “Gamer_Z.” Yaro <zmy...@gmail.com>wrote: > I think it would help even to make the delete happen onclick instead of > onmousedown. I have accidentally deleted blips when I just missed the > button I meant to click, but unlike Gwave, I cannot just drag my mouse away > before releasing the button. > > —Zachary “Gamer_Z.” Yaro > On Dec 29, 2011 7:00 PM, "Thomas Wrobel" <darkfl...@gmail.com> wrote: > > > How about a popup tickbox for "enable delete", so the first delete > > takes two clicks, but the rest only one? > > > > On 29 December 2011 23:28, Ali Lown <a...@lown.me.uk> wrote: > > >> There was some starter project that wasn't fully implemented - to add > a > > >> verification popup when deleting a blip. > > > > > > I often end up moderating/cleaning-up the wave with my friends in. On > > > Google wave this require opening the drop-down menu which takes time. > > > I really like the way it can easily be done on WIAB and the fact the > > > next blip's delete button auto-aligns into the same space making it > > > very efficient to delete whole chains of irrelevant blips. > > > Opening a confirmation dialog would be a severe irritation, when I > > > feel the delete button is sufficiently clear as is. > > > -- blog:http://thelifeofbenhegs.blogspot.com/ phone: +447767-322-122
