Repro.

Note that the following works OK:

Sub TestAWTPointInVAriantArray
  Dim p(0)
  Dim h As New com.sun.star.awt.Point
  h.X=1
  p(0)=h
  Msgbox "h.X=" & h.X & " p(0).X=" & p(0).X 
End Sub

As pointed out by Mike, using Object or Variant as the type of p(0) will work.

Sub Test1
  Dim p(0) As Object
  Dim h As New com.sun.star.awt.Point
  h.X=1
  p(0)=h
  Msgbox "h.X=" & h.X & " p(0).X=" & p(0).X 
End Sub

Now one thing bent my mind. Although printing p(0).X returns 0, if you inspect p(0) using XRay Tool you'll see that X = 1 inside p(0). What gives?

Sub Test2
  Dim p(0) As New com.sun.star.awt.Point
  Dim h As New com.sun.star.awt.Point
  h.x = 1
  p(0) = h
  MsgBox p(0).X ' Prints 0
  XRay p(0) ' Here p(0).X is equal to 1
End Sub

The built-in debugger in the IDE also sees no problem with the p array from the start message.

The problem arises for arrays of structures. Same for custom types:

Type MyType 
  X As Long
End Type  

Sub TestCustomType
  Dim p(0) As MyType
  Dim h As MyType
  h.X=1
  p(0)=h
  Msgbox "h.X=" & h.X & " p(0).X=" & p(0).X 
End Sub

Result: h.X=1 p(0).X=0

The array elements are correct in all examples. The construct p(0).X "sees" the previous version of p(0).

Sub TestAWTPoint5
  Dim p(0) As New com.sun.star.awt.Point, q
  Dim h As New com.sun.star.awt.Point
  Dim v
  p(0).X=9
  h.X=1
  p(0)=h
  Msgbox "h.X=" & h.X & " p(0).X=" & p(0).X   ' h.X=1 p(0).X=9
  v=p(0)
  Msgbox "v.X=" & v.X                         ' v.X=1  
End Sub

Dear Vladimir Sokolinskiy,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug