Apache OpenOffice (AOO) Bugzilla – Issue 77152
RPT : autoshapes are not visible in report
Last modified: 2009-07-19 20:07:01 UTC
1. open a new database 2. open a new report designer 3. insert any data control and bind it to any datasource 4. insert a autoshape into detail section 5. execute the report ==>> the shape is not displayed in the report document
add keyword new_implementation
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.
Please check in cws rpt23fix01
Please verify. Thanks.
Reopen it. You have to position a label control at position 0,0 and a shape below it to reproduce it.
Fixed in rpt23fix02
verified in CWS rpt23fix02 find more information about this CWS, like when it is available in the master builds, in EIS, the Environment Information System: http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Frpt23fix02
Tested w 2.3m_1 and SRB 1.0 Re-opeing issue. When following the steps in the issue it passes - adding a second graphic into the group header however fails. Actually, you can have a graphic in the group header as many copies of a graphic as you like, in different sections it seems - as long as they are all the same shape. The problem happens when you have different shapes. Not only is the second shape added not displayed, it is dropped from the report when it is saved. Attaching a test document Report1 has a shape in the group header Report1_1 has a shape in the detail section Report1_2 did have a triangle in the group header instead of the diamond. The graphic is deleted everytime the report is saved.
Created attachment 47636 [details] bug doc
please remember the one-per-issue rule ... Issue 80928 is for thee vanishing triangle.
Andrew, if I understand you right, the main and only point is that two different shapes in a report do not work - yes? If so, we should probably add this to issue 80928, and close this one here, again. (We should definitely close it, since the original problem is fixed. Question is whether there are more issues than the one described in issue 80928.)
atjensen: please read fs's last comment.
one-per-issue rule
-> closed