Bug 127952 - Form window sizes not saved correctly
Summary: Form window sizes not saved correctly
Status: RESOLVED DUPLICATE of bug 41777
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.2.7.1 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-03 14:54 UTC by LoloSon
Modified: 2019-11-13 07:23 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 LoloSon 2019-10-03 14:54:23 UTC
Description:
Does not record the size of forms when there are several different form sizes in a database.

Steps to Reproduce:
1. Create a form in Base with a specific size
2. Create a new form in Base with a specific size
3. Create a new form in Base with a specific size
4. Open them: they all have the same size
5. Maximise or modify form windows size (not in edit mode) changes all the forms size :-(


Actual Results:
Modifying a form window size in play o edit mode changes all the forms window size af the project.

Expected Results:
I expect the windows form size could be all the time the same and could just be changed in edit mode.


Reproducible: Always


User Profile Reset: No



Additional Info:
There were not this problem in older versions (before 5.0)
Comment 1 Alex Thurgood 2019-11-13 07:17:01 UTC
@LoloSon : please provide a sample ODB file containing several forms with different sizes made with an older version in which the form sizes were maintained, otherwise it is going to be difficult to show that there is a regression.
Comment 2 Alex Thurgood 2019-11-13 07:21:33 UTC
This seems linked to the behaviour in which LO opens documents with the default size of the StartCenter and/or the last opened document, see for example bug 41777.

Indeed, this report is probably a DUPLICATE of bug 41777
Comment 3 Alex Thurgood 2019-11-13 07:23:38 UTC
Indeed, re-reading bug 41777, pretty certain this report is a DUP of that. Marking as such.

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