Bug 416441 - Add window rule Default name order, application name> window rule?
Summary: Add window rule Default name order, application name> window rule?
Status: RESOLVED MOVED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.16.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-19 04:03 UTC by ferweer
Modified: 2020-01-22 14:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Notation where similar names are arranged and it is difficult to read application rules (4.56 KB, image/png)
2020-01-19 04:06 UTC, ferweer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ferweer 2020-01-19 04:03:56 UTC
SUMMARY
window settings for application name
This is the default, which will result in similar names appearing in the name list after adding many.
ISimilar to another suggestion, https://bugs.kde.org/show_bug.cgi?id=416440, this is a suggestion to enhance the convenience of this window rule tab.
How is it?

STEPS TO REPRODUCE
1. systemsettings5>windows rules >windows rules

OBSERVED RESULT
App names follow similar naming conventions, making it difficult to identify which application is which

EXPECTED RESULT
Set the application name to the first display name, such as
application name ー windows settings

Operating System: Kubuntu 19.04
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.2
Comment 1 ferweer 2020-01-19 04:06:36 UTC
Created attachment 125236 [details]
Notation where similar names are arranged and it is difficult to read application rules

Notation where similar names are arranged and it is difficult to read application rules
Comment 2 Vlad Zahorodnii 2020-01-21 12:36:38 UTC
Hmm, one could argue that application name and window rule type should be in separate columns or that window rules and application rules should be in separate tabs. Please create a Phabricator task instead.

https://phabricator.kde.org/
Comment 3 Christoph Feck 2020-01-21 12:45:41 UTC
Generally, we use bugs.kde.org for our users. If a developer thinks that an issue is important enough to be tracked as a task in phabricator, I believe it is the developer's responsibility to add it there.
Comment 4 Vlad Zahorodnii 2020-01-21 13:04:14 UTC
Okay, I'll create a Phabricator task.
Comment 5 ferweer 2020-01-22 01:42:23 UTC
(In reply to Christoph Feck from comment #3)
Thank you, I did not know Phabricator. I was worried about adding requests and suggestions there.
(In reply to Christoph Feck from comment #4)
I first came up with it. If users create requested and proposed tasks on the site used by kde developers, will it interfere with development? not?
As you might expect, I am not a kde developer.
I really agree with having separate tabs. for rules or name. It might be even better if it can be sorted.