<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>dragsort Issue Tracker Rss Feed</title><link>http://dragsort.codeplex.com/WorkItem/List.aspx</link><description>dragsort Issue Tracker Rss Description</description><item><title>Reopened Issue: Dragged item bad positioned when using UI.Layout [24530]</title><link>http://dragsort.codeplex.com/workitem/24530</link><description>I use UI.Layout plugin to layout the page &amp;#40;top header, left menu, rest content&amp;#41;. When I use the List DragSort for a list inside a UI.Layout content pane, the dragged item is bad positioned. It has an offset equal to the top left position of the UI.Layout pane. I&amp;#39;m testing with IE7, jquery 1.3.2, dragsort 0.3, ui.layout 1.2.0.&lt;br /&gt;&amp;#160;&lt;br /&gt;I have examined the plugin code, and I think the problem is caused because the list.draggedItem is positioned absolute inside a div already positioned absolute. The top, left css styles are not relative to the document, but to the parent absolute div. The offset&amp;#40;&amp;#41; function is not 100&amp;#37; compatible with css&amp;#40;&amp;#123;top&amp;#58;y,left&amp;#58;x&amp;#125;&amp;#41; when ancestor absolute divs are in play.&lt;br /&gt;&amp;#160;&lt;br /&gt;I have found a solution for me&amp;#58; substract the position of the absolute containers. My patch is adding this piece of code just before the last statement of the setPos function&amp;#58;&lt;br /&gt;&amp;#160;&lt;br /&gt;&amp;#9;this.draggedItem.parents&amp;#40;&amp;#41;.each&amp;#40;function&amp;#40;&amp;#41;&amp;#123;&lt;br /&gt;&amp;#9;    if &amp;#40;this.style.position &amp;#61;&amp;#61; &amp;#34;absolute&amp;#34;&amp;#41; &amp;#123;&lt;br /&gt;&amp;#9;        var offset &amp;#61; &amp;#36;&amp;#40;this&amp;#41;.offset&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;&amp;#9;        top -&amp;#61; offset.top&amp;#59;&lt;br /&gt;&amp;#9;        left -&amp;#61; offset.left&amp;#59;&lt;br /&gt;&amp;#9;    &amp;#125;&lt;br /&gt;&amp;#9;&amp;#125;&amp;#41;&amp;#59;&lt;br /&gt;</description><author>mcm_ham</author><pubDate>Fri, 14 Jun 2013 07:30:09 GMT</pubDate><guid isPermaLink="false">Reopened Issue: Dragged item bad positioned when using UI.Layout [24530] 20130614073009A</guid></item><item><title>Reopened Issue: Only trigger dragEnd when order has changed [27382]</title><link>http://dragsort.codeplex.com/workitem/27382</link><description>P&amp;#58;S. Is here a way to send request to server only when some items really reordered, not by click only on item &amp;#63;&lt;br /&gt;</description><author>llorca</author><pubDate>Fri, 14 Jun 2013 07:30:09 GMT</pubDate><guid isPermaLink="false">Reopened Issue: Only trigger dragEnd when order has changed [27382] 20130614073009A</guid></item><item><title>Reopened Issue: Small error in code [30203]</title><link>http://dragsort.codeplex.com/workitem/30203</link><description>In version 0.4.1, Line 188 reads&amp;#58;&lt;br /&gt;&amp;#160;&lt;br /&gt;list.removeAttr&amp;#40;&amp;#34;data-origStyle&amp;#34;&amp;#41;&amp;#59; &amp;#40;causing an error&amp;#41;.&lt;br /&gt;&amp;#160;&lt;br /&gt;But should be &lt;br /&gt;&amp;#160;&lt;br /&gt;list.draggedItem.removeAttr&amp;#40;&amp;#34;data-origStyle&amp;#34;&amp;#41;&amp;#59;&lt;br /&gt;</description><author>mcm_ham</author><pubDate>Fri, 14 Jun 2013 07:30:09 GMT</pubDate><guid isPermaLink="false">Reopened Issue: Small error in code [30203] 20130614073009A</guid></item><item><title>Reopened Issue: dragEnd callback doesn't always fire when it should [31969]</title><link>http://dragsort.codeplex.com/workitem/31969</link><description>The example html page provided with your code doesn&amp;#39;t provide for a situation where this can occur but there is a fundamental flaw in the code&amp;#58; The dragEnd callback only fires when the item being dragged has it&amp;#39;s order changed &amp;#40;either within it&amp;#39;s own list, or within the new list that it is being dragged to&amp;#41;.&lt;br /&gt;&amp;#160;&lt;br /&gt;The documentation says&amp;#58; &amp;#34;dragEnd&amp;#58; The callback function that will be called after the dragging has ended.&amp;#34;&lt;br /&gt;&amp;#160;&lt;br /&gt;Unforunately this is not true.  If you want to see a situation where it doesn&amp;#39;t work that way, setup a page where there are is a master list containing a couple draggable item&amp;#39;s in it, and then a couple of other empty lists that can be dragged to&amp;#47;from, but which don&amp;#39;t have any items in them to begin with.  Setup the dragEnd callback to show an alert so that you know when it&amp;#39;s being fired.  Drag one of the items from the master list to one of the empty lists, notice the callback fires. Now drag that same item from the new list that it&amp;#39;s a child of, to another one of the empty lists.  Notice the callback doesn&amp;#39;t fire, even though the item was moved&amp;#33;&lt;br /&gt;&amp;#160;&lt;br /&gt;The bug occurs because the dropEnd callback is only set to fire when one or more of the items has it&amp;#39;s order changed within a list.  The callback should always fire if an item is dragged from one destination to another, regardless of whether the order changes.  Otherwise, if you only have a few items and a bunch of possible destinations, the dropEnd callback won&amp;#39;t get fired when expected &amp;#40;if at all&amp;#41;.&lt;br /&gt;&amp;#160;&lt;br /&gt;I patched the code so that it functions in the way I desired and I have attached the patch here.  Thanks for the script, let me know if anyone has any questions.&lt;br /&gt;</description><author>mcm_ham</author><pubDate>Fri, 14 Jun 2013 07:30:08 GMT</pubDate><guid isPermaLink="false">Reopened Issue: dragEnd callback doesn't always fire when it should [31969] 20130614073008A</guid></item><item><title>Created Unassigned: Draggable item with scrollbar inside [34156]</title><link>http://dragsort.codeplex.com/workitem/34156</link><description>Hi, I have a dashboard widget that is draggable nicely with List DragSort, however inside that &amp;#60;LI&amp;#62; the widget body &amp;#40;a div&amp;#41; have a specific size and a sometimes a scrollbar &amp;#40;overflow&amp;#58;auto&amp;#41;.&lt;br /&gt;&lt;br /&gt;The scrollbar doesn&amp;#39;t work on Firefox, and on IE creates a sticky effect very unpleasant.&lt;br /&gt;&lt;br /&gt;For what I see there are options for scrolling outside the draggable item but not inside...&lt;br /&gt;&lt;br /&gt;Does nobody have fund this issue&amp;#63; any way to work around this&amp;#63;&lt;br /&gt;&lt;br /&gt;Thanks&lt;br /&gt;</description><author>iuzzef</author><pubDate>Sun, 09 Jun 2013 16:45:26 GMT</pubDate><guid isPermaLink="false">Created Unassigned: Draggable item with scrollbar inside [34156] 20130609044526P</guid></item><item><title>Closed Issue: Dragged item bad positioned when using UI.Layout [24530]</title><link>http://dragsort.codeplex.com/workitem/24530</link><description>I use UI.Layout plugin to layout the page &amp;#40;top header, left menu, rest content&amp;#41;. When I use the List DragSort for a list inside a UI.Layout content pane, the dragged item is bad positioned. It has an offset equal to the top left position of the UI.Layout pane. I&amp;#39;m testing with IE7, jquery 1.3.2, dragsort 0.3, ui.layout 1.2.0.&lt;br /&gt;&amp;#160;&lt;br /&gt;I have examined the plugin code, and I think the problem is caused because the list.draggedItem is positioned absolute inside a div already positioned absolute. The top, left css styles are not relative to the document, but to the parent absolute div. The offset&amp;#40;&amp;#41; function is not 100&amp;#37; compatible with css&amp;#40;&amp;#123;top&amp;#58;y,left&amp;#58;x&amp;#125;&amp;#41; when ancestor absolute divs are in play.&lt;br /&gt;&amp;#160;&lt;br /&gt;I have found a solution for me&amp;#58; substract the position of the absolute containers. My patch is adding this piece of code just before the last statement of the setPos function&amp;#58;&lt;br /&gt;&amp;#160;&lt;br /&gt;&amp;#9;this.draggedItem.parents&amp;#40;&amp;#41;.each&amp;#40;function&amp;#40;&amp;#41;&amp;#123;&lt;br /&gt;&amp;#9;    if &amp;#40;this.style.position &amp;#61;&amp;#61; &amp;#34;absolute&amp;#34;&amp;#41; &amp;#123;&lt;br /&gt;&amp;#9;        var offset &amp;#61; &amp;#36;&amp;#40;this&amp;#41;.offset&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;&amp;#9;        top -&amp;#61; offset.top&amp;#59;&lt;br /&gt;&amp;#9;        left -&amp;#61; offset.left&amp;#59;&lt;br /&gt;&amp;#9;    &amp;#125;&lt;br /&gt;&amp;#9;&amp;#125;&amp;#41;&amp;#59;&lt;br /&gt;</description><author>mcm_ham</author><pubDate>Thu, 16 May 2013 11:29:23 GMT</pubDate><guid isPermaLink="false">Closed Issue: Dragged item bad positioned when using UI.Layout [24530] 20130516112923A</guid></item><item><title>Closed Issue: Only trigger dragEnd when order has changed [27382]</title><link>http://dragsort.codeplex.com/workitem/27382</link><description>P&amp;#58;S. Is here a way to send request to server only when some items really reordered, not by click only on item &amp;#63;&lt;br /&gt;</description><author>llorca</author><pubDate>Thu, 16 May 2013 11:29:23 GMT</pubDate><guid isPermaLink="false">Closed Issue: Only trigger dragEnd when order has changed [27382] 20130516112923A</guid></item><item><title>Closed Issue: Small error in code [30203]</title><link>http://dragsort.codeplex.com/workitem/30203</link><description>In version 0.4.1, Line 188 reads&amp;#58;&lt;br /&gt;&amp;#160;&lt;br /&gt;list.removeAttr&amp;#40;&amp;#34;data-origStyle&amp;#34;&amp;#41;&amp;#59; &amp;#40;causing an error&amp;#41;.&lt;br /&gt;&amp;#160;&lt;br /&gt;But should be &lt;br /&gt;&amp;#160;&lt;br /&gt;list.draggedItem.removeAttr&amp;#40;&amp;#34;data-origStyle&amp;#34;&amp;#41;&amp;#59;&lt;br /&gt;</description><author>mcm_ham</author><pubDate>Thu, 16 May 2013 11:29:23 GMT</pubDate><guid isPermaLink="false">Closed Issue: Small error in code [30203] 20130516112923A</guid></item><item><title>Closed Issue: dragEnd callback doesn't always fire when it should [31969]</title><link>http://dragsort.codeplex.com/workitem/31969</link><description>The example html page provided with your code doesn&amp;#39;t provide for a situation where this can occur but there is a fundamental flaw in the code&amp;#58; The dragEnd callback only fires when the item being dragged has it&amp;#39;s order changed &amp;#40;either within it&amp;#39;s own list, or within the new list that it is being dragged to&amp;#41;.&lt;br /&gt;&amp;#160;&lt;br /&gt;The documentation says&amp;#58; &amp;#34;dragEnd&amp;#58; The callback function that will be called after the dragging has ended.&amp;#34;&lt;br /&gt;&amp;#160;&lt;br /&gt;Unforunately this is not true.  If you want to see a situation where it doesn&amp;#39;t work that way, setup a page where there are is a master list containing a couple draggable item&amp;#39;s in it, and then a couple of other empty lists that can be dragged to&amp;#47;from, but which don&amp;#39;t have any items in them to begin with.  Setup the dragEnd callback to show an alert so that you know when it&amp;#39;s being fired.  Drag one of the items from the master list to one of the empty lists, notice the callback fires. Now drag that same item from the new list that it&amp;#39;s a child of, to another one of the empty lists.  Notice the callback doesn&amp;#39;t fire, even though the item was moved&amp;#33;&lt;br /&gt;&amp;#160;&lt;br /&gt;The bug occurs because the dropEnd callback is only set to fire when one or more of the items has it&amp;#39;s order changed within a list.  The callback should always fire if an item is dragged from one destination to another, regardless of whether the order changes.  Otherwise, if you only have a few items and a bunch of possible destinations, the dropEnd callback won&amp;#39;t get fired when expected &amp;#40;if at all&amp;#41;.&lt;br /&gt;&amp;#160;&lt;br /&gt;I patched the code so that it functions in the way I desired and I have attached the patch here.  Thanks for the script, let me know if anyone has any questions.&lt;br /&gt;</description><author>mcm_ham</author><pubDate>Thu, 16 May 2013 11:29:22 GMT</pubDate><guid isPermaLink="false">Closed Issue: dragEnd callback doesn't always fire when it should [31969] 20130516112922A</guid></item><item><title>Created Issue: Allowing a &lt;thead&gt; header block... [33956]</title><link>http://dragsort.codeplex.com/workitem/33956</link><description>The table code currently doesn&amp;#39;t allow a &amp;#60;thead&amp;#62; block at the top of the sortable rows - you can fix this with the following code at line 22&amp;#58;&lt;br /&gt;&lt;br /&gt;if&amp;#40; &amp;#36;&amp;#40;cont&amp;#41;.is&amp;#40;&amp;#34;table&amp;#34;&amp;#41; &amp;#38;&amp;#38; &amp;#36;&amp;#40;cont&amp;#41;.children&amp;#40;&amp;#39;tbody&amp;#39;&amp;#41;.size&amp;#40;&amp;#41; &amp;#61;&amp;#61;&amp;#61; 1 &amp;#41;&lt;br /&gt;  cont &amp;#61; &amp;#36;&amp;#40;cont&amp;#41;.children&amp;#40;&amp;#39;tbody&amp;#39;&amp;#41;.get&amp;#40;0&amp;#41;&amp;#59;&lt;br /&gt;</description><author>drbaggy</author><pubDate>Wed, 10 Apr 2013 20:41:09 GMT</pubDate><guid isPermaLink="false">Created Issue: Allowing a &lt;thead&gt; header block... [33956] 20130410084109P</guid></item><item><title>Created Issue: Error in ie 8 [33848]</title><link>http://dragsort.codeplex.com/workitem/33848</link><description>it doesn&amp;#39;t  work in ie 8. i test it in other browser and it work fine for me. There is a way to solve it &amp;#63;&lt;br /&gt;&lt;br /&gt;Thanks &amp;#33;&lt;br /&gt;regards.&lt;br /&gt;</description><author>pablodif</author><pubDate>Thu, 07 Mar 2013 11:58:11 GMT</pubDate><guid isPermaLink="false">Created Issue: Error in ie 8 [33848] 20130307115811A</guid></item><item><title>Created Issue: Dropping in container element does not work [33749]</title><link>http://dragsort.codeplex.com/workitem/33749</link><description>I have 2 lists w&amp;#47;a fixed height. I noticed when you drag from list 1 to 2 and release the mouse button when over list 2, but you are not over list item, then the move does not take. Unless you have moused over an &amp;#60;li&amp;#62; item from list 2, the drop does not work the way you&amp;#39;d expect.&lt;br /&gt;&lt;br /&gt;To fix the problem, I added a patch to the source code that checks when dragging between lists and if you&amp;#39;re dropping to a list and the list.placeHolderItem object isn&amp;#39;t in the current list, it&amp;#39;ll move the item to the dropped list container.&lt;br /&gt;&lt;br /&gt;This allows you to have a fixed height on your &amp;#60;ul&amp;#62; elements and drop the elements. This should also resolve issues where an &amp;#38;quot&amp;#59;empty&amp;#38;quot&amp;#59; element can be hard to drop to. This should also fix issues where there is margin&amp;#47;whitespace between the &amp;#60;li&amp;#62; items.&lt;br /&gt;&lt;br /&gt;I&amp;#39;m attaching my patch.&lt;br /&gt;</description><author>DanSwitzer2</author><pubDate>Fri, 08 Feb 2013 20:01:57 GMT</pubDate><guid isPermaLink="false">Created Issue: Dropping in container element does not work [33749] 20130208080157P</guid></item><item><title>Created Issue: Broken layout with dimensions in percentages [33636]</title><link>http://dragsort.codeplex.com/workitem/33636</link><description>I have an UL with 9 LI items laid out more or less like the image on the project&amp;#39;s homepage. The difference is that UL has width and height set to 100&amp;#37; within a fixed-dimension container, and all LI items have width and height set to 33.33&amp;#37; and floated left.&lt;br /&gt;&lt;br /&gt;What happens is that layout becomes broken in various ways when placeholder replaces one of the LI elements. I managed to fix this by removing the &amp;#96;.css&amp;#40;...&amp;#41;&amp;#96; part on line 124 &amp;#40;I am using the version of the code that can be downloaded from the download section&amp;#41;. &lt;br /&gt;&lt;br /&gt;I assume that the calculated width&amp;#47;height that jQuery returns doesn&amp;#39;t exactly match the way browser calculates 33.33&amp;#37; in this case.&lt;br /&gt;&lt;br /&gt;Here is the relevant CSS I use&amp;#58;&lt;br /&gt;&lt;br /&gt;.shuffleboard &amp;#123;&lt;br /&gt;    position&amp;#58; relative&amp;#59;&lt;br /&gt;    padding&amp;#58; 1em&amp;#59;&lt;br /&gt;&amp;#125;&lt;br /&gt;&lt;br /&gt;.shuffleboard ul &amp;#123;&lt;br /&gt;    position&amp;#58; relative&amp;#59;&lt;br /&gt;    margin&amp;#58; 0 auto&amp;#59;&lt;br /&gt;    padding&amp;#58; 0&amp;#59;&lt;br /&gt;    width&amp;#58; 100&amp;#37;&amp;#59;&lt;br /&gt;    height&amp;#58; 100&amp;#37;&amp;#59;&lt;br /&gt;&amp;#125;&lt;br /&gt;&lt;br /&gt;.shuffleboard li &amp;#123;&lt;br /&gt;    list-style&amp;#58; none&amp;#59;&lt;br /&gt;    float&amp;#58; left&amp;#59;&lt;br /&gt;    width&amp;#58; 33.333&amp;#37;&amp;#59;&lt;br /&gt;    height&amp;#58; 33.333&amp;#37;&amp;#59;&lt;br /&gt;    position&amp;#58; relative&amp;#59;&lt;br /&gt;&amp;#125;&lt;br /&gt;</description><author>brankovukelic</author><pubDate>Wed, 02 Jan 2013 21:33:24 GMT</pubDate><guid isPermaLink="false">Created Issue: Broken layout with dimensions in percentages [33636] 20130102093324P</guid></item><item><title>Commented Issue: No data-listidx attribute on list items when using multiple lists [33582]</title><link>http://dragsort.codeplex.com/workitem/33582</link><description>When using more than one list in the selector, with or without dragBetween set to true, data-listidx will be assigned to the UL elements used in the selector and not the child LI elements, leaving no way of saving the list order.&lt;br /&gt;Comments: ** Comment from web user: LuisRodrigues ** &lt;p&gt;This is an example of the bug&lt;/p&gt;</description><author>LuisRodrigues</author><pubDate>Tue, 18 Dec 2012 19:17:30 GMT</pubDate><guid isPermaLink="false">Commented Issue: No data-listidx attribute on list items when using multiple lists [33582] 20121218071730P</guid></item><item><title>Created Issue: No data-listidx attribute on list items when using multiple lists [33582]</title><link>http://dragsort.codeplex.com/workitem/33582</link><description>When using more than one list in the selector, with or without dragBetween set to true, data-listidx will be assigned to the UL elements used in the selector and not the child LI elements, leaving no way of saving the list order.&lt;br /&gt;</description><author>LuisRodrigues</author><pubDate>Tue, 18 Dec 2012 19:08:42 GMT</pubDate><guid isPermaLink="false">Created Issue: No data-listidx attribute on list items when using multiple lists [33582] 20121218070842P</guid></item><item><title>Commented Issue: Only trigger dragEnd when order has changed [27382]</title><link>http://dragsort.codeplex.com/workitem/27382</link><description>&amp;#60;p&amp;#62;P&amp;#58;S. Is here a way to send request to server only when some items really reordered, not by click only on item &amp;#63;&amp;#60;&amp;#47;p&amp;#62;&lt;br /&gt;&lt;br /&gt;Comments: ** Comment from web user: llorca ** &lt;p&gt;Hi how can I dragsort stop and start? Or disable and enable? &lt;br&gt;In other function.&lt;/p&gt;&lt;p&gt;Because I want to use with together Uploadify.&lt;/p&gt;&lt;p&gt;Photo instantly uploading I want to stop or disable dragsort.&lt;br&gt;Thank you.&lt;/p&gt;</description><author>llorca</author><pubDate>Fri, 14 Dec 2012 06:44:25 GMT</pubDate><guid isPermaLink="false">Commented Issue: Only trigger dragEnd when order has changed [27382] 20121214064425A</guid></item><item><title>Commented Issue: dragsort won't initialize if all lists are empty [33484]</title><link>http://dragsort.codeplex.com/workitem/33484</link><description>I have 3 lists, initially empty, filled dynamically later.&lt;br /&gt;If I call &amp;#36;&amp;#40;list&amp;#41;.dragsort&amp;#40;&amp;#123; dragSelector&amp;#58; &amp;#39;.item&amp;#39; &amp;#125;&amp;#41; when they are empty, nothing happens.&lt;br /&gt;However, if at least one of the is nonempty, all of them get initialized.&lt;br /&gt;&lt;br /&gt;This is clearly a bug, either it should initialize either way &amp;#40;preferred&amp;#41; or only for nonempty lists.&lt;br /&gt;Happens in current firefox &amp;#38;amp&amp;#59; chrome, not tested elsewhere.&lt;br /&gt;&lt;br /&gt;For the, the workaround of creating the lists with a placeholder item, initializing and then deleting the item works.&lt;br /&gt;Comments: ** Comment from web user: himdel ** &lt;p&gt;Additional info:&lt;/p&gt;&lt;p&gt;I can actually make it intialize almost fine using&lt;br&gt;$('.orderselect').dragsort({ itemSelector: '.option', dragSelector: '.option', placeHolderTemplate: '&amp;lt;div&amp;gt;&amp;lt;/div&amp;gt;' })&lt;/p&gt;&lt;p&gt;But then, dropping doesn't work - the item returns where it was.&lt;/p&gt;&lt;p&gt;If I add&lt;br&gt;$('.orderselect').dragsort({ itemSelector: '.option', dragSelector: '.option', placeHolderTemplate: '&amp;lt;div class=&amp;quot;option&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;' })&lt;br&gt;it works, but weird - an empty option appears while dragging, which I don't want.&lt;br&gt;&lt;/p&gt;</description><author>himdel</author><pubDate>Tue, 27 Nov 2012 21:18:43 GMT</pubDate><guid isPermaLink="false">Commented Issue: dragsort won't initialize if all lists are empty [33484] 20121127091843P</guid></item><item><title>Created Issue: dragsort won't initialize if all lists are empty [33484]</title><link>http://dragsort.codeplex.com/workitem/33484</link><description>I have 3 lists, initially empty, filled dynamically later.&lt;br /&gt;If I call &amp;#36;&amp;#40;list&amp;#41;.dragsort&amp;#40;&amp;#123; dragSelector&amp;#58; &amp;#39;.item&amp;#39; &amp;#125;&amp;#41; when they are empty, nothing happens.&lt;br /&gt;However, if at least one of the is nonempty, all of them get initialized.&lt;br /&gt;&lt;br /&gt;This is clearly a bug, either it should initialize either way &amp;#40;preferred&amp;#41; or only for nonempty lists.&lt;br /&gt;Happens in current firefox &amp;#38;amp&amp;#59; chrome, not tested elsewhere.&lt;br /&gt;&lt;br /&gt;For the, the workaround of creating the lists with a placeholder item, initializing and then deleting the item works.&lt;br /&gt;</description><author>himdel</author><pubDate>Tue, 27 Nov 2012 21:10:41 GMT</pubDate><guid isPermaLink="false">Created Issue: dragsort won't initialize if all lists are empty [33484] 20121127091041P</guid></item><item><title>Created Issue: scrollContainer loses correct item offsets when dragging [33163]</title><link>http://dragsort.codeplex.com/workitem/33163</link><description>Hi, I believe that I have found a problem with the scrolling code.&lt;br /&gt;&lt;br /&gt;For example, use this url on my development box&amp;#58; http&amp;#58;&amp;#47;&amp;#47;slideshowmaker.ath.cx&amp;#47;index.htm &amp;#58; &lt;br /&gt;&lt;br /&gt;If you drag one of the first few slides past the area so that the slider pane scrolls, then you grab one of the last items and try to move it left, you will see that the &amp;#34;selected&amp;#34; item gets drawn many pixels left of where the mouse really is.  It seems to lose track of the correct offset because its not taking into account the scrollContainer&amp;#39;s scolled position.&lt;br /&gt;&lt;br /&gt;I figured the scrollContainer&amp;#39;s selector should be &amp;#39;.slides-wrapper .slider-pane&amp;#39; if I understood the docs but seems &amp;#39;.slider-pane .slider-timeline&amp;#39; works better &amp;#40;actually will scroll&amp;#41;.&lt;br /&gt;&lt;br /&gt;Or am I missing something&amp;#63;&lt;br /&gt;&lt;br /&gt;Thanks&lt;br /&gt;</description><author>zachrybaker</author><pubDate>Mon, 24 Sep 2012 21:59:38 GMT</pubDate><guid isPermaLink="false">Created Issue: scrollContainer loses correct item offsets when dragging [33163] 20120924095938P</guid></item><item><title>Created Issue: Add Tolerance to trigger to avoid missing click [32717]</title><link>http://dragsort.codeplex.com/workitem/32717</link><description>Similar to patch&amp;#58; 12014 - &amp;#42;BUT&amp;#42; with some additional changes &amp;#40;see attached diff&amp;#41; and without allowing configuration of tolerance &amp;#40;I prefer allowing configuration&amp;#41;&lt;br /&gt;&lt;br /&gt;I don&amp;#39;t know if this fixes all of the issues with the above mentioned patch, but simply adding tolerance will cause some behavior problems. &lt;br /&gt;&lt;br /&gt;This diff also tracks&amp;#58;&lt;br /&gt;1. currentTarget - the target over which the drag started.  This avoids the drift problem introduced by adding tolerance due to the current code relying on &amp;#39;&amp;#36;&amp;#40;e.target&amp;#41;.closest&amp;#39;.&lt;br /&gt;&lt;br /&gt;2. startX &amp;#38; startY - stores and calculates the distance the mouse has moved and only triggers drag start when the tolerance has been exceeded.&lt;br /&gt;&lt;br /&gt;3. dragStart - modified to use currentTarget rather than closest target to avoid the drift issue.&lt;br /&gt;&lt;br /&gt;I don&amp;#39;t know if this diff fixes all remaining issues, but these were the ones I had encountered during my testing.&lt;br /&gt;</description><author>davidcl64</author><pubDate>Tue, 15 May 2012 15:56:55 GMT</pubDate><guid isPermaLink="false">Created Issue: Add Tolerance to trigger to avoid missing click [32717] 20120515035655P</guid></item></channel></rss>