On Tuesday, November 19, 2013 3:10:29 AM UTC-6, rengel wrote: When I first tried to use find by entering Ctrl-F, I was frustrated that I > couldn't enter anything into the Find field. Only after studying the > documentation and watching the screencast I was able to perform a search. > The minibuffer detracts the focus from the Find tab. I have to jump between > two different places on the screen to change settings. >
The old way sucked. Impossible to say how many people turned away from Leo because of it. I am working long hours to correct it. Why use the minibuffer at all? When Ctrl-F opens the Find tab the fields > are there right on this tab. As a user I expect that can enter my search > term in the Find field and my replacement term in the Change field. > You're right. For newbies, and for anyone else that prefers it, Ctrl-F should indeed open the Find tab, select all the text in the findbox, and put focus in the findbox. There will be a new setting that chooses between mouse-oriented and minibuffer-oriented operation of the Find pane. I prefer using the minibuffer because (with my settings) the text in the minibuffer is much larger than the text in the findbox. Rev 6330, committed a few hours ago, makes the Find Pane fully functional, or very nearly so, with the mouse: - All the buttons work when clicked. - It's possible to enter text in either the findbox or replacebox using the mouse. Most aspects of standard key handling also work in the Find Pane: - Tab moves between the elements in what seems to me the most useful way. - The Enter key executes a button when it has been tab selected. - The Return key in the findbox or replacebox executes the find-next command. Still to do: - Bind Ctrl-G and all find-related key-bindings to all the widgets in the Find pane. - Ensure that <Return> does nothing when tab-focus is on a radio button or check box. - Add keyboard shortcuts to the labels of the buttons. For example, the first button will be "Find Next (F3)". Nontrivial! Most (all?) these bindings will be to the containing QFrame, rather than to each individual widget. > Just put in a 'Start Search' button and this functionality behaves like expected. Debatable, for at least three reasons: 1. Many editors, including Scite, use a "Find Next" button, not a "Start Search" button. 2. Labels of the buttons in the Find pane should indicate command the button executes. The first button must be "Find Next". 3. Imo, opening the Find pane is the real start of a search. As I write this, I remember an Aha from last night. Ctrl-F should be bound to the find-tab-open command(!) Now there is one less command in the Find menu, and the name describes more accurately what Ctrl-F does. That is, the find-tab-open command will be a front end for two commands, depending on the new setting: A. (mouse-oriented) opens the Find pane and puts focus in the findbox. B. (minibuffer-oriented) works like Ctrl-F: opens the Find pane and starts a minibuffer command, except (Aha!) that <tab>, not Ctrl-Shift-R will be the Easter Egg that selects the replacement string. This will cause a cascade of further simplifications. > One more thing: Instead of "For help: <alt-x>...." there should be a button that triggers that action. Great suggestion! I've just made a note of it. It will happen today. > You don't have to redo the Find/Replace screencast if this dialog works like people are used to from many other products. Screencasts will change the way people think about Leo. All aspects of Leo will be covered. The new screencast will discuss both mouse-oriented and minibuffer-oriented operation, including the <tab> Easter Egg. Many thanks for your comments. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
