Hi, see my comments below:
On 18.09.2012 16:14, Nagaev Boris wrote: > Hello! > > Additional argument can be added to setCurrentIndex, which would tell > it to emit changes, like WApplication::setInternalPath. Then I would prefer new methods like changeCurrentIndex() and changeCurrentText()! > On Tue, Sep 18, 2012 at 5:42 PM, Rob Van Dyck<rob.van.d...@gmail.com> wrote: >> Hi Stefan, >> >> I actually find this usefull: this way there is a difference between >> external data changes (user changed value) and internal changes (as >> in: setCurrentIndex). Ok, I understand. But from my use case I want to trigger calls to any connected slot. So for now I have to emulate this... Thus I would really like to see the above proposed new methods! :-) Regards, Stefan >> On Tue, Sep 18, 2012 at 2:15 PM, Stefan Ruppert<s...@myarm.com> wrote: >>> Hi all, >>> >>> currently no signal is emitted when the WComboBox current index changes >>> due to a setCurrentIndex() or setValueText() call. From my point of view >>> it should emit those signals! Any reasons against this? >>> >>> 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 witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
