-
Fabien Morin authored
- cartesianProduct is not needed : getCellKeyList can do the same thing in a better and cleaner way - if movements already exists, we don't want to take only the first one, but all movements are needed - improve error message to display the Line (title and relative_url) and the coordinates of the not found cell. This will make debugging much more easier - to set quantity on new created movements, we search on movement_list if movements contribute to the current movement applied on, but we need to look also on already processed movements (current_aggregated_amount_list) - the condition to check if the quantity of the current movement should be updated was wrong, fix it - in TradeCondition, now one loop turn is enought to make all calculation - change some variables names that where already used previously to avoid mistakes git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28024 20353a03-c40f-0410-a6d1-a30d3c3de9de
68860733