Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Add warning when "Label" field is empty in Set Custom Command #1053

Open
DrDurango opened this issue Jun 5, 2016 · 2 comments

Comments

@DrDurango
Copy link

If the user enters a custom comm and (for instance "sort") in the Command field in the Set Custom Command dialog, and fails to enter anything in the "Label" field, the dialog will ignore what the user entered and do nothing after the user clicks on the button.
This is very annoying, especially to a new user. There are a number of questions about this on stackoverflow web sites.
I recommend the following:

  1. The Label field should NOT be blue after the user starts entering text in the Command field. It should turn white to indicate to the user that Geany is expecting input. Currently the field stays blue, which implies that it it not necessary to enter text in the Label field.
  2. If the user enters a command in the Command field, but fails to enter anything in the Label field, Geany should give a warning if the user clicks on , and Geany should suggest a label name based on the Command.
@DrDurango DrDurango changed the title [Feature Request] Add essage when "Label" field is empty in Set Custom Command [Feature Request] Add warning when "Label" field is empty in Set Custom Command Jun 5, 2016
@elextr
Copy link
Member

elextr commented Jun 5, 2016

Custom commands work for me without labels, the menu shows the command instead. And the keybindings work as well.

@b4n
Copy link
Member

b4n commented Jun 5, 2016

@DrDurango the label is not the problem. The problem you see is that when you click a button without first "validating" the command entry's value with Return or Tab the changes to it are discarded. To enter a custom command then, don't forget to hit Return to validate the field.

This is a known issue, but unfortunately it mostly depends on a GTK behavior I don't know how to work around.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants