hayaku Posted April 7 Posted April 7 Hello, Half way between a bug report and a feature request. If you are inside of a text frame, or recently were inside of a text frame, and hit Ctl + F, the search window comes up, but does not automatically shift the text focus to the search window, allowing you to type. This means that you start typing (expecting to start searching) but instead, text randomly appears inside your text frame (about half of all my typos, picked up by proof readers, seem to result from this) or else my paragraphs randomly change font and style, because my keystrokes get interpreted within the "Text Styles" menu. Easier to spot, and make their way through to print test copies much less often, but still annoying as hell!! To get around this, I have reprogrammed my muscle memory to hit "Ctrl + F, Ctl + F" in rapid succession, since the first brings up the search menu, while the second shifts the focus to the search menu, as expected. But this is very frustrating, and in no other software that I've ever used have I had to do this twice. Context shift was expected and automatic. Can this please be addressed? I can't think of a single use case to bring up the search menu, but leave the context/cursor where it was. Just creates frustration. Thanks!! NotMyFault, HCl and matisso 2 1 Quote
MikeTO Posted April 7 Posted April 7 I assume you're using Windows because you've typed Ctrl and not Cmd. I've never experienced this on macOS so perhaps this is a bug specific to Windows? Is there any more information you can provide on when it happens and when it doesn't? When it happens, take a screenshot of your History panel and save that for later and after you have a few of those review them to look for a pattern. Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
hayaku Posted April 20 Author Posted April 20 Yes, I am using Windows. This happens 100% of the time. It is not so much a replaceable bug, as it is a design oversight. A little more context: I typically work from a "Toggle UI" minimised situation. When I hit Ctl + F, it brings up the UI and the Search bar, but does not move the context window to the search bar. If I happen to have the UI already open, but on another page (Preflight, Pages, etc) it does switch correctly to the Search tab, and does move the context to the Search bar. Problem seems to happen when Ctl + F has to Trigger [UI Show > Select Search Tab > Select Search Bar]. It seems that in this case, on Windows 10, it fails to do the last part. MikeTO 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.