Bug Hunting Session
Bug 38165 - Closing Base window closes open edit windows without saving causing data loss
Summary: Closing Base window closes open edit windows without saving causing data loss
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
3.3.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Base-UX
  Show dependency treegraph
 
Reported: 2011-06-10 11:31 UTC by Matt Schulte
Modified: 2017-06-03 09:54 UTC (History)
2 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 Matt Schulte 2011-06-10 11:31:30 UTC
We have verified this bug exists on Windows installs of 3.2.2 and 3.4.0 Final (2011-06-03).

Open a database in the Base app.  
Open a Form and modify something on the form.
Close the Base app (using the X button or choosing File->Exit of File->Close).
The Form that was being edited closes with no prompt to save your changes.

To me this is a large bug.  App should always check for changes before exiting and prompt to save if changes detected.
Comment 1 Alex Thurgood 2011-06-10 23:35:40 UTC
This is the way that Base has always was functioned. If you delete the parent container, i.e. the main Base application window it is equivalent to disposing of the connection. The child windows which represent Query, Table, Form and Report management all depend on the main Base application window.

In effect, your request is not a bug request, but a feature request to make the child windows independent of the main Base. Unfortunately, this would require quite a lot of work and many changes to the underlying code I suspect, not to mention the Base API.


Alex
Comment 2 Alex Thurgood 2011-06-10 23:42:50 UTC
From what I can recall, the child windows do not communicate their status to the parent window, so it is currently impossible for the parent to know whether anything has changed. This is why it is advisable, out of principle, to regularly click on the "Save" button of the parent window, since changes are only written to the ODB file when the user does this.

Given the current lack of developer resources available in the project for Base-related problems, it is unlikely that this will change anytime soon.

Alex
Comment 3 Alex Thurgood 2011-06-10 23:55:17 UTC
Having said all that, I have discovered another bug (related no doubt to the same behaviour, which will cause a table, query, form, report wizard to enter a loop if the parent window is closed before the wizard can complete. I will open a separate report for this.

Alex
Comment 4 Matt Schulte 2011-06-13 08:16:57 UTC
I suppose "it has always been that way" is one way to look at it.  But IMO any program that exits without checking the state of its child windows is just wrong.  

I do understand that resources are limited but I believe this should still be something that is added to the list of things to tackle at some point down the road.
Comment 5 Alex Thurgood 2011-06-13 08:38:48 UTC
(In reply to comment #4)
> 
> I do understand that resources are limited but I believe this should still be
> something that is added to the list of things to tackle at some point down the
> road.



Oh, I fully agree with you, but (1) I'm not a developer :-)), and (2) the UNO programming interface is a fairly complex beast and not always as fleshed out as one would like to be !

Alex
Comment 6 Björn Michaelsen 2011-12-23 12:27:01 UTC Comment hidden (obsolete)
Comment 7 Alex Thurgood 2015-01-03 17:40:27 UTC Comment hidden (no-value)