Re-add min width to button in new enty dialog

[Siedlerchr]

User description

Try to fix #14789

Steps to test

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• [.] I manually tested my changes in running JabRef (always required)
• [.] I added JUnit tests for changes (if applicable)
• [.] I added screenshots in the PR description (if change is visible to the user)
• [.] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• [.] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

---

PR Type

Bug fix

---

Description

• Restores minimum width constraint to entry type buttons

• Prevents buttons from shrinking below preferred size

• Adds Region import for USE_PREF_SIZE constant

---

Diagram Walkthrough

flowchart LR
  A["NewEntryView.java"] -->|Add Region import| B["Import javafx.scene.layout.Region"]
  A -->|Set button constraints| C["button.setMinWidth<br/>Region.USE_PREF_SIZE"]
  C -->|Prevents shrinking| D["Button layout fixed"]

Loading

File Walkthrough

	Relevant files
Bug fix	NewEntryView.java Add minimum width constraint to entry buttons                        jabgui/src/main/java/org/jabref/gui/newentry/NewEntryView.java Added import for javafx.scene.layout.Region class Added button.setMinWidth(Region.USE_PREF_SIZE) to prevent buttons from shrinking below their preferred size Applied constraint in addEntriesToPane() method when creating entry type buttons +2/-0

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🟡	🎫 #14789 🟢 Recommended-type buttons should not reflow due to reduced width (e.g., "Misc" should not shift position) ⚪ The "New Entry" dialog should open with the same default size/geometry as before the change in PR No major or unexpected shrink should occur that leaves large unused space The dialog should not open substantially narrower than before After clicking "Other types", the layout should not become crowded due to increased number of options
🟡	🎫 #13109 🔴 Pseudonymization functionality should be available on the CLI Implementation should provide similar CLI experience to consistency check Implementation should follow the pattern of CheckConsistency class
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Learned best practice	Fix method name capitalization The method name contains a typo: 'Bibtex' should be 'BibTeX' to match the correct capitalization used elsewhere in the codebase and in the field's standard naming convention. jabgui/src/main/java/org/jabref/gui/newentry/NewEntryView.java [447] -private void switchSpecifyBibtex() { +private void switchSpecifyBibTeX() { [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 6 __ Why: Relevant best practice - Correct typographical errors in user-facing strings, code comments, and method names to maintain code quality and professionalism	Low
Update

[github-actions]

The build of this PR is available at https://builds.jabref.org/pull/14791/merge.