Bug 82664 - Impress: Character tab with FONT SCALING, etc. missing in styles dialog
Summary: Impress: Character tab with FONT SCALING, etc. missing in styles dialog
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 117725 (view as bug list)
Depends on:
Blocks: ImpressDraw-Styles Character-Dialog
  Show dependency treegraph
 
Reported: 2014-08-15 14:08 UTC by Cor Nouws
Modified: 2024-04-22 06:05 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
PDF with three dialogs, showing what is missing (172.17 KB, application/pdf)
2019-06-18 06:46 UTC, Cor Nouws
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cor Nouws 2014-08-15 14:08:57 UTC
Text in Writer can have settings for Position, via Format > Character.
When done if e.g. the frame for the style Title is selected, the settings become part of the style.

However, opening window with setting for any style, does not offer the tab Position..

Has always been this way - as far as I can remember
Comment 1 Cor Nouws 2014-08-15 14:09:48 UTC
(In reply to comment #0)
> Text in Writer can have

must be text in IMPRESS .. obviously
Comment 2 Cor Nouws 2015-06-08 13:19:39 UTC Comment hidden (obsolete)
Comment 3 Cor Nouws 2015-06-08 21:05:47 UTC Comment hidden (obsolete)
Comment 4 Cor Nouws 2015-06-08 21:05:57 UTC
.
Comment 5 QA Administrators 2016-09-20 10:01:07 UTC Comment hidden (obsolete)
Comment 6 Buovjaga 2018-06-15 18:56:13 UTC
*** Bug 117725 has been marked as a duplicate of this bug. ***
Comment 7 QA Administrators 2019-06-16 02:57:27 UTC Comment hidden (obsolete)
Comment 8 Callegar 2019-06-16 07:52:06 UTC
Issue is still present in libreoffice 6.3 beta 1
Comment 9 Cor Nouws 2019-06-16 08:10:47 UTC
unchanged in Version: 6.4.0.0.alpha0+
Build ID: f75c2b04785aa05cff3bcd52689feb7400a14e8e
CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-06-15_11:49:26
Locale: nl-NL (nl_NL.UTF-8); UI-Language: en-US
Calc: threaded

Is there any reason why it would be a bad idea to add that Tab properties in Dram/Impress too ?
Comment 10 Heiko Tietze 2019-06-17 11:32:31 UTC
(In reply to Cor Nouws from comment #0)
> However, opening window with setting for any style, does not offer the tab
> Position..

(In reply to Cor Nouws from comment #9)
> Is there any reason why it would be a bad idea to add that Tab properties in
> Dram/Impress too ?

You mean the changed title should be listed among the master slides?
Comment 11 Cor Nouws 2019-06-18 06:46:05 UTC
Created attachment 152262 [details]
PDF with three dialogs, showing what is missing
Comment 12 Heiko Tietze 2019-06-18 13:09:47 UTC
Don't see a reason why this properties shouldn't be accessible at this dialog.
Comment 13 V Stuart Foote 2019-06-18 13:13:45 UTC
(In reply to Heiko Tietze from comment #10)
> (In reply to Cor Nouws from comment #0)
> > However, opening window with setting for any style, does not offer the tab
> > Position..
> 
> (In reply to Cor Nouws from comment #9)
> > Is there any reason why it would be a bad idea to add that Tab properties in
> > Dram/Impress too ?
> 
> You mean the changed title should be listed among the master slides?

No. In Draw/Impress:

The 'Character' dialog offers four pannels

   Font - Font Effects - Position - Highlighting

The composition of style panel(s) Title, Subtitle (Master mode or Normal) picks up just three

   Font - Font Effects - Highlighting

So where are the controls held in the Position tab for working with Drawing/Slide style for Text box graphics?

Lack of Rotation is obvious, we define a Vertical Text box graphic object for that. And otherwise we rotate the graphic frame itself--not the text.

But, where to set/indicate Superscript/Subscript, or scaling of H-font width, or adjustment of kerning?

Seems like the Position tab is needed. Or, are those settings _not_ recorded into style (and setting each from Character dialog is always direct formatting)?
Comment 14 Cor Nouws 2019-06-18 19:41:28 UTC
(In reply to V Stuart Foote from comment #13)

> into style (and setting each from Character dialog is always direct
> formatting)?
- Create a text box, set e.g. Width scaling 200%
- create new style with that box selected
- apply to another text box
  > width scaling applied
Comment 15 Cor Nouws 2020-02-22 13:01:55 UTC
@heiko: should it be hard to fix this?
Comment 16 Justin L 2020-02-22 13:34:42 UTC Comment hidden (no-value)
Comment 17 Justin L 2020-02-22 16:21:24 UTC
(In reply to Justin L from comment #16)
>  Is there much point in setting an entire paragraph to superscript?
Oh - missed the example of width scaling as the desired setting. Sorry.
Comment 18 Heiko Tietze 2020-02-24 08:24:04 UTC
(In reply to Cor Nouws from comment #15)
> @heiko: should it be hard to fix this?

Define "hard". The UI might not be such a big deal but it also needs to be in the edit engine. For example I don't see how to rotate a paragraph by 90° in Impress. Copy/paste from Writer always inserts an OLE object, wouldn't you expect styled text with full compatibility? Why do we need the Position attributes at all?
Comment 19 Cor Nouws 2020-02-24 09:26:35 UTC
(In reply to Heiko Tietze from comment #18)

Add a shape
type Apple Pie
choose Format > Character
set font scaling to 200% on tab Position
create new style from that shape
  > font position is part of the new style

select style in side bar
choose Modify
  > font position is not there

It should be there.
Comment 20 Heiko Tietze 2020-02-24 10:23:29 UTC
(In reply to Cor Nouws from comment #19)
> It should be there.

/signed
Comment 21 Justin L 2020-06-23 16:51:42 UTC
I thought adding this just might, possibly be easy. But it isn't (unless perhaps you already know the magic tricks of the UI.)
I'm guessing the answers lie partially in sd/source/ui/dlg/tabtempl.cxx
and sd/uiconfig/simpress/ui/templatedialog.ui
Comment 22 Heiko Tietze 2021-06-11 08:17:46 UTC
*** Bug 142751 has been marked as a duplicate of this bug. ***
Comment 23 Heiko Tietze 2021-06-11 08:20:04 UTC
The Format > Styles > Edit Style command (or using the context menu in the Stylist at the sidebar) deals with the paragraph style, ie. Title, Subtitle etc. We do not yet have access to character style in Impress. But it is requested in bug 40871...

*** This bug has been marked as a duplicate of bug 40871 ***
Comment 24 Eyal Rozenberg 2022-12-23 14:27:57 UTC Comment hidden (obsolete)
Comment 25 Cor Nouws 2023-11-05 21:12:24 UTC
This is not about Character Styles. It is about the position of characters in a paragraph (scaling, spacing).
Comment 26 Eyal Rozenberg 2023-11-05 21:26:36 UTC
(In reply to Cor Nouws from comment #25)
> This is not about Character Styles. It is about the position of characters
> in a paragraph (scaling, spacing).

I have - mistakenly - assumed that this can be seen as just a symptom of not having proper character styles. If text in Impress had character styles, that would mean, in particular, that it had scaling and spacing properties which we could control using Format | Character - which would become a full-fledged Character Style editing dialog.

Cor, how would you mark bug 128810? Related? Perhaps blocking?
Comment 27 Cor Nouws 2024-04-21 20:43:42 UTC
(In reply to Eyal Rozenberg from comment #26)
> Cor, how would you mark bug 128810? Related? Perhaps blocking?
None of those, Eyal.
Setting e.g. font scaling for a outline style, can be done independent from the (non)existence of character styles.
Comment 28 Eyal Rozenberg 2024-04-21 21:57:19 UTC
(In reply to Cor Nouws from comment #27)
> Setting e.g. font scaling for a outline style, can be done independent from
> the (non)existence of character styles.

Well, that's true... so resolving this bug won't resolve that one, but in the other direction it probably would. Still, leave things this way for now.
Comment 29 Cor Nouws 2024-04-22 06:05:49 UTC
(In reply to Eyal Rozenberg from comment #28)
> ... but in
> the other direction it probably would.
Serious? How then?