On Fri, Oct 23, 2015 at 1:42 AM, deDietrich Gabriel < gabriel.dedietr...@theqtcompany.com> wrote:
> Hi Adam, > > > Can you post your example? We could have a look at it here as well and see > if our measurements are consistent. > > > I don't have a simple example at the moment. I discovered this when opening a 650MB file sent to us by a customer using our application. It currently takes about 13 minutes to open the file (using the current shipping version of our application that does not use Qt takes about 1.5 minutes to load the file), and in the process of profiling the load, I saw what appears to be a lot of time spent in QAccessibleEvent::uniqueId(). It's likely that I could put something simpler together using our application, and I could make the compiled version of that available for testing and profiling, but not the source. Coming up with a self contained example would probably take a fair amount of time. That's why I was hoping there was a simple killswitch for accessibility so I could at least make sure that I'm on the right track here. We're building our own Qt libraries (with relatively standard configuration flags and only a few patches to Qt code that have nothing to do with accessibility). Is there a configure option I can use to remove accessibility in the libraries altogether? Adam
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
