Good point, thanks! On May 4, 2010, at 1:15 PM, ext Thorbjørn Lindeijer wrote:
> On 05/04/2010 12:50 PM, ext Ivan De Marino wrote: >> I guess it's not really necessary. >> After all, "onReleased" depend on a previous "onPressed". >> So, if you want stuff to happen "onPressed" you can. If you want stuff >> to happen "onReleased" you use... whoever survived between "onReleased" >> and "onClicked". >> >> To me, sounds like the one to "kill" is "onReleased". >> But having a "MouseArea" that doesn't have a "onClicked" sounds weird... > > The main difference between Clicked and Released signals is as far as I > know whether you released while-on-the-area or not. If you pressed on a > mouse area, drag away from it, and then release, you should not get a > Clicked and only a Released event. > > So personally I don't see how you can get rid of the Released event, > since you wouldn't be able to respond to all releases anymore (only the > kinds that are Clicked). The Clicked event is the optional one, but it > provides convenience for a very common scenario (that of a push button) > so I'd consider it unhelpful to remove it. > > Regards, > Bjørn > > -- > Thorbjørn Lindeijer > Software Engineer > Nokia, Qt Development Frameworks > _______________________________________________ > Qt-qml mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-qml -- Henrik Hartz, Senior Qt Product Manager Qt Development, Nokia _______________________________________________ Qt-qml mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-qml
