On 6/28/11 7:14 AM, Jacek Kałucki wrote: > I noticed issue when searching large grids (more than 4k rows) > on Windows platform with the find dialogue (Ctrl+F). > If I start search from the beginning and final result > is located near the end, I receive system error > (it's not an exception so I can't mask it for user) when the search ends: > > 1158: Couldn't create a timer. > The current process has used all of its system allowance of handles for > Window Manager objects. > > It won't happen on *nix machines of course. > Positive is, that user can close notification window and application > performs well. > Any ideas how to avoid this, please?
The next thing to do would be to make a simple, wxPython-only implementation that shows the problem, and post to wxPython-users. Then again, Find is implemented in dGrid, not wx.grid.Grid. Could be something to do with our implementation. See lines 3119-3136 in dGrid. I see nothing wrong with the implementation by the way, but at least it's something to play with. You could print out system information in each iteration and try to narrow down what's eating up the handles. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
