Julien Galand wrote:
[...]
Hi Mathias,
I have followed your advice. Doing so enabled me to investigate further,
and I have concluded that there is definitely an alignment weakness in
the UNO C++ headers.
The point is that I compile my add-on with alignment 2. I thought there
would be no
Hi Julien,
Julien Galand wrote:
As a conclusion :
- Either compile a C++ UNO component with the alignment compiler option
set to 8 (or at least all SDK/UNO headers).
- Or the Reference template structure definition should be wrapped
with #pragma align(8).
But the latter option is a fix
Julien Galand wrote:
// BUG (of binding ?) : Use KeyEvent.KeyChar, and not KeyEvent.KeyCode
!!
//
// Note:
// The same bug appears when retrieving a KeyEvent, such as
// XAcceleratorConfiguration.getKeyEventsByCommand(.uno:AddDirect).
// = the returned KeyEvents have KeyChar filled by
Le 20 oct. 06, à 10:54, Mathias Bauer a écrit :
Julien Galand wrote:
// BUG (of binding ?) : Use KeyEvent.KeyChar, and not KeyEvent.KeyCode
!!
//
// Note:
// The same bug appears when retrieving a KeyEvent, such as
// XAcceleratorConfiguration.getKeyEventsByCommand(.uno:AddDirect).
// = the
Julien Galand wrote:
Hi,
Maybe this mail isn't appropriate in this mailing list (then tell me).
As far as I have understood, there seems to be a bug in the C++ UNO
binding of the awt::KeyEvent structure.
When using the following code snippet to set keyboard shortcuts
programmatically by the
Le 19 oct. 06, à 14:00, Stephan Bergmann a écrit :
I very much doubt that this is directly a problem of the UNO C++
language binding. com.sun.star.awt.KeyEvent is a UNO struct that has
members KeyChar and KeyCode. Maybe you can post the failing C++ code
here (if it is not too long) and
