You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.
Note that in SharpDevelop 2.1 pressing enter will cause the default
button to be clicked (either Find or Find Next) and focus will return to
the dialog. This was not added to SharpDevelop 2.0.
Rename the "Search and Replace" dialog to "Find and Replace" since the
options on the dialog are all called Find even the toolbar button.
Alternatively change the options in the dialog so they are called Search
and leave the dialog name unchanged.
No keyboard accelerators for dialog buttons. 'Fi&nd what', 'Re&place
with:', '&Find', '&Search in:'
Can we add keyboard accelerators for the toolbar buttons?
Change "Search in:" to "Look in:".
Use the standard replace keyboard shortcut Ctrl+H instead of Ctrl+R.
Disable the various buttons if no find text has been entered.
After clicking the Replace all button the focus should stay with the
Search and Replace dialog. Currently the text editor grabs the focus.
Currently when clicking Find All the focus is kept with the Search and
Replace dialog.
Search part has a button called Find, but the Replace part has a button
called Find Next. They should be consistent.
Comment from Matt Ward on 7/12/2006 21:59:17:
In revision 2.1.1574 - Ctrl+F and Ctrl+R now switch the search and
replace dialog between the search/replace mode when the dialog has
focus. Before this only worked if the dialog was open but did not have
the focus. This removes the need for special shortcuts for the toolbar
buttons. The dialog's buttons are now disabled when no find pattern is
entered - fixes the problem where pretty much every character in the
text file would be matched if a search was done with an empty string for
a find pattern.
Comment from Daniel Grunwald on 11/10/2013 17:57:39:
We also should replace the XmlForms. Maybe a complete rewrite of the GUI
might be in order?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
SD-919, originally created on 6/27/2006 11:41:44 by Matt Ward
Possible enhancements for the search and replace dialog taken from
forum:
http://community.sharpdevelop.net/forums/thread/9022.aspx
Note that in SharpDevelop 2.1 pressing enter will cause the default
button to be clicked (either Find or Find Next) and focus will return to
the dialog. This was not added to SharpDevelop 2.0.
Rename the "Search and Replace" dialog to "Find and Replace" since the
options on the dialog are all called Find even the toolbar button.
Alternatively change the options in the dialog so they are called Search
and leave the dialog name unchanged.
No keyboard accelerators for dialog buttons. 'Fi&nd what', 'Re&place
with:', '&Find', '&Search in:'
Can we add keyboard accelerators for the toolbar buttons?
Change "Search in:" to "Look in:".
Use the standard replace keyboard shortcut Ctrl+H instead of Ctrl+R.
Disable the various buttons if no find text has been entered.
After clicking the Replace all button the focus should stay with the
Search and Replace dialog. Currently the text editor grabs the focus.
Currently when clicking Find All the focus is kept with the Search and
Replace dialog.
Search part has a button called Find, but the Replace part has a button
called Find Next. They should be consistent.
Comment from Matt Ward on 7/12/2006 21:59:17:
In revision 2.1.1574 - Ctrl+F and Ctrl+R now switch the search and
replace dialog between the search/replace mode when the dialog has
focus. Before this only worked if the dialog was open but did not have
the focus. This removes the need for special shortcuts for the toolbar
buttons. The dialog's buttons are now disabled when no find pattern is
entered - fixes the problem where pretty much every character in the
text file would be matched if a search was done with an empty string for
a find pattern.
Comment from Daniel Grunwald on 11/10/2013 17:57:39:
We also should replace the XmlForms. Maybe a complete rewrite of the GUI
might be in order?
The text was updated successfully, but these errors were encountered: