[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    dbusmenuqt and left-click
From:       Andriy Rysin <arysin () gmail ! com>
Date:       2010-08-04 22:33:03
Message-ID: AANLkTikO6DM_nxYvgwqBNk7Ncgw8ekfa4wvHbb4rSFNZ () mail ! gmail ! com
[Download RAW message or body]

In keyboard layout indicator module I have a reaction to left-click via
activateRequested(), which is to toggle the layout to the next one (as
opposed to right-click which brings menu). Though currently (with latest
dbusmenuqt) no matter whether I click left or right button it's always
context menu that appears.

Is this a bug or something else is needed to make activateRequested() work?

Thanks,
Andriy

    /**
     * Inform the host application that an activation has been requested,
     *           for instance left mouse click, but this is not guaranteed
since
     *           it's dependent from the visualization
     * @param active if it's true the application asked for the activatin
     *              of the main window, if it's false it asked for hiding
     * @param pos the position in the screen where the user clicked to
     *  trigger this signal, QPoint() if it's not the consequence of a mouse
click.
     */
    void activateRequested(bool active, const QPoint &pos);

[Attachment #3 (text/html)]

In keyboard layout indicator module I have a reaction to left-click via act=
ivateRequested(), which is to toggle the layout to the next one (as opposed=
 to right-click which brings menu). Though currently (with latest dbusmenuq=
t) no matter whether I click left or right button it&#39;s always context m=
enu that appears.<br>
<br>Is this a bug or something else is needed to make activateRequested() w=
ork?<br><br>Thanks,<br>Andriy<br><br>=A0=A0=A0 /**<br>=A0=A0=A0=A0 * Inform=
 the host application that an activation has been requested,<br>=A0=A0=A0=
=A0 *=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 for instance left mouse click, but this=
 is not guaranteed since<br>
=A0=A0=A0=A0 *=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 it&#39;s dependent from the vi=
sualization<br>=A0=A0=A0=A0 * @param active if it&#39;s true the applicatio=
n asked for the activatin<br>=A0=A0=A0=A0 *=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 of the main window, if it&#39;s false it asked for hiding<br>
=A0=A0=A0=A0 * @param pos the position in the screen where the user clicked=
 to<br>=A0=A0=A0=A0 *=A0 trigger this signal, QPoint() if it&#39;s not the =
consequence of a mouse click.<br>=A0=A0=A0=A0 */<br>=A0=A0=A0 void activate=
Requested(bool active, const QPoint &amp;pos);<br>
<br>


[prev in list] [next in list] [prev in thread] [next in thread]