getCellByRange("A1") what is he doing with just one cell address?

[vek.m1234]

Why is he specifying a single cell address for a Range? (A range is a set of cells within the Sheet which is all possible cells.
A cursor is a range where you can move.)

Could someone explain the code? (taken from the Calc Reference Card) I expected him to specify a range like “A1:C6” and then create a cursor to hop about inside that range…
(Interface XCellRange)
In spreadsheets valid names may be “A1:C5” or “$B$2” or even defined names for cell ranges such as “MySpecialCell”.

Why then is he calling .gotoEndOfUsedArea - if it’s only 1cell long it makes no sense that I can discern?? (the purpose of which is to do address conversion from relative to absolute???)

[what’s a decent reading resource to understand this - I’ve already tried the ‘Macros Explained’ book]

[karolus]

the prefix My doesn’t give any usefull Information, aslong therse no YourSheet, ThereSheet or whatever…

and Cur after …gotoEndofUsedArea is exactly the same Object, no Need for:

Range = MySheet.getCellRangeByName(cur.AbsoluteName)

[vek.m1234]

it was taken from here https://documentation.libreoffice.org/assets/Uploads/Documentation/en/MACROS/RefCards/LibOBasic-3-Calc-Flat-A4-EN-v111.pdf

[karolus]

additional to my last Comment `…exactly the same as Range

[mikekaganski]

and then create a cursor to hop about inside that range

What made you think so?

[karolus]

Hallo

To answer your question… in case of a single AddressString it returns a (single) Cellobject.

[vek.m1234]

but how does it all hang together??

[Lupp]

This is owed to the structure of the LibreOffice API. The “objects” you are working with when programming for LibO, are defined by the Services they support. If you intend to get access to a single cell characterized by the typical service com.sun.star.sheet.SheetCell you generally get returned an object also supporting the service “com.sun.star.sheet.SheetCellRange” (which then also shows a property .RangeAddress e.g.). There are additional services, and in some special cases they may even conflict on a specific level.
If you now find useful literature clearly describing the concept of service-and-interface-oriented programming, please post a hint.
(Not sure if this helps much: https://en.wikipedia.org/wiki/Service-oriented_programming.)