---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119663/
---
(Updated Sept. 30, 2015, 4:02 nachm.)
Status
--
This change has been
> On Aug. 8, 2014, 3:35 nachm., Thomas Lübking wrote:
> > Would it be sufficient to set the cursor on "target" instead of an
> > application wide override?
> >
> > setOverrideCursor has this "nasty" stack behavior which could be
> > troublesome in a library and I could eg. think of "screensave
> On Aug. 8, 2014, 5:35 nachm., Thomas Lübking wrote:
> > Would it be sufficient to set the cursor on "target" instead of an
> > application wide override?
> >
> > setOverrideCursor has this "nasty" stack behavior which could be
> > troublesome in a library and I could eg. think of "screensave
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119663/#review64072
---
Would it be sufficient to set the cursor on "target" instead o
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119663/
---
Review request for kde-workspace.
Bugs: 334762
http://bugs.kde.org/sh
