Wt

Hey, a right button click is a special thing in a browser and can not reliably be caught (there are workarounds by catching 'contextmenu' but as the name says, that's suspiciously hacky).

But the mouseUp/mouseDown signals for headers in WAbstractItemView are indeed lacking and should be added.

Hey,

adding mouseUp/mouseDown will be enough, but the behaviour when connecting to this to signals has to be better explained in the reference.

For example if you have a simple WTable with two cell, let say cell_1 and cell_2 and connect their signals as following:

WTableCell *cell_1;
cell_1.maouseWentDown.connect(&setTempCellIndex);
cell_2.mouseWentUp.connect(&useTempCell_2);

So if you click on cell_1 and drag the mouse pointer and release it on the cell_2 than the useTempCell_2 is called as expected.

On the other hand when you connect the mouseWentUp of cell_1 as well, you never get the useTempCell_2 called under the same scenario:

WTableCell *cell_1;
cell_1.maouseWentDown.connect(&setTempCellIndex);
cell_1.mouseWentUp.connect(&useTempCell_1);
cell_2.mouseWentUp.connect(&useTempCell_2);

I cannot judge whether it is a bug or a feature but it has to be better documented at least.

Regards

Stoycho

On the other hand when you connect the mouseWentUp of cell_1 as well, you never get the useTempCell_2 called under the same scenario

For clarity, despite you release the mouse button over cell_2 the useTempCell_1 is called because the mouseWentDown and mouseWentWp of cell_1 are both connected, i.e., the gesture begins over cell_1 and despite it ends over cell_2 the slot connected to cell_1's mouseWentUp is called, but the cell_2's mouseWentUp is not.