[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch

2018-10-01 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381975

--- Comment #9 from Christoph Feck  ---
Seems to be a Qt regression. Just using Qt::WindowStaysOnTopHint does not work;
you actually have to use NET::KeepAbove.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch

2018-02-12 Thread Paul
https://bugs.kde.org/show_bug.cgi?id=381975

Paul  changed:

   What|Removed |Added

 CC|pip@gmx.com |

-- 
You are receiving this mail because:
You are watching all bug changes.

[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch

2018-02-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=381975

--- Comment #8 from javascriptj...@hotmail.com ---
> So, if you don't want "always on top", nor do you want "always on bottom"...
> what do you want?

I want the current behavior that I get from unticking "always on top" in
kruler, but which isn't remembered when the app is restarted, as I described in
the original report above.  If you untick "always on top," there is no
enforcement of any z-ordering so other windows can be raised in front of
kruler, or kruler raised on top of them.  I didn't realize this wasn't clear.


> 
> I would respectfully suggest you take a look at the source code and correct
> the problem yourself.

So do all bug filers get told to fix the source code themselves, or am I just
lucky?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch

2018-02-11 Thread Paul
https://bugs.kde.org/show_bug.cgi?id=381975

--- Comment #7 from Paul  ---
(In reply to javascriptjedi from comment #6)
> As I already described when I originally reported this bug, the problem is
> that I *don't want* "always on top" to be enforced (nor do I want "always on
> bottom"), But kruler won't remember this preference.

Ignoring the fact the preference may or may not work, and you may or may not
have created a window rule.

So, if you don't want "always on top", nor do you want "always on bottom"...
what do you want?

I would respectfully suggest you take a look at the source code and correct the
problem yourself.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch

2018-02-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=381975

--- Comment #6 from javascriptj...@hotmail.com ---
> "Position - Remember" and "Keep Above - Force" works well for me.

Works well for you at doing what?

As I already described when I originally reported this bug, the problem is that
I *don't want* "always on top" to be enforced (nor do I want "always on
bottom"), But kruler won't remember this preference.

> Well, if you don't want to enforce any particular window behaviour upon
> kruler... :)

I'm not sure what's supposed to be funny. If there were a window rule to
counteract kruler's inability to remember that I don't want "always on top"
being unticked, it would have to have the impact of preventing "always on top"
behavior, so I could change kruler's z-position manually in the z-order.

Seems pretty clear.  So, it looks like there's no workaround then.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch

2018-02-11 Thread Paul
https://bugs.kde.org/show_bug.cgi?id=381975

--- Comment #5 from Paul  ---
(In reply to javascriptjedi from comment #4)
> What sort of Window rule did you have in mind?  

"Position - Remember" and "Keep Above - Force" works well for me.

> I see options to force the window to the top and force it to the
> bottom, neither of which I want.  The desired behavior is that
> the kruler window is not forced at all.

Well, if you don't want to enforce any particular window behaviour upon
kruler... :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch

2018-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=381975

--- Comment #4 from javascriptj...@hotmail.com ---
(In reply to Paul from comment #2)
> As an interim measure you could create a window rule...
> 
> System Settings - Window Management - Window Rules.

What sort of Window rule did you have in mind?  I see options to force the
window to the top and force it to the bottom, neither of which I want.  The
desired behavior is that the kruler window is not forced at all.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch

2017-12-11 Thread Bruno Baumgartner
https://bugs.kde.org/show_bug.cgi?id=381975

Bruno Baumgartner  changed:

   What|Removed |Added

 CC||m...@wossc.org

--- Comment #3 from Bruno Baumgartner  ---
Kubuntu 14.04-5
I do not have at all the «Always on Top» feature. But it is very necessary now
since I have become a professional Desktop Publisher. It would make live much
easier.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch

2017-09-13 Thread Paul
https://bugs.kde.org/show_bug.cgi?id=381975

Paul  changed:

   What|Removed |Added

 CC||pip@gmx.com

--- Comment #2 from Paul  ---
As an interim measure you could create a window rule...

System Settings - Window Management - Window Rules.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch

2017-09-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=381975

--- Comment #1 from javascriptj...@hotmail.com ---
Any chance of this getting fixed?  I didn't report it just to feel good about
myself.

-- 
You are receiving this mail because:
You are watching all bug changes.