Download it now!
Bug 43492 - Watch function of user defined type displays only first child variable
Summary: Watch function of user defined type displays only first child variable
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
3.3.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-03 10:59 UTC by mieszcz
Modified: 2018-03-16 09:54 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mieszcz 2011-12-03 10:59:03 UTC
As in example:

Type configDataElement
'The types will be defined As: String, Element
	elementName	As	String
	elementString	As	String
End Type

sub main
dim a As configDataElement
a.elementName = "xdafsdsf"
a.elementString = "something else"
End sub

Now start program debugging.
And add variable a into watch.
In the watch you can see only the child called elementName, and nothing else.
It is wrong. For simple type it is not so annoying, but when user define more complicated type (even with trees), then it is very annoying if you cannot see
what is stored in the variables.


The bug still persists in 3.5.0.0 beta
Comment 1 sasha.libreoffice 2012-04-27 07:53:06 UTC
Reproduced in 3.3.4 and 3.5.2 on Fedora 64 bit
When we watch variable "a" in watching window, then we see arrow to left of it. But when we click this arrow to unfold object variable, nothing happens.
Comment 2 QA Administrators 2015-01-05 17:52:41 UTC Comment hidden (obsolete)
Comment 3 mieszcz 2015-01-05 19:53:58 UTC
The bug is still present in libreoffice version 4.2.8.2
Comment 4 QA Administrators 2016-01-17 20:05:44 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2017-03-06 14:48:14 UTC Comment hidden (obsolete)
Comment 6 mieszcz 2017-03-11 13:28:27 UTC
It seems, that in Libreoffice version 5.2.6.2 everything works well.
In my opinion the bug can be closed.
Comment 7 QA Administrators 2018-03-12 03:35:54 UTC Comment hidden (obsolete)
Comment 8 mieszcz 2018-03-15 10:25:31 UTC
This bug can be closed, as it seems to work well at this time
Comment 9 Xisco Faulí 2018-03-16 09:54:24 UTC
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.