Bug 45691 - Tools > Customize > Events: Assigned actions cannot be removed
Summary: Tools > Customize > Events: Assigned actions cannot be removed
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.4.4 release
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-06 04:22 UTC by Volker Lenhardt
Modified: 2015-01-06 10:36 UTC (History)
2 users (show)

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 Volker Lenhardt 2012-02-06 04:22:51 UTC
If I open the Tools|Customize dialog (in any component) and assign a macro action to an event, the action cannot be removed after the OK button has been clicked. 

That is, klicking on the remove button temporarily withdraws the string from the action column, but the action remains assigned, as one can see when reopening the customize dialog and/or evoking the event in question.

Even clicking on the reset button does not reestablish the original state with no actions assigned.

This was discovered when a macro was assigned to an inappropriate event and this was to be corrected. The only way to come out of this is to assign a macro that does nothing: changing the action is possible.

This behavior shows with LO 3.4.4.3 (openSUSE brand) under openSUSE 12.1 and with LO 3.4.5 (original) under Windows 7, both on Intel i5 64 Bit.

This behavior does not show with OOo 3.3.0 under Windows Vista and with OOo 3.2.1 (original) under openSUSE 12.1.
Comment 1 Jochen 2012-02-06 14:03:28 UTC
I can confirm the bug in LO 3.4.5 OOO340m1 (Build:502) (OS: Windows 7 Prof 64 bit).

I have tested the phenomen in LO 3.5.0 RC3 (OS: Windows XP). There is no problem. Does anyone know if the problem is in LO 3.5.x fixed?
Comment 2 jmys 2012-04-28 05:52:04 UTC
I can confirm the bug in LO 3.4.5 OOO340m1 (Build:502) (OS: Windows XP Prof 32
bit).

The same problem was partialy reported as well in:
https://bugs.freedesktop.org/show_bug.cgi?id=39449#c5
Comment 3 QA Administrators 2015-01-05 17:52:16 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

Thank you for your help!

-- The LibreOffice QA Team
Comment 4 Volker Lenhardt 2015-01-06 10:36:19 UTC
Seems resolved. Works for me now.

OS: openSUSE 13.2 (Harlequin) (x86_64)
LO: Version: 4.3.5.2.0+ Build-ID: 430m0(Build:2)