Issue 117945 - Can't assign the 'OnOpening' action to a macro stored in the users spreadsheet
Summary: Can't assign the 'OnOpening' action to a macro stored in the users spreadsheet
Status: CLOSED DUPLICATE of issue 96997
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC All
: P3 Normal
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 16:12 UTC by gregmcc
Modified: 2018-07-17 10:01 UTC (History)
3 users (show)

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


Attachments
MacroSelector (92.30 KB, image/jpeg)
2011-04-27 16:12 UTC, gregmcc
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description gregmcc 2011-04-27 16:12:15 UTC
Created attachment 76453 [details]
MacroSelector 

This is happens on Vista32 and OSX.

Can't assign the 'OnOpening' action to a macro stored in the users spreadsheet - you are only provided with two selections not three :-
 - My Macros      ( stored in your version of OO3.4 Dev )
 - OpenOffice Macros

There should be a third :-
 - Save in File


Much easier to explain looking at the attachment.

[ The only way that I have the OpenDocument opening a macro contained within the spreadsheet - is because the original file has been copied from Excel originally ... ]


But this is proving difficult when I want to broadcast other files - and can't get the listeners working straight after opening the document.


Regards

GregMcC , Liverpool , UK
Comment 1 bmarcelly 2011-04-28 08:56:58 UTC
Duplicate of Issue 96997.
Work-around : use menu Tools > Customize > Events
Comment 2 Oliver-Rainer Wittmann 2012-06-13 12:24:11 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.
Comment 3 Marcus 2017-05-20 11:27:52 UTC
Reset assigne to the default "issues@openoffice.apache.org".
Comment 4 oooforum (fr) 2018-07-17 10:01:01 UTC
Already reported

*** This issue has been marked as a duplicate of issue 96997 ***