On Thu, Sep 19, 2013 at 01:02:01AM -0700, Josh Andler wrote:
Just a couple observations: 1) The English words chosen for the various fields in the UI are not very amateur (non-professional/non-educated) friendly. 2) The ability to hang Inkscape unintentionally if an image is not small enough (with no related warning) is disconcerting.
Threading would solve this.... are we thinking about switching to c++11?
seemed like a good reason to test it. It seems like it should operate with relatively similar speed, regardless of size, when you're just dealing with interpreting "blocks"
I am not sure that the underlying algorithm is actually O(n) for n pixels, we have been talking about that, but I feel that correctness is more valuable for completion than scaling. A cancelable progress bar and a note that this is slow with large images should solve this problem while we think of suitable optimisations.
njh