Bug 136882 - Enter group does not have any visual feedback
Summary: Enter group does not have any visual feedback
Status: RESOLVED DUPLICATE of bug 122735
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
6.4.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-18 14:21 UTC by Alex
Modified: 2021-10-28 23:28 UTC (History)
1 user (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 Alex 2020-09-18 14:21:45 UTC
Description:
When user presses Enter Group, there is no visual feedback as to which objects are part of the group and which are not. Also there is no feedback for state of group edit mode. Essentially makes feature unusable.

Steps to Reproduce:
1. Open Draw or Writer (mostly annoying in these, but bug also present in Impress and Calc)
2. Make a group of any two objects, place a third object just floating about
3. Enter the group, observer the lack of any visual feedback.

Actual Results:
No dimming/highlight

Expected Results:
Some kind of dimming and / or object highlight (as per documentation) would be nice.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Tested on Linux and Windows builds, with and without HW accel. Version info may be not 100% correct as I have installed latest release in hope it was fixed.
Comment 1 psidiumcode 2021-05-18 18:08:25 UTC
I could reproduce it. 

Version: 7.0.5.2
Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a
CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded

Version: 7.2.0.0.alpha1+ / LibreOffice Community
Build ID: b1c0734ffe0f395757b6e0cea7830d820231afeb
CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded
Comment 2 Regina Henschel 2021-10-28 23:28:19 UTC
The problem is already tracked in bug 122735.

*** This bug has been marked as a duplicate of bug 122735 ***