Project

General

Profile

Actions

Bug #1028

closed

Signal is not emitted after reenabling widget

Added by dima s over 12 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
10/18/2011
Due date:
% Done:

0%

Estimated time:

Description

Hi,

If I connect signal to widget and then disable and enable this widget the connected signal stops emitting. Included test example.

Regards,

dima


Files

testsignal.cc (1.09 KB) testsignal.cc Test example dima s, 10/18/2011 01:30 PM
hello.C (1.1 KB) hello.C Pieter Libin, 10/31/2011 04:40 PM
Actions #1

Updated by Koen Deforche over 12 years ago

  • Status changed from New to InProgress
  • Assignee set to Pieter Libin
  • Target version set to 3.2.0
Actions #2

Updated by Pieter Libin over 12 years ago

Hi,

I was not able to reproduce this problem with neither the 3.1.11 release nor the current master.

I added a label the the checkboxes (see attachment) to make it easier to explain the steps I executed.

The scenario:

click inner checkbox: the button is disabled

click outer checkbox: the inner checkbox is disabled

click outer checkbox: the inner checkbox is enabled

click inner checkbox : the button is enabled

If I understand correctly, the last step does not enable the button in your case?

Can you let me know that I understand the problem correctly,

and if so, which version of wt and which browser you are using?

Kind regards,

Pieter

Actions #3

Updated by Pieter Libin over 12 years ago

  • Status changed from InProgress to Feedback
Actions #4

Updated by dima s over 12 years ago

Hi,

Yes, you understand correctly. I've rechecked this issue and it has appeared to happen only in IE 8, though I was sure other browsers were also touched. So, this is the case with wt 3.1.11 and IE 8.

Regards,

dima

Actions #5

Updated by Pieter Libin over 12 years ago

  • Assignee changed from Pieter Libin to Koen Deforche

Hey Koen,

it seems that the WCheckBox's clicked signal is not working at all on IE8.

Pieter

Actions #6

Updated by Koen Deforche over 12 years ago

Hey,

I can only reproduce this with progressive bootstrap mode. That's correct ?

(That's still a bug, but I want to make sure I am reproducing what you see)

Regards,

koen

Actions #7

Updated by dima s over 12 years ago

Hi,

Can you explain please what means "progressive bootstrap mode" ? I can reproduce this always.

Regards,

dima

Actions #8

Updated by Koen Deforche over 12 years ago

Hey Dima,

This is a configuration option in the wt_config.xml file. If you don't know it then for you probably have not enabled it. It is off by default.

That means that I am not able to replicate your problem though.

The next thing I will try is to reproduce the problem with Wt 3.1.11 instead of the git head. If you like (and it would help) could you also check with the latest git version ?

Regards,

koen

Actions #9

Updated by dima s over 12 years ago

Hey Koen,

I don't use wt_confix.xml in test example. I checked latest git version - the problem is still reproducible in Internet Explorer 8.

Regards,

dima

Actions #10

Updated by Koen Deforche over 12 years ago

  • Status changed from Feedback to InProgress

Hey,

Okay, we could reproduce this now. Sorry for the confusion. The bug is intriguing though. Another mystery bug in IE, but this one seems hard to work around...

Regards,

koen

Actions #11

Updated by Koen Deforche over 12 years ago

  • Target version changed from 3.2.0 to 3.2.1
Actions #12

Updated by Koen Deforche about 12 years ago

  • Status changed from InProgress to Resolved
Actions #13

Updated by Koen Deforche about 12 years ago

  • Status changed from Resolved to Closed

Fixed in 3.2.1

Actions

Also available in: Atom PDF