Bug 142883 - Can't associate macro with shortcut key
Summary: Can't associate macro with shortcut key
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.4.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-15 22:56 UTC by c-dorman
Modified: 2021-06-16 11:21 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description c-dorman 2021-06-15 22:56:00 UTC
Description:
I recorded a macro to change selected text's font and font size.  When I pull up the Main program for my macro in the Function box of the Customize panel, Load... doesn't associate the macro with the shortcut key.  Instead, a file-open panel opens,and seems to want me to find a cfg file for it to work with.

Actual Results:
Asks for cfg file

Expected Results:
Associate my macro with a shortcut key


Reproducible: Always


User Profile Reset: No



Additional Info:
.
Comment 1 [REDACTED] 2021-06-16 11:21:53 UTC
(In reply to c-dorman from comment #0)

> pull up the Main program for my macro in the Function box of the Customize
> panel, Load... doesn't associate the macro with the shortcut key.

Why do you click the "Load..." button?

When being in Tools -> Customize (LibreOffice Writer file opened) perform the following 

- Select your macro library in pane "Category" in the lower left side of the dialog (scroll down to "LibreOffice Macros")
- Under pane "Function" select your specific macro to be assigned to a shortcut
- Select the shortcut key to be assigned to the macro in the upper pane labeled "Shortcut Keys" 
- Click button "Modify" to perform the association (watch the shortcut appearing in pane labelled "Keys" at the right lower edge of the dialog).


PS: "Load..." button requires a file of containing shortcut definitions created by e.g "Save..."

From my perspective not a bug - please feel free to reopen if you don't agree.