Bug 501739

Summary:	Improve UX if text is too long for the input fields
Product:	[Applications] kmenuedit	Reporter:	postix <postix>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	wishlist	CC:	nate
Priority:	NOR
Version First Reported In:	6.3.3
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description postix 2025-03-19 12:28:18 UTC

Right now we got single line input fields. These work fine as long as the text fits into them and is fully shown.

There are two issues:

1) The user may not notice that not everything is visible, because there are no ellipses or fade outs
2) The user may be restricted in screen size given a long input text.

Especially "Environment Variables" and "Command-line arguments" can become quiet long.

Therefore it would be great if either
a) there were an ellipses or fade out effect
or
b) single line input fields became vertical expanding multi line input fields

Comment 1 Nate Graham 2025-03-19 20:03:10 UTC

These are standard single-line Qt text fields; if the problem exists here, in principle it exists everywhere.

I see two options:
1. Improve the discoverability of too-long text in standard Qt text fields.
2. Switch to a multi-line text field here as needed, and then wrap the text.

#2 is feasible to do here, but I'm not sure it would be a good idea since it would cause the layout to bounce around and align poorly, and then we'd just get bug reports about that.

Comment 2 postix 2025-03-19 20:19:07 UTC

Make sense. 

Got a last idea: 
#3 Show a popup multi-line input field on click above or below the input field

When the text fits (does not fit), popup closes (opens) and the focus is set accordingly to the right control. The text would be shown in both controls. I could imagine it to work nicely.

Think _out of the box_  :-)