Qt has been updated to 5.15.9 (in Chum and Chum:testing).
Small issue appeared that was leading to freezing of Qt apps when QT_WAYLAND_RESIZE_AFTER_SWAP environment variable was set. New Qt-Runner (0.4.0) removes that variable from the environment used by applications running in it. If you use Qt apps via some other compositor (newcompositor), make sure that you don’t have that env var defined (it is by default on SFOS).
Q: Can I have (activate) Password manager on Angelfish? I can’t find an option to store usernames and passwords in Angelfish. Did I oversee something in Angelfish’s settings?
Actually it seems QtWebEngine does not expose this feature (yet), being discussed for Qt 6.6 or 6.7 but not there yet. So Angelfish would have a hard time implementing that.
@rinigus When upgrading to SFOS 4.5.0.21 qt-runner was uninstalled for me and I can no longer install it from chum app. It seems that chum doesn’t have a build of qt-runner for 4.5.0.21. Can you please add a build for qt-runner or is there some issue?
I was actually curious to try some de applications, like elisa (that does not work anyway) but seems i can’t remove the kde dependencies as everything depends on some other thing, how do i remove things completely?
How can I activate virtual keyboard for a Qt 5.15 app? Calling Qt.inputMethod.show() from qml doesn’t work. I looked at Qt5 VirtualKeyboard but other Qt 5.15 apps in chum don’t seem to use that.
BTW, if someone have issues with app getting wrong width/height it can be solved by disabling Qt::AA_EnableHighDpiScaling.
Just tested Angelfish. Works fast. Thanks for porting! Great achievement!
Found small issues:
If connect headphones when something already playing it has issues with sound (like freezes). Works fine if headphones already connected when Angelfish has been started.
Not able to use “pin” in the player to control player on youtube to rewind a video.
Sometimes not able to exit from fullscreen (on youtube).
Tested on XA2 Plus.
p.s. 4. Quite funny option in settings of Angelfish is “hide navigation bar”.
It does work for me, though iirc, the default fw rules get in the way of device discovery maybe. try noson-app --deviceurl=http://<ipaddress>:1400 as a first run to see if it finds your zone then.