Issue 128465 - Inserting a Formula Directly - formula not shown immediately
Summary: Inserting a Formula Directly - formula not shown immediately
Status: RESOLVED DUPLICATE of issue 127861
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: 4.2.0-dev
Hardware: PC All
: P5 (lowest) Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2021-07-02 13:52 UTC by Czesław Wolański
Modified: 2023-12-30 11:22 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Comparing the result of inserting formula directly (106.86 KB, image/jpeg)
2021-07-02 13:52 UTC, Czesław Wolański 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Czesław Wolański 2021-07-02 13:52:15 UTC 
Created attachment 87040 [details]
Comparing the result of inserting formula directly

Help topic "Shortcuts (OpenOffice Math Accessibility)" states:

"If you want to insert a formula into a text document,
 and you already know the correct writing,
 you can proceed as follows:

 1. Write the formula into your text
 2. Select the formula
 3. Choose the command Insert - Object - Formula."

The result should be a displayed formula.
In AOO 4.2.0-dev it is not - one can only see a rectangle with the object's name and "plug-in"-like icon. In versions 4.1.10, 4.1.9 and 4.1.11-dev the formula is shown as expected (cf. the attached file with screenshots).


---------------

AOO420m3(Build:9822)  -  Rev. 9505b3531f
2021-06-19 10:32 - CYGWIN_NT-10.0 x86_64 - Snapshot Test Build
Comment 1 Matthias Seidel 2021-07-02 15:15:18 UTC 
Confirmed with AOO 4.2.0 (latest build) on Windows 10.
Comment 2 damjan 2023-12-30 08:54:59 UTC 
Testing a couple of old versions, by creating a Writer document, typing 1+1, and selecting that and running Insert -> Object -> Formula.

Commit                                  |Date      |OS     |Status
----------------------------------------+----------+-------+-------
f331e23ffae9e26f93997dc8f02086c5733e80df|2014-02-25|FreeBSD|Works
(the merge base between 4.1.x and 4.2.0)|          |       |
6dd50e53129adaa307ec5b2aba73acd299ab2e3b|2014-10-21|FreeBSD|Works
f1d7d1c02075b181fb9e6b602d2923ea341d9bba|2016-08-05|Windows|Works
71bc2237ed32a770b27c542d9e9f101134b193a4|2017-07-01|Windows|Works
4e549649559c9592d2292549945507e18df42348|2018-01-04|Windows|Broken
a658d2c3a558c3c19f1f11cd0c149f02935bb073|2023-01-30|FreeBSD|Broken

So:
- it affects all operating systems, not just Windows.
- it broke between 2017-07-01 and 2018-01-04.
- it affects the latest trunk too.

It will probably need a "git bisect" across those last few months of 2017.
Comment 3 damjan 2023-12-30 11:22:40 UTC 
I was wrong, the very latest trunk fixes this bug.

This must be a duplicate of bug 127861, as that bug's regression occurred in the same time range, and reverting the fix for bug 127861 reproduces this bug on the latest trunk too.

Resolving duplicate. Thank you for your bug report!

*** This issue has been marked as a duplicate of issue 127861 ***