https://bugs.documentfoundation.org/show_bug.cgi?id=172899

--- Comment #14 from MartinPC <[email protected]> ---
Created attachment 208129
  --> https://bugs.documentfoundation.org/attachment.cgi?id=208129&action=edit
REVISED Workaround Macros for LibreOffice Writer Soft Hyphen Display Bug

This is an indivisible block of LibreOffice BASIC code that contains two
REVISED macros: 

• SoftHyphensOn() turns the display of "inactivated/​dormant" soft/​conditional
hyphens ON.

• SoftHyphensOff() turns them OFF.

They save users from having to manually navigate to Tools > Options >
LibreOffice Writer > Formatting Aids > Soft hyphens in order to toggle the
display of "dormant" soft/​conditional hyphens there. 

The ENTIRE block of code must be pasted into a BASIC macro module for the
macros to work. If this revised block is replacing an original block, the
ENTIRE REVISED BLOCK must be pasted over the ENTIRE ORIGINAL BLOCK. (And then
the macro module must be saved.)

Only the SoftHyphensOn() and SoftHyphensOff() macros should be directly invoked
by users. Other subroutines in the code block that APPEAR as macro listings in
the macro editor are actually helper code that is used by the SoftHyphensOn()
and SoftHyphensOff() macros.

These two macros are most conveniently used by adding them to a toolbar button
next to the "Toggle Formatting Marks" button (¶), where the new buttons should
probably be renamed something like "-ON" and "-OFF" for the sake of
compactness.

These REVISED macros no longer generate status messages in LibreOffice Writer's
statusbar ("Soft Hyphens: ON" and "Soft Hyphens: OFF"). In the original macros,
those messages blocked or interfered with the display of OTHER useful status
information. If you're unsure of whether soft hyphens are ON or OFF, just click
on the toolbar button that sets them the way you want them to be any time
you're unsure. Clicking on the same button multiple times without going back
and forth between ON and OFF won't break anything.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to