Bug 125614 - Make Base Search record dialog non modal
Summary: Make Base Search record dialog non modal
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Base-Enhancements
  Show dependency tree / graph
 
Reported: 2019-06-01 07:05 UTC by sportegioco
Modified: 2024-12-19 17:22 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description sportegioco 2019-06-01 07:05:46 UTC 
Description:
In libreoffice base when I open the search record window, it is presented in a modal format and I cannot write on masks or on table until the window is closed.
In libreoffice writer when I use the find and replace window instead I can keep it open and write to the document
This speeds up the work a lot

Actual Results:
The problem is in all version of libreoffice

Expected Results:
Change to non modal window


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Alex Thurgood 2019-06-03 07:40:42 UTC 
@sportegloco : for some reason, you have created a duplicate of your own previous bug report bug 113140, which was marked as a duplicate of bug 32506.

Doing the same here.

*** This bug has been marked as a duplicate of bug 32506 ***
Comment 2 sportegioco 2019-06-03 08:09:41 UTC 
I saw bug 32506, but this is not a duplicate. Simply ask to change the window from modal to non modal because it speeds up the work, ... no other change
Comment 3 Alex Thurgood 2019-06-27 08:08:35 UTC 
OK, so let's set this to new then, even if I still think they are ultimately the same thing, as a Search & Replace dialog would need to be non-modal in order to check that the desired changes had taken place.
Comment 4 Alex Thurgood 2019-06-27 08:10:02 UTC 
*** Bug 126123 has been marked as a duplicate of this bug. ***