On 19/02/2016 11:13, Dubstar_04 wrote:
> This is a copy of the code from the mouse area:
>
> MouseArea {
> id: mouseArea
> anchors.fill:parent
>
> hoverEnabled: true
> cursorShape: Qt.CrossCursor
> }
>
>
> The Apps were built with "framework": "ubuntu-sdk-15.04" which framework are you using?
>
That isn't enough. MouseArea.cursorShape is subject to interference from
overlapping MouseAreas etc. Nothing guarantees you it will be reflected
on the QWindow::cursor() of your application, which is what the shell
(Unity 8) sees. So it depends on the scene as a whole.
That test app I pointed you to uses just plain Qt/QML. There's no Ubuntu
Ui Toolkit in there.
My guess is that the bug is either in the application code or in the
toolkit used by it.
Check if you QWindow::cursor() also changes to a Qt.CrossCursor.
On 19/02/2016 11:13, Dubstar_04 wrote:
> This is a copy of the code from the mouse area:
>
> MouseArea {
> id: mouseArea
> anchors.fill:parent
>
> hoverEnabled: true
> cursorShape: Qt.CrossCursor
> }
>
>
> The Apps were built with "framework": "ubuntu-sdk-15.04" which framework are you using?
>
That isn't enough. MouseArea. cursorShape is subject to interference from
overlapping MouseAreas etc. Nothing guarantees you it will be reflected
on the QWindow::cursor() of your application, which is what the shell
(Unity 8) sees. So it depends on the scene as a whole.
That test app I pointed you to uses just plain Qt/QML. There's no Ubuntu
Ui Toolkit in there.
My guess is that the bug is either in the application code or in the
toolkit used by it.
Check if you QWindow::cursor() also changes to a Qt.CrossCursor.