Hi Koen,
On 12.07.2012 15:45, Koen Deforche wrote:
> Hey Stefan,
>
> 2012/7/12 Stefan Ruppert<[email protected]>:
>> I get the following decodeSignal() error everytime a popup menu is open and
>> I click on a tab of a WTabWidget. See the attached screenshot section.
>>
>> "[error] "Wt: decodeSignal(): signal 's4b' not exposed"
>>
>> Each tab seems to have its own signal: 's4b', 's4c', etc...
>
> With what version of Wt is this? This behaviour has changed somewhat lately.
>
> In older versions of Wt, when a popup is open, it blocks signals to
> other widgets (pretty much like a modal dialog does). With the latest
> release of Wt this should no longer be the case.
I use the stable Wt 3.2.1. Does this mean it was changed between 3.2.1
and the upcoming 3.2.2?
>> Also I have a WTabWidget which has no widgets attached (myTab->addTab(0,
>> WString::tr("details-text"));). But I use the currentChanged() signal to get
>> an event when the user has selected a new tab and change something
>> internally. Within this widget the current tab is changed even a popup menu
>> is open and closed by the click. This does not happen if a WTabWidget has a
>> widget attached.
>
> This kind of inconsistent behavior sounds like a bug, but I have no
> idea of what causes it.
>
> If you could isolate it in a small test case, I'll have a look at it.
I'll try to create a test case next week.
Regards,
Stefan
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
