Issue 77047 - RPT: inputting and editing text in report may confuse
Summary: RPT: inputting and editing text in report may confuse
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: recent-trunk
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2007-05-07 16:55 UTC by christoph.lukasiak
Modified: 2013-02-07 22:40 UTC (History)
1 user (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description christoph.lukasiak 2007-05-07 16:55:19 UTC
0. open a new database
1. create a table with any field
2. open the report designer and bind it to the table
3. create a 'textbox'

-> you cannot insert any text, because it is a 'formatted field' 

=> you have to take a 'label field' instead and change the property content of
the property 'label', which is a listbox in the control property browser (pretty
hidden) - the formatting of the inputted custom text is also confusing and
limited, a more direct method of inputting and editing text in report would be nice
Comment 1 christoph.lukasiak 2007-05-07 16:57:30 UTC
add keyword new_implementation
Comment 2 Frank Schönheit 2007-05-15 09:57:05 UTC
The Report Designer iTeam decided that this is no show stopper for the first
release, and no "should be fixed if possible at all". targeting to "not
determined" for the moment.
Comment 3 Frank Schönheit 2007-07-03 09:16:42 UTC
reset target
Comment 4 marc.neumann 2007-09-10 13:25:42 UTC
The Report Designer iTeam decided to retargeting this issue to 2.4.
Comment 5 bettina.haberer 2007-11-05 15:59:41 UTC
Target changed to 3.0. The form control icon for 'text box' will be adjusted
(icon and term), as that frame is a placeholder for a fomated data field; in the
current state the user could associate the text box with a field, which enabled
pure text input. Furthermore the frame of the 'text box' will show the path to
the appropriate field and the data source. 
Comment 6 bettina.haberer 2008-06-20 15:29:00 UTC
Due to resources we'll have to consider in a further release.
Comment 7 bettina.haberer 2008-10-30 16:32:20 UTC
Target moved.
Comment 8 bettina.haberer 2010-05-21 14:51:48 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".