Bug 57307 - Basic IDE: adding variable to Watch window performs incorrectly if variable name contains_underscores
Summary: Basic IDE: adding variable to Watch window performs incorrectly if variable n...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version: 3.4.2 release
Hardware: All All
: medium minor
Assignee: LeMoyne Castle
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-20 08:14 UTC by sasha.libreoffice
Modified: 2015-01-22 14:16 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
Selection/Watch failures (123.90 KB, image/png)
2013-01-04 16:49 UTC, LeMoyne Castle 		Details
View All

Description sasha.libreoffice 2012-11-20 08:14:20 UTC 
Basic IDE problem: If we place cursor on variable with underscores in name and click "Enable Watch (F7)" for adding variable to Watch window, it performs incorrectly. Adds only part of name.
Problem seen also if double click on such variable name in program's text. Only part of name selected.

Steps to reproduce:
0. Start any LO module, for example, Writer
1. Press Alt-F11, in dialog "LibreOffice Basic Macros" press "New" and then "Ok"
2. In Basic IDE enter something like this:

Sub Main
First_Result=1
Second_Result=2
End Sub

3. Place cursor on variable name and press "Enable Watch (F7)"
Expected: added variable with correct name to window "Watch"
Actually: added only part of name, for example First instead of First_Result

reproduced in 3.4.2 on Windows XP 32 bit and in 3.6.3 on RFR 17 64 bit

Workaround: select correct name of variable manually and press F7
Comment 1 LeMoyne Castle 2012-12-22 05:19:52 UTC 
Confirmed in build from 12/20 master.  This issue is a more general IDE interface issue of selecting whole identifiers (on dbl click, on add to watch, ???).  

Selection in BASIC IDE should extend the selection from cursor to cover an entire identifier that contains any legal character.  This should include extending the selection to whole keywords that contain other chars invalid for identifiers (like the $ at the end of CHR$()).  I can confirm that is a long-standing issue.  Moved to NEW.
Comment 2 LeMoyne Castle 2013-01-04 16:49:30 UTC 
Created attachment 72513 [details]
Selection/Watch failures

Shows all manner of selected dreck in the Watch Window including: parts of vars, parts of multiple vars, etc.
Comment 3 QA Administrators 2015-01-05 17:51:27 UTC 
** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

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)

Thank you for your help!

-- The LibreOffice QA Team
Comment 4 Beluga 2015-01-22 14:16:16 UTC 
Still doing it.

Win 7 Pro 64-bit Version: 4.5.0.0.alpha0+
Build ID: 07e84cae983c08afdba03018413a19d01abb3006
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-19_06:15:38

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.