On Wed, May 05, 2004 at 11:17:05AM +0100, Angus Leeming wrote:
> No, I admit I hadn't thought of that. However, there are no timers
> connected to QRefDialogBase::refsLB, referenceED are there?
Well, there's all sorts of internal fun. But if we're works we're
probably* OK
regards
john
On Wednesday 05 May 2004 10:57 am, John Levon wrote:
> On Wed, May 05, 2004 at 08:56:53AM +0100, Angus Leeming wrote:
> > Emitted signals disappear into hyperspace if signals are blocked.
> > Note
>
> Are you positive this won't cause problems elsewhere? (timers etc.)
No, I admit I hadn't thought
On Wed, May 05, 2004 at 08:56:53AM +0100, Angus Leeming wrote:
> Emitted signals disappear into hyperspace if signals are blocked. Note
Are you positive this won't cause problems elsewhere? (timers etc.)
regards
john
John Levon wrote:
> On Tue, May 04, 2004 at 10:40:54PM +0100, Angus Leeming wrote:
>
>> Thanks, John. So what's the recommended strategy to address this?
>
> Manually save and restore the dialog state is the only one I can
> think of
Thanks, John. However, I googled for "Qt prevent signals" and
On Tue, May 04, 2004 at 10:40:54PM +0100, Angus Leeming wrote:
> Thanks, John. So what's the recommended strategy to address this?
Manually save and restore the dialog state is the only one I can think
of
john
On Tue, May 04, 2004 at 10:30:37PM +0100, Angus Leeming wrote:
> Can someone clued up in Qt ascertain why interaction with the 'sort',
> 'update' or 'document' widgets invokes QRefDialog::changed_adaptor. I
> can see no reason at all, either in the .ui file or in the
> QRefDialog.C, QRef.C files.
On Tuesday 04 May 2004 10:38 pm, John Levon wrote:
> On Tue, May 04, 2004 at 10:30:37PM +0100, Angus Leeming wrote:
> > Can someone clued up in Qt ascertain why interaction with the
> > 'sort', 'update' or 'document' widgets invokes
> > QRefDialog::changed_adaptor. I can see no reason at all, eithe
