Bug 103240 - Modify toolbar state in Customize dialog
Summary: Modify toolbar state in Customize dialog
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.3.0.0.alpha0+
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 107388 (view as bug list)
Depends on:
Blocks: Customize-Dialog Toolbars
  Show dependency treegraph
 
Reported: 2016-10-15 13:49 UTC by Yousuf Philips (jay) (retired)
Modified: 2018-09-08 04:49 UTC (History)
5 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 Yousuf Philips (jay) (retired) 2016-10-15 13:49:46 UTC
In Tools > Customize > Toolbars, the option to set the status of the toolbar isnt available. It should give drop down list access to the 'Visible' toolbar property available in the *WindowState.xcu files. Not sure if users should also be give access to the 'ContextSensitive' toolbar property.
Comment 1 Muhammet Kara 2016-12-07 11:21:48 UTC
(In reply to Yousuf Philips (jay) from comment #0)
> In Tools > Customize > Toolbars, the option to set the status of the toolbar
> isnt available. It should give drop down list access to the 'Visible'
> toolbar property available in the *WindowState.xcu files. Not sure if users
> should also be give access to the 'ContextSensitive' toolbar property.

What if we add some radio buttons like the ones for Style? (Under them)
Style:        Icons      Icons & Text      Text
Visible:      True       False
Comment 2 Yousuf Philips (jay) (retired) 2016-12-08 16:41:40 UTC
(In reply to Muhammet Kara from comment #1)
> What if we add some radio buttons like the ones for Style? (Under them)
> Style:        Icons      Icons & Text      Text
> Visible:      True       False

I guess radio buttons are fine, but is it not possible to also have a 'True (Contextual)' value as well?
Comment 3 Heiko Tietze 2017-07-20 12:21:31 UTC
*** Bug 107388 has been marked as a duplicate of this bug. ***