Sorry, I made a mistake. In docs it is written that 'move_after' function can't work with sorted stores, but nothing is written about 'insert_after' (with swap function it is correct – it works only with unsorted stores).
I came up with some solution. It seems to be impossible to return to unsorted state (without reloading) so I created default sorting (which in fact doesn't sort). This solved the situation with 'insert_after' function, but 'swap' still didn't work (sorting is not disabled – it is just set to default state). Therefore I changed rows manually by changing their values. My solution is in patch (compared to rev. 814) – it seems to work, though there may be better ways to solve this.
Sorry, I made a mistake. In docs it is written that 'move_after' function can't work with sorted stores, but nothing is written about 'insert_after' (with swap function it is correct – it works only with unsorted stores).
I came up with some solution. It seems to be impossible to return to unsorted state (without reloading) so I created default sorting (which in fact doesn't sort). This solved the situation with 'insert_after' function, but 'swap' still didn't work (sorting is not disabled – it is just set to default state). Therefore I changed rows manually by changing their values. My solution is in patch (compared to rev. 814) – it seems to work, though there may be better ways to solve this.