John Levon wrote:
OK, so we're not calling speller_-close() when the window is closed or
Close is pressed - bad, we didn't write out the accepted word list.
dialogs call controller().stop() but this doesn't actually do anything
interesting. Angus, how can we make it so that it will call
On Sun, Feb 16, 2003 at 05:40:49PM +, Angus Leeming wrote:
I'd suggest doing nothing to this code for a while.
Too late ...
Attached is a NEW Dialog class that should make life a LOT easier.
Actually most of my problems were unrelated to the framework ...
can we leave this for a short
John Levon wrote:
>
> OK, so we're not calling speller_->close() when the window is closed or
> Close is pressed - bad, we didn't write out the accepted word list.
>
> dialogs call controller().stop() but this doesn't actually do anything
> interesting. Angus, how can we make it so that it
On Sun, Feb 16, 2003 at 05:40:49PM +, Angus Leeming wrote:
> I'd suggest doing nothing to this code for a while.
Too late ...
> Attached is a NEW Dialog class that should make life a LOT easier.
Actually most of my problems were unrelated to the framework ...
can we leave this for a short
OK, so we're not calling speller_-close() when the window is closed or
Close is pressed - bad, we didn't write out the accepted word list.
dialogs call controller().stop() but this doesn't actually do anything
interesting. Angus, how can we make it so that it will call -close()
but nothing else
OK, so we're not calling speller_->close() when the window is closed or
Close is pressed - bad, we didn't write out the accepted word list.
dialogs call controller().stop() but this doesn't actually do anything
interesting. Angus, how can we make it so that it will call ->close()
but nothing
