Created attachment 178426 [details] Search slot Actual Behaviour When the cursor is in the search slot and the user wants to perform a more detailed search. The shortcut Cmd + Shift + F (Mac) does not work. Expected Behaviour When the cursor is in the search slot and the user wants to perform a more detailed search using the shortcut Cmd + Shift + F (Mac), it should work. Reproduce Follow steps in the "Actual Behaviour"
Maybe it's macOS specific as I can't reproduce with 7.1 or the latest. Do you still see this in 7.4? Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away. Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 96a856f87f16cca2e039c973c18d57c8b9dca362 CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Jumbo Built on 19 December 2022
Hi Buovjaga. I confirm that it is still there. cmd + alt + f when cursor on the text opens the find and replace window cmd + alt + f when in the search slot does not open the search and replace window. Version: 7.4.2.3 / LibreOffice Community CPU threads: 8; OS: Mac OS X 12.6; UI render: default; VCL: osx Locale: it-IT (it_IT.UTF-8); UI: en-US Calc: threaded
Tried to reproduce although have to admit I am confused since title and OP talk about cmd + shift + f while Daniele talks about cmd + alt + f My results: cmd + alt + f when cursor on text: opens find and replace window cmd + alt + f when in search bar: opens find and replace window Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e272fd31b115e6ea128b593087aeaf4f55119a36 CPU threads: 8; OS: Mac OS X 13.1; UI render: Skia/Raster; VCL: osx Locale: de-DE (en_DE.UTF-8); UI: en-US Calc: threaded
@Daniele and @Anduril: can you retry with main build from https://dev-builds.libreoffice.org/daily/master/current.html and let us know if this is resolved for you?
Hi @Steve, should I choose : tb93-TDF or tb92-TDF?
(In reply to Daniele from comment #5) > Hi @Steve, should I choose : tb93-TDF or tb92-TDF? According to your CPU, x86_64 for Intel, aarch64 for M1.
Thanks @Buovjaga, there are two M1 versions: MacOSX-aarch64@tb92-TDF and MacOSX-aarch64@tb93-TDF on this page: https://dev-builds.libreoffice.org/daily/master/current.html I am not sure which I should use. Also, as I am working with LO I would like if the best thing not to touch the 7.4.2.3 I am using and keep both this one and the newest one upon installation. I would the delete the one I dowloaded from https://dev-builds.libreoffice.org/daily/master/current.html once finished with the test. Is this correct?
(In reply to Daniele from comment #7) > Thanks @Buovjaga, > there are two M1 versions: > > MacOSX-aarch64@tb92-TDF > and > MacOSX-aarch64@tb93-TDF > > on this page: https://dev-builds.libreoffice.org/daily/master/current.html > I am not sure which I should use. Pick the one with the newest date. > Also, as I am working with LO I would like if the best thing not to touch > the 7.4.2.3 I am using and keep both this one and the newest one upon > installation. I would the delete the one I dowloaded from > https://dev-builds.libreoffice.org/daily/master/current.html once finished > with the test. Is this correct? Yes, you can delete the unstable version after testing.
Unfortunately after installation, when opening it i got the message: “LibreOfficeDev” is damaged and can’t be opened. You should move it to the Bin. And so I did. I installed: MacOSX-aarch64@tb92-TDF 2022-12-22 04:36:08 and MacOSX-aarch64@tb93-TDF 2022-12-21 04:37:18 Sorry I cannot help.
(In reply to Daniele from comment #9) > Unfortunately after installation, when opening it i got the message: > “LibreOfficeDev” is damaged and can’t be opened. You can try this in the terminal: xattr -d com.apple.quarantine /path/to/LibreOfficeDev.app Note to correct the actual path. It removes the quarantine attribute from the app.
Or more user friendly: you can just right click the installed main build application in your applications folder and select open. Do this twice and you should be able to start your test.
Hi @Steve: I did the test with MacOSX-aarch64@tb93-TDF 2023-01-03 05:15:28 and clicking on alt + Cmd + f while in the search slot opens the advanced search window. Kudos to the developers! @Buovjaga: the xattr command worked, thanks. @Steve: I could not make the user-friendly way work, unfortunately.
Thanks for testing, I think this is enough to close.
Yes, it can be closed @Buovjaga, the solution works very well.