'Cannot create bitmap cursor' with qt backend #3562
Comments
fishdude@... commented QImageReader is not able to read() from intfac5.png in WzMainWindow::loadCursor() in wzapp_qt.cpp It gives an 'InvalidDataError'. But intfac5.png can be viewed with gwenview(qt based) and imagemagick without problems. |
fishdude@... commented The issue seems to be a lookup issue of intfac5.png. |
Cyp changed status from |
Cyp changed resolution from `` to |
Cyp commented qt: Use QImage instead of QImageReader to load mouse cursor images. Some combination of QImageReader, QImage, QPixmap, QCursor and the wzfs wz:: virtual file system apparently doesn't The following error was printed (multiple times) to the shell: Fixes #3562.
|
Cyp commented qt: Use QImage instead of QImageReader to load mouse cursor images. Some combination of QImageReader, QImage, QPixmap, QCursor and the wzfs wz:: virtual file system apparently doesn't The following error was printed (multiple times) to the shell: Fixes #3562.
|
2 similar comments
Cyp commented qt: Use QImage instead of QImageReader to load mouse cursor images. Some combination of QImageReader, QImage, QPixmap, QCursor and the wzfs wz:: virtual file system apparently doesn't The following error was printed (multiple times) to the shell: Fixes #3562.
|
Cyp commented qt: Use QImage instead of QImageReader to load mouse cursor images. Some combination of QImageReader, QImage, QPixmap, QCursor and the wzfs wz:: virtual file system apparently doesn't The following error was printed (multiple times) to the shell: Fixes #3562.
|
keyword_cursor_qt
resolution_fixed
type_bug
| by fishdude@...Configuring wz with --with-backend=qt and having qt 4.8.2 installed, i get
'QCursor: Cannot create bitmap cursor; invalid bitmap(s)'
18 times when starting the game.
Inside the game i have only the system cursor available, as it could be guessed.
Cursors are working with SDL backend and have worked with qt backend before.
Maybe there was a change from 4.8.1 to 4.8.2.
Issue migrated from trac:3562 at 2022-04-16 09:54:32 -0700
The text was updated successfully, but these errors were encountered: