Bug 136285 - In LO7, the macro inspector started working incorrectly.
Summary: In LO7, the macro inspector started working incorrectly.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
7.0.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: BASIC-IDE
  Show dependency treegraph
 
Reported: 2020-08-30 11:51 UTC by Kadet
Modified: 2021-11-17 05:14 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Screenshots of the error (529.91 KB, application/zip)
2020-08-30 11:52 UTC, Kadet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kadet 2020-08-30 11:51:31 UTC
Description:
In LibreOffice 7.0.0.3. and in LibreOffice 7.0.1.2., it is no longer possible to copy the value of variables during step-by-step debugging of the program. (Win7, Win10, MAC). (Scrin).
Also, the variable NAME was highlighted and transferred to its value.

Steps to Reproduce:
1.Two clicks in the inspector window in the variable value field during step-by-step debugging of the program. The value is not highlighted or copied. (Scrin.jpg)
2.the value of the variable str1 = "this is a string" (Step1.jpg).
3.select (by clicking, without copying) the variable name in the inspector window (the value or type cannot be selected) (Step2.jpg).
4.щёлкаем в окошке "Контрольное значение" — в нём появляется имя переменной, а заодно значение переменной меняется на её имя (и в инспекторе и реально в макросе) (Step3.jpg).
5.looking at the" new " value of the variable in msgbox (Step4.jpg).
(If the variable type is numeric, it is assigned 0 (the numeric value of the string), but it doesn't change other types of variables.)

Actual Results:
The value of the variable is not copied. The variable name is transferred to its value.

Expected Results:
The value of the variable must be copied. The variable name should not be highlighted, copied, or transferred to is transferred to its value.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
In LO6. 4. 7 everything worked as it should.
Comment 1 Kadet 2020-08-30 11:52:40 UTC
Created attachment 164873 [details]
Screenshots of the error

Screenshots of the error
Comment 2 Kadet 2020-08-30 16:06:45 UTC
Sorry; 4. click in the "Control value" window — the name of the variable appears in it, and at the same time the value of the variable changes to its name (both in the inspector and actually in the macro) (Step3.jpg).
Comment 3 Andreas Heinisch 2020-09-10 20:48:52 UTC
Confirmed in:

Version: 7.1.0.0.alpha0+ (x64)
Build ID: 91f5709dc362cbdfa3322f93275f842b5059c49c
CPU threads: 6; OS: Windows 10.0 Build 17134; UI render: Skia/Vulkan; VCL: win
Locale: de-DE (de_DE); UI: en-US
Calc: CL
Comment 4 Andreas Heinisch 2020-09-10 21:12:26 UTC
But works in:

Version: 6.3.3.2 (x64)
Build-ID: a64200df03143b798afd1ec74a12ab50359878ed
CPU-Threads: 6; BS: Windows 10.0; UI-Render: GL; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: CL
Comment 5 Andreas Heinisch 2020-09-12 07:42:32 UTC
Very strange behaviour of LO. I tried to test this error again and I could not reproduce it neither in 7.0.0.3 nor in 7.1. Setting to unconfirmed again, maybe someone can reproduce it later.
Comment 6 Buovjaga 2021-04-19 16:09:50 UTC
Kadet: do you still reproduce this in 7.1? An example file would be nice to make the testing quicker

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 7 QA Administrators 2021-10-17 03:55:24 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2021-11-17 05:14:06 UTC
Dear Kadet,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp