You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by SET <ao...@nmset.info.INVALID> on 2024/01/07 13:26:35 UTC

Keyboard mappings to macros became unavailable when AOO is started from C++

Hi,

This issue is observed on Linux in 4.1.15 and 4.5.0. It is not observed in 
4.1.7.

A C++ application starts AOO using bootstrap() and text documents are created 
from *.ott templates containing basic macros. Some macros have bindings to 
keyboard combinations, all defined in the UI.

In 4.1.7, the keyboard bindings work as expected in unsaved new documents.

In 4.1.15 and 4.5.0, the macros are not called by the keyboard shortcuts when 
a new file is generated from a template. Executing the macros directly using 
the UI dialogs succeeds.

The bindings will work in 2 circumstances:

 - the newly generated document is saved and reloaded via the File menu,
 - the newly generated document is saved, closed and opened again.
 
If AOO is started from bash, without being started by the controlling 
application, the bindings just work.

Thank you for any input, help and eventual resolution.

Regards.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Re: Keyboard mappings to macros became unavailable when AOO is started from C++

Posted by Matthias Seidel <ma...@hamburg.de>.
Hi and welcome,

Am 07.01.24 um 14:26 schrieb SET:
> Hi,
>
> This issue is observed on Linux in 4.1.15 and 4.5.0. It is not observed in
> 4.1.7.
>
> A C++ application starts AOO using bootstrap() and text documents are created
> from *.ott templates containing basic macros. Some macros have bindings to
> keyboard combinations, all defined in the UI.
>
> In 4.1.7, the keyboard bindings work as expected in unsaved new documents.
>
> In 4.1.15 and 4.5.0, the macros are not called by the keyboard shortcuts when
> a new file is generated from a template. Executing the macros directly using
> the UI dialogs succeeds.
>
> The bindings will work in 2 circumstances:
>
>   - the newly generated document is saved and reloaded via the File menu,
>   - the newly generated document is saved, closed and opened again.
>   
> If AOO is started from bash, without being started by the controlling
> application, the bindings just work.
>
> Thank you for any input, help and eventual resolution.

@All:

This refers to a Bugzilla issue:

https://bz.apache.org/ooo/show_bug.cgi?id=128582

It seems to occur since AOO 4.1.12. Any idea what we changed in that 
version?

Regards,

    Matthias

>
> Regards.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>

Re: Keyboard mappings to macros became unavailable when AOO is started from C++

Posted by SET <ao...@nmset.info.INVALID>.
Hi,

After reverting fb9ad7aa175, basic macros are callable by keyboard shortcuts when AOO 
4.5.0 is started with ::cppu::bootstrap().

I made a diff bdb20b2a64..60e0a1c111 where I suspected fb9ad7aa175. bdb20b2a64 is 
the commit displayed in the 'About' dialog of 4.1.11 from your website, and 60e0a1c111 
got 4.1.12.

To recapitulate the many situation:

 A. Any version started with the 'soffice' script on Arch Linux
    No unexpected behaviour when macros are called by keyboard shortcuts in all 
situations.

 B. 4.1.11 started by ::cppu::bootstrap()
    No unexpected behaviour in all situations.

 C. 4.1.12 to 4.5.0 started by ::cppu::bootstrap() with fb9ad7aa175 applied
    Macros are not callable by keyboard shortcuts on a new unsaved text document; they 
are callable by keyboard shortcuts after loading a saved document from storage.

 D. 4.5.0 started by ::cppu::bootstrap() with fb9ad7aa175 *reverted*
    No unexpected behaviour when macros are called by keyboard shortcuts in all 
situations.
    
I mentioned templates in the OP because it's my workflow. In fact the problem occurs 
without templates also, please see comment #9.

Ref: https://bz.apache.org/ooo/show_bug.cgi?id=128582[1]

Thank you.

--------
[1] https://bz.apache.org/ooo/show_bug.cgi?id=128582