Issue 22788 - TEXTBOX insertTextContent() wrong in CALC
Summary: TEXTBOX insertTextContent() wrong in CALC
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Windows 2000
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2003-11-24 06:47 UTC by dfrench
Modified: 2013-02-24 21:07 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---

Writer doc with macro code that demos issue (7.52 KB, text/plain)
2003-11-24 06:50 UTC, dfrench
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description dfrench 2003-11-24 06:47:37 UTC
The behaviour of TEXTBOX is inconsistent between DRAW/IMPRESS , CALC and WRITER.
Fields inserted into the TEXT of TEXTBOX work as expected in DRAW and IMPRESS 
but insertTextContent() fails with "illegal argument exception" in WRITER and 
the field, although present, does not display correctly in TEXTBOX CALC 
(replaced by "?").

Originates at
Comment 1 dfrench 2003-11-24 06:50:26 UTC
Created attachment 11511 [details]
Writer doc with macro code that demos issue
Comment 2 ooo 2003-12-10 13:47:06 UTC
Fields have to be supported by the client of the edit engine.  Obviously this is 
not done by the Writer and Calc integration of the edit engine.  This really 
should be fixed set straight.

This issue is for Calc now, I'll create a new one for Writer.
Comment 3 ooo 2003-12-10 14:34:33 UTC
Comment 4 stefan.baltzer 2003-12-15 11:33:29 UTC
SBA: Reassigned to Stephan.
Comment 5 stephan.wunderlich 2003-12-15 12:29:03 UTC
SW: the api can't provide a functionality that isn't provided by the application
itself and in calc and writer it isn't possible to insert fields in textshapes.

SW->BH: This is a request for enhancement from my point of view and so yours to
take a look at.
Comment 6 dfrench 2003-12-15 19:13:24 UTC
It is possible to insert fields in textshapes in CALC as shown in the attached 
document ... the problem here is that CALC does not evaluate the field or 
display it correctly. I would class this as a DEFECT myself but I am more 
concerned that the problem is looked for in the right place ... in this case 
presentation rather than representation in the document.
Writer is different. It is not possible to insert fields in textshapes in 
WRITER because of the "illegal argument exception" . I suggest that this is 
also a defect if only because of the ugly way of rejecting the attempt. 
In principle, I would expect a TEXT object to look and behave the same in all 
Comment 7 stephan.wunderlich 2003-12-16 08:18:58 UTC
SW->dfrench: It only seams to be possible in Calc according to your attached
document. When you open a calc document via UI and insert a textshape without
the usage of the api, you'll see that it isn't possible to insert a field in
there. Same is valid for Writer, the insert-Fields submenu is greyed out when
you are inside a text shape. So the writer throws the right
IllegalArgumentException because the application isn't able to accept your
argument. One could discuss if Calc should throw the same exception instead of
silently accepting the wrong argument.
Comment 8 ace_dent 2008-05-16 02:57:46 UTC Issue Tracker - Feedback Request.

The Issue you raised has the status 'New' pending further action, but has not
been updated within the last 4 years. Please consider re-testing with one of the
latest versions of OOo, as the problem(s) may have already been addressed.
Either use the recent stable version:
or consider trying the new OOo 3 BETA (still in testing):
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
Many thanks,
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
Comment 9 bettina.haberer 2010-05-21 14:47:56 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".