| Summary: | kwin doesnt place winecfg's window centered | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | farmboy0 |
| Component: | rules | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | l.lunak |
| Priority: | NOR | ||
| Version First Reported In: | 5.6.5 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
first part of the rule description
seconf part of the rules description xwininfo xprops kwinrules |
||
|
Description
farmboy0
2016-07-03 15:22:38 UTC
Created attachment 99828 [details]
first part of the rule description
Created attachment 99829 [details]
seconf part of the rules description
It'll likely demand that position (or configure itself there afterwards) "Ignore requested geometry" (At least "apply initially", perhaps "force" is required) PS: "kcmshell5 kwinoptions", you can configure the global placement strategy there. No need for a rule here. Ignore requested geometry doesnt work. Neither of them. Global window placement is already set to centered. No effect, even not without the rule. can you please dump "xprop" and "xwininfo" on the window and attach the output? xwininfo > ~/winecfg.info xprop > ~/winecfg.props The cursor turns into a "+" each time, then just click the window. Created attachment 99830 [details]
xwininfo
Created attachment 99831 [details]
xprops
The window certainly positions itself, but (required) setting "ignore requested geometry" to "force" and "yes"(!) should prevent that. Otherwise there's a bug. In that case please attach ~/.config/kwinrulesrc Created attachment 99832 [details]
kwinrules
I don't think the rule set up this way actually matches the winecfg window (window class is not set, nor anything else in the first screenshot). And this works perfectly fine here, when the winecfg window is open, using Alt+F3/Advanced/Special window settings (or whatever it's exactly in English) and then following comment #9. |