Issue 14115 - [sheet] setTitleRows not working properly
Summary: [sheet] setTitleRows not working properly
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: Other Other OS
: P3 Trivial
Target Milestone: ---
Assignee: niklas.nebel
QA Contact: issues@api
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-05-05 12:09 UTC by bernardmoreton
Modified: 2013-02-24 21:07 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 bernardmoreton 2003-05-05 12:09:54 UTC 
Whatever values are set for startrow and endrow, or startcolumn/endcolumn, one 
row only is set, and Format/PrintRanges/Edit shows just $1.

The same code block sets the print area perfectly well, so I believe there is a 
real defect here.  Maybe setTitleColumns should also be checked.

The problem exists in 1.0.1 as well as in 1.1beta

dim xPR as new com.sun.star.table.CellRangeAddress	' set up print range
dim aAddresses(0 to 0)	
' ...	
xPR.sheet=0				' Try to define title rows
xPR.StartColumn=1
xPR.StartRow=1
xPR.EndColumn=3
xPR.EndRow=3
aAddresses(0)=xPR
oSheet.setTitleRows(aAddresses())

Bernard Moreton
Comment 1 ooo 2003-05-06 08:55:52 UTC 
implementation issue
Comment 2 niklas.nebel 2003-05-06 09:06:56 UTC 
setTitleRows takes a single CellRangeAddress, not a sequence.
Comment 3 niklas.nebel 2003-05-06 09:07:25 UTC 
closing.
Comment 4 bernardmoreton 2003-05-06 13:54:11 UTC 
On using
aTitleRows=oSheet.getCellRAngeByPosition(0,0,8,3)
oSheet.setTitleRows(aTitleRows)

got error message
IllegalArgumentException
Message: cannot coerce argument type during corereflection call!.

At least the sequence code didn't generate an error!  Or have I 
misunderstood?

Many thanks for your prompt reply, but I think a further clue is 
needed!

Bernard Moreton
Comment 5 bernardmoreton 2003-05-07 14:22:06 UTC 
Cracked it - and my head as well!  Please ignore my last comment.
And many thanks again for the clues given!
Bernard Moreton
Comment 6 ace_dent 2008-05-17 21:20:08 UTC 
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 7 ace_dent 2008-05-17 23:23:22 UTC 
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew