Re: Issues with setupMatchSession/matchSessionComplete in RunnerManager

2009-07-30 Thread Ryan P. Bitanga
On Thu, Jul 30, 2009 at 11:29 PM, Ryan P. Bitanga wrote: > On Thu, Jul 30, 2009 at 9:28 AM, Aaron J. Seigo wrote: >> On Wednesday 29 July 2009, Ryan P. Bitanga wrote: >>> On Thu, Jul 30, 2009 at 2:04 AM, Aaron J. Seigo wrote: >>> > On Wednesday 29 July 2009, Ryan P. Bitanga wrote: >>> >> On Thu, Ju

Re: Issues with setupMatchSession/matchSessionComplete in RunnerManager

2009-07-30 Thread Ryan P. Bitanga
On Thu, Jul 30, 2009 at 9:28 AM, Aaron J. Seigo wrote: > On Wednesday 29 July 2009, Ryan P. Bitanga wrote: >> On Thu, Jul 30, 2009 at 2:04 AM, Aaron J. Seigo wrote: >> > On Wednesday 29 July 2009, Ryan P. Bitanga wrote: >> >> On Thu, Jul 30, 2009 at 12:43 AM, Aaron J. Seigo wrote: >> >> > On Wednes

Re: Issues with setupMatchSession/matchSessionComplete in RunnerManager

2009-07-29 Thread Aaron J. Seigo
On Wednesday 29 July 2009, Ryan P. Bitanga wrote: > On Thu, Jul 30, 2009 at 2:04 AM, Aaron J. Seigo wrote: > > On Wednesday 29 July 2009, Ryan P. Bitanga wrote: > >> On Thu, Jul 30, 2009 at 12:43 AM, Aaron J. Seigo wrote: > >> > On Wednesday 29 July 2009, Ryan P. Bitanga wrote: > >> > >> so I think

Re: Issues with setupMatchSession/matchSessionComplete in RunnerManager

2009-07-29 Thread Ryan P. Bitanga
On Thu, Jul 30, 2009 at 2:04 AM, Aaron J. Seigo wrote: > On Wednesday 29 July 2009, Ryan P. Bitanga wrote: >> On Thu, Jul 30, 2009 at 12:43 AM, Aaron J. Seigo wrote: >> > On Wednesday 29 July 2009, Ryan P. Bitanga wrote: >> so I think the best place to do this would be in >> the destructor of FindM

Re: Issues with setupMatchSession/matchSessionComplete in RunnerManager

2009-07-29 Thread Aaron J. Seigo
On Wednesday 29 July 2009, Ryan P. Bitanga wrote: > On Thu, Jul 30, 2009 at 12:43 AM, Aaron J. Seigo wrote: > > On Wednesday 29 July 2009, Ryan P. Bitanga wrote: > >> Because we can launch a new query while jobs for an existing query are > >> still executing, any slots that are connected to prepare

Re: Issues with setupMatchSession/matchSessionComplete in RunnerManager

2009-07-29 Thread Ryan P. Bitanga
On Thu, Jul 30, 2009 at 12:43 AM, Aaron J. Seigo wrote: > On Wednesday 29 July 2009, Ryan P. Bitanga wrote: >> Because we can launch a new query while jobs for an existing query are >> still executing, any slots that are connected to prepare and teardown >> have to be threadsafe. > > setup and tead

Re: Issues with setupMatchSession/matchSessionComplete in RunnerManager

2009-07-29 Thread Aaron J. Seigo
On Wednesday 29 July 2009, Ryan P. Bitanga wrote: > Because we can launch a new query while jobs for an existing query are > still executing, any slots that are connected to prepare and teardown > have to be threadsafe. setup and teadrown should be called and executed from the main thread. queries

Re: Issues with setupMatchSession/matchSessionComplete in RunnerManager

2009-07-29 Thread Ryan P. Bitanga
On Wed, Jul 29, 2009 at 7:17 PM, Martin Gräßlin wrote: > Am Mittwoch 29 Juli 2009 12:53:56 schrieb Ryan P. Bitanga: >> Another issue is that teardown is currently only emitted when the >> dialog is hidden. I think the assumption was that there would be a one >> to one correspondence between emissi

Re: Issues with setupMatchSession/matchSessionComplete in RunnerManager

2009-07-29 Thread Martin Gräßlin
Am Mittwoch 29 Juli 2009 12:53:56 schrieb Ryan P. Bitanga: > Hi all, > > I should have thought of this sooner, but upon taking a closer look at > the code, I just realized that we have a few issues with the whole > setup/teardown scenario. > > Because we can launch a new query while jobs for an exi