Bug 142237 - Fontwork Sidebar missing properties that were previously available
Summary: Fontwork Sidebar missing properties that were previously available
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
7.2.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-12 13:59 UTC by Rafael Lima
Modified: 2021-05-12 17:55 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshots describing the issue (215.91 KB, application/vnd.oasis.opendocument.graphics)
2021-05-12 13:59 UTC, Rafael Lima
Details
current master / 7.2.0 alpha, Draw with Fontwork object selected -- Sidebar Properties Deck all Content panels present (211.02 KB, image/png)
2021-05-12 16:08 UTC, V Stuart Foote
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael Lima 2021-05-12 13:59:49 UTC
Created attachment 171922 [details]
Screenshots describing the issue

So I was testing the Fontwork feature in LO 7.2 alpha (build from 2021-05-06) and I noticed that the sidebar of Fontwork objects are now missing all the properties that were previously available.

In the attached ODG file I show screenshots describing the problem.

Basically, in LO 7.1 the user can change properties as Area, Effect, Line, Shadow, etc (which is very handy). However, in LO 7.2 the sidebar only shows the Fontwork properties.

I believe this was caused by this patch
https://gerrit.libreoffice.org/c/core/+/112275

I also believe the original intent of this patch was to add Fontwork to the sidebar in addition to the properties that were already present. However, it ended up removing the other properties.
Comment 1 V Stuart Foote 2021-05-12 16:08:21 UTC
Created attachment 171924 [details]
current master / 7.2.0 alpha, Draw with Fontwork object selected -- Sidebar Properties Deck all Content panels present

Can not confirm on Windows TB77 nightly

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 5d7251c7121cee8885fa9f2387c4a0625dd4ecee
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

The Properties Deck is fully populated with its content panels, able to adjust Fontwork objects from their default properties.
Comment 2 Rafael Lima 2021-05-12 17:12:17 UTC
> The Properties Deck is fully populated with its content panels, able to
> adjust Fontwork objects from their default properties.

So, I restarted in Safe Mode and used the option "Reset settings and user interface modifications". Then I clicked "Apply Changes and Restart". Now my sidebar looks like yours.

This happened before with other UI changes in LO that did not take effect until I reset my user profile. It seems that whenever there's a change in the sidebar, I need to reset my profile.

Will that be the case for users that upgrade from 7.1 to 7.2, meaning that this issue could happen with them after upgrade as well?
Comment 3 V Stuart Foote 2021-05-12 17:55:47 UTC
(In reply to Rafael Lima from comment #2)
> > The Properties Deck is fully populated with its content panels, able to
> > adjust Fontwork objects from their default properties.
> 
> So, I restarted in Safe Mode and used the option "Reset settings and user
> interface modifications". Then I clicked "Apply Changes and Restart". Now my
> sidebar looks like yours.
> 

Good.

> This happened before with other UI changes in LO that did not take effect
> until I reset my user profile. It seems that whenever there's a change in
> the sidebar, I need to reset my profile.
> 
> Will that be the case for users that upgrade from 7.1 to 7.2, meaning that
> this issue could happen with them after upgrade as well?

Yes, as I recall--between major releases the Sidebar customization has to be reset to defaults, especially when there are new features being added. And of course usually best to back up and completely clear user Profile--then restore what is useful (unfortunately that is not well automated).