<div class="gmail_quote">Okay, if that's true, then I agree it's important. The original poster's comment says that he moved it to mouseStart, so I assumed it would still do the refresh as soon as you start to sort. Though, now seeing that the move was from mouseCapture to mouseStart, I'm confused how that would even make a difference; aren't they called back-to-back and only once per sort?</div>
<div class="gmail_quote">
</div><div class="gmail_quote">
</div><div class="gmail_quote">On Wed, Aug 26, 2009 at 12:43 AM, Paul Bakaus <span dir="ltr"><<a href="mailto:paul.bakaus@googlemail.com">
paul.bakaus@googlemail.com</a>></span> wrote:
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hey Scott,<div>
</div><div>in fact I wasn't talking about adding items during the sort, but even before that. Right now, the sortable is able to simply accompensate for anything that comes in / goes out, so people never have to call refresh - which to me, is quite a thing of beauty. In the new selectables, you have to call refresh() right now though, so it depends on the plugin wether it makes sense or not.</div>
<div>
</div><div>I think changing this behaviour would not be a big deal in terms of functionality, because as you said, you then have to simply call the refresh method, however I think it would introduce compatibility issues on a great scale.
</div></blockquote></div>