Issue 34722 - [macro] Macro recorder records cellmovements while entering formula
Summary: [macro] Macro recorder records cellmovements while entering formula
Status: CLOSED DUPLICATE of issue 9769
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: niklas.nebel
QA Contact: issues@sc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-28 12:18 UTC by rob_hughes
Modified: 2013-08-07 15:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
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 rob_hughes 2004-09-28 12:18:38 UTC 
open a new OO.o spreadsheet

start in A1

click Tools | Macros | Record Macro

move to C8

enter 1,2,3 in cells C8,C9,C10

move to C11

enter formula =SUM(now move up 1, hit shift to anchor, move up 2 more,
close paren)

hit return (C11 shows 6)

click Stop Recording

save the macro with a new name.

Now clear the data on the sheet, and run the new macro.

It puts the formula "=Sum(C8:C10)" belonging in cell C11 into cell C8, and
shows "Err:522" in C8.

C9 correctly contains 2.
C10 correctly contains 3.
C11 is blank
Comment 1 frank 2004-09-28 12:59:09 UTC 
Hi Joerg,

please have a look. Target 2 Ok ?

Frank
Comment 2 joerg.skottke 2004-09-28 13:17:37 UTC 
The problem is that the uno:GoUp events are recorded while the formula is
created. The Current cell is c8 then and this is where the formula is inserted.
This is indeed a problem, i believe the effort to fix this is significant.

Workaround: Enter the formula directly or edit the BASIC code afterwards.

According to the OOo PCDs i cannot do much more than to set this issue to "OOo
Later" as target, macros have no priority for the upcoming release and OOo 1.x. 
- reassign
- changed summary
Comment 3 niklas.nebel 2004-09-28 13:30:26 UTC 
See issue 17396 and issue 9769.

*** This issue has been marked as a duplicate of 9769 ***
Comment 4 niklas.nebel 2004-09-28 13:31:09 UTC 
closing duplicate.