[Octave-bug-tracker] [bug #59176] [octave forge] (windows) COM object.Item(n) fails on further '.'-index (error `0x8002000e')

[John Donoghue]

Follow-up Comment #3, bug #59176 (project octave):

eLibro.Worksheets(1).Name = 'page1'


also works.

The issue is that octave is calling each 'subobject' in turn:

So for:

eLibro.Worksheets.Item(1).Name = 'page1';

its doing separate subrefs to:

1. Get the worksheets property.
2. Get the Item property (fails in this case because the property expects an
index)
3. Calls (1)
4. Sets the Name property to page.

Interrestingly running:

eLibro.Worksheets.Item(1).Name


works ok as it groups the subref call types into one operation call, allowing
us to perform multiple operations like getting applying the index to the
property.

But I am not sure why octave is giving single subref operations for assign vs
getting the values. (at least for the parts of the operation that are just
getting values)



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59176>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/