On 08/25/08 16:29, maoyg wrote:
> I have submitted the second patch about issue7088#. I have some questions
> about this issue.
> My solution is to add another parameter in ScDocFunc::InsertCells(...),
> I only tested the status that the selection is the current view.
> I think ScDocFunc::InsertCells(...)/DeleteCells(...) method possibly refered
> to the many things.
> I found the ScDocFunc::InsertCells(...) is also used for the uno api
> implementation.
> Can I use which way to test it for the uno api implemention?
> whether need I write some basic scripts? Can you give me some guide?
Yes, a simple Basic macro is usually the easiest way to test API calls.
The following inserts a row before the third row on the first sheet:
Sub InsertRow
ThisComponent.Sheets(0).Rows.insertByIndex(2,1)
End Sub
> when the uno api called ScDocFunc::InsertCells(...), the program will execute
> the following code:
> else{ for(SCTAB nTab=nStartTab; nTab<=nTabCount; nTab++)
> aMark.SelectTable(nTab,TRUE);},
> I think the document will occur the error when the sheets have the scenarios.
> what do you think of it?
If a row is inserted on a sheet, it should also be inserted on the
scenario sheets that belong to that sheet, so the scenario ranges point
to the right cells.
Niklas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
