Issue 114184 - Grey out the text on macro buttons when the macros are disabled.
Summary: Grey out the text on macro buttons when the macros are disabled.
Status: UNCONFIRMED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-29 19:52 UTC by gregmcc
Modified: 2017-05-20 11:27 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description gregmcc 2010-08-29 19:52:40 UTC 
Hi,

A very helpful enhancement would be to 'Grey out the text on macro buttons' 
when the macros were disabled.

If  a component opens another component then that second component's macros are 
disabled - which is confusing - you are clicking on macro buttons that have 
been disabled because of the way the component was opened. If the text on the 
macro buttons were greyed out - it would be obvious that the macros were not 
available.

Cheers

Greg McC
Liverpool
Comment 1 jsc 2010-10-04 10:07:51 UTC 
jsc -> fs: what's your opinion on this? In general i think it can be a useful
enhancement.
Comment 2 Frank Schönheit 2010-10-04 10:13:22 UTC 
There is no such thing as "macro buttons" - there are buttons which can have
macros associated with various of the events they fire, amongst others, the
"This button has been pressed" event.

This means that it is difficult to properly determine the situation where a
button must be disabled (aka "greyed out"). Finally, there might be even more
listeners reacting on the "button has been pressed" event that just the macro.

So, while it is possible to apply some heuristics to this, I am not convinced it
wouldn't lead to unwanted side effects.
Comment 3 Frank Schönheit 2010-10-04 10:14:04 UTC 
> If  a component opens another component then that second component's macros
> are disabled

which probably is a bug in the macro you use to open that other component :)
Comment 4 Marcus 2017-05-20 11:27:29 UTC 
Reset assigne to the default "issues@openoffice.apache.org".