Group creation not possible anymore with default settings

[AEgit]

JabRef 5.0-dev--snapshot--2019-03-18--master--52696f04b
Windows 10 10.0 amd64
Java 1.8.0_201

Steps to reproduce the behavior:

1. Open "Groups" panel and try to add a group (or edit a pre-existing one - the problem appears there as well)
2. Give a name (and a description, but that does not change the problem)
3. Hierarchical context is set to default (i. e. "Independent group") and Type is set to default as well (i. e. "Statically group entries by manual assignment")
4. Note, that you cannot create this group -> the "OK" button is greyed out and inactive

Workaround:

5. Set "Type" to "Automatically create groups" - now it is possible to create the group, i. e. the "OK" button is active
6. After using the workaround it is also possible to switch back to the default "Type" for this group, i. e. "Statically group entries by manual assignment" when creating the group

Note, that you have to use the workaround EVERY time you create a new group.

[Siedlerchr]

Noticed that as well. Once you switch to another radio button and back again the OK is no longer disabled, Probabl the validation/disable property of the ok button is not set correctly

[bernhard-kleine]

If you confirm the name of the group with "enter", the OK appears clickable. Even if have want to edit an existing group, you have first to accept the group name with enter, otherwise any change can not be saved.

[harinda05]

Without refactoring the logic of the existing code much I was able to create a simple patch for this. Now the enabling/disabling the OK button with regards to the text fields have been validated properly. As @Siedlerchr mentioned now no need to switch to another radio button and back again to enable the OK button.

ps: This is my first commit in the repo. So if there's any specifics I have missed I beg your pardon :) Happy to contribute!

[Siedlerchr]

Thanks to @harinda05 this should be resolved now in the latest master.

We would like to ask you to use a development build from https://builds.jabref.org/master and report back if it works for you. Please remember to make a backup of your library before trying-out this version.

[AEgit]

I can confirm that this bug has been fixed in:

JabRef 5.0-dev--snapshot--2019-04-08--master--3d2d61d0c
Windows 10 10.0 amd64
Java 1.8.0_201