Thanks everybody for yours answers.<br><br>It is clearer and I am in fact agree with you and trolltech.<br><br>I suppose that to draw a button is not much more cpu time consuming against a label ?<br><br>Simon<br><br><div>
<span class="gmail_quote">2007/1/31, Giovanni Bajo <<a href="mailto:rasky@develer.com">rasky@develer.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 1/31/2007 11:06 AM, Simon stokes wrote:<br><br>> I have a gridlayout of QLabels. What it the signal to use in this<br>> context to change, for example, the text from the QLabel I have<br>> **clicked** ?<br><br>
*All* widgets receive *events* from mouse clicks, which can be handled<br>by subclassing and overriding the event function, or by installing an<br>event handler.<br><br>Some widgets, by default, handle events by emitting corresponding
<br>signals. This is done for widgets where the specific events need *often*<br>to be handled (eg: a click for a button), so that the user can customize<br>the behaviour by connecting a slot.<br><br>In you case, Trolltech decided that QLabel usually don't need click to
<br>be handled, so they didn't provide a standard event handler which emits<br>a standard signal for it. But you can do it yourself, in your own<br>QClickableLabel, though.<br>--<br>Giovanni Bajo<br></blockquote></div>
<br>