| Summary: | Add window rule Default name order, application name> window rule? | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | ferweer <gyrlgith> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED MOVED | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.16.5 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Notation where similar names are arranged and it is difficult to read application rules | ||
|
Description
ferweer
2020-01-19 04:03:56 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
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/ 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. Okay, I'll create a Phabricator task. (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. |