enthought/enaml — comment on commit 3a6d947d8dd305f8824972197e2dfd9392c9873b
File:  line 0
By sccolbert:

So I just tested that package from pypi on an application with 1000 push
buttons whose size and position depended on the size of the main window.

The time to re-solve the system on each resize event was ~7ms. The time for
painting the widgets was almost 3x that, so I would say that the solver is
fast enough (Qt painting, incidentally, was ~3x faster than wx).

I'll use this for now, but I still think there is a good reason to have our
own Cythonized port.

On Wed, Oct 19, 2011 at 2:58 PM, Chris Colbert wrote:

> yep, that was it.
>
>
> On Wed, Oct 19, 2011 at 2:45 PM, Robert Kern <
> reply@reply.github.com>wrote:
>
>> You mean the lines that look like this:
>>
>> failed 0x109e21e80
>> failed 0x109e22610
>>
>> If you look at the comment above where these are printed out (grep for
>> "failed" in `tests/Tests.cc`), he's just printing out when adding an
>> incompatible row, then continuing. I don't think it's a test failure.
>>
>> // Add the constraint -- if it's incompatible, just ignore it
>> try
>> {
>> solver.AddConstraint(rgpcns[j]);
>> }
>> catch (ExCLRequiredFailure &)
>> {
>> cout << "failed "<< rgpcns[j].ptr() << endl;
>>
>> --
>> Reply to this email directly or view it on GitHub:
>>
>> https://github.com/enthought/enaml/commit/3a6d947d8dd305f8824972197e2dfd9392c9873b#commitcomment-662228
>>
>
>