Re: [SailfishDevel] how to get qml debug output to file
Could it be related how and where the qml is loaded? I'm reading the qml files from resource file. I haven't tested this yet with simple application that uses the default sailfishapp structure, so that I could confirm this, just guessing. -- Tero 2014-02-24 9:00 GMT+02:00 Andrey Kozhevnikov coderusin...@gmail.com: working fine for both cpp and qml output On 24.02.2014 05:37, Artem Marchenko wrote: I found message handler working just fine (both for QML console and cpp qDebug() messages) is emulator builds, but not for when code is running on device. Go figure. Could it be so that on device exactly QML engine is somehow always used separately from your c++ execution context.. no it doesn't make sense. It would be nice to have some logs-to-file way working in production with both QML and c++ logs indeed. Cheers, Artem. On Wed, Feb 5, 2014 at 4:58 PM, Robin Burchell robin.burch...@jolla.com wrote: On 04 Feb 2014, at 22:37, Tero Siironen tero.siiro...@iki.fi wrote: Andrey Kozhevnikov coderusin...@gmail.com kirjoitti 4.2.2014 kello 23.14: This is messages handler i'm using in my projects: This doesn't seem to make a difference for me, the log file still contains only c++ side debug prints, qml prints (like console.log()) are not handled with messagehandler. Actually I found out that even if set in pro-file: DEFINES +=QT_NO_DEBUG_OUTPUT DEFINES +=QT_NO_WARNING_OUTPUT I still get qml debug prints printed out to console, so it seems that those prints from qml are not handled via normal debug handling at all? I would like to get no debug printing at all, or then just to file. DEFINES in qmake adds additional defines (-D) to the cflags used to build C++ affect code compiled with them. QtDeclarative was not compiled with these defines, so your adding them won't affect console.log (whose C++ implementation lives inside QtDeclarative). If you don't want debug prints, you need to install a message handler (you say you've tried this and it doesn't work, I can't answer why that would be the case, it should work, as it uses the same infrastructure). BR, Robin ___ SailfishOS.org Devel mailing list -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] how to get qml debug output to file
Andrey Kozhevnikov coderusin...@gmail.com kirjoitti 4.2.2014 kello 23.14: This is messages handler i'm using in my projects: This doesn’t seem to make a difference for me, the log file still contains only c++ side debug prints, qml prints (like console.log()) are not handled with messagehandler. Actually I found out that even if set in pro-file: DEFINES +=QT_NO_DEBUG_OUTPUT DEFINES +=QT_NO_WARNING_OUTPUT I still get qml debug prints printed out to console, so it seems that those prints from qml are not handled via normal debug handling at all? I would like to get no debug printing at all, or then just to file. — Tero ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Binding weirdness on Jolla device after deploy with screen locked
Just to confirm this, I'm having same issues with my app. If I launch it and put the screen off right away the application's screen is not updated when I open it again from the cover. Have to swipe it back to home and reopen it to get updated window. -- Tero 2014/1/26 christopher.l...@thurweb.ch: Hi Ove That's pretty much the behaviour I get, and the swipe to multitasking and back fixes things. The behaviour 1s 100% reproducible when the screen is locked during deploy, and never occurs when deploying to an unlocked screen. That the problem to do with bindings is only a wild assumption on my part, it could be down to the screen not updating as you suggest. Grüsse Chris Zitat von Ove Kåven o...@arcticnet.no: Den 26. jan. 2014 13:42, skrev christopher.l...@thurweb.ch: Hi all I have come across some weird behaviour on the Jolla: Bindings don't seem to work immediately after an app has deployed when the screen is locked. Are you able to tell the difference between something like this, and the more straightforward issue of the app display simply not updating? I frequently experience the latter immediately after a deploy. If I click anything, or try to use the pulley menu, I can hear the sounds and get the console logs, but the display doesn't start updating before I swipe out to the multitasking view and then reactivate it. Everything works otherwise. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] How to hide pushup menu?
I have PushUpMenu in my app which currently has only one item, and in some situations also that item should not be visible. How can I hide the menu? I tried to set MenuItem's visibility to false, but that lead to weird behaviour; PushUpMenu is still there and empty, but the empty menu can be pushed up about screen height. I also tried to use visible property in PushUpMenu, but that doesn't seem to hide the menu. Disabling the MenuItem could be one option, but as it still shows the item's label it would be a bit misleading for the user in my situation. I would prefer to hide the whole PushUpMenu when there's no items that could be used. -- Tero ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to hide pushup menu?
2014/1/23 Oleksii Serdiuk conta...@oleksii.name: Did you try setting `pushUpMenu` property to null? Docs say that it should be null if no push-up menu has been assigned: https://sailfishos.org/sailfish-silica/qml-sailfishsilica-silicaflickable.html#pushUpMenu-prop Thanks for pointing that out, I have to try it, sounds like correct way to do it. -- Tero ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to hide pushup menu?
I found out that I had to set the contentHeight property for the flickable to get rid of the floating pushupmenu”. And then it was enough to set enabled: false and visible: false to get the menu not showing. I tried also setting the pushup property null, but then I had to define the menu outside of the flickable and that caused another interesting side effect. There was black diagonal line through the page. I have no idea where that came from. But anyway, now it works like I wanted it to work — Tero Tero Siironen izer...@gmail.com kirjoitti 23.1.2014 kello 13.55: 2014/1/23 Oleksii Serdiuk conta...@oleksii.name: Did you try setting `pushUpMenu` property to null? Docs say that it should be null if no push-up menu has been assigned: https://sailfishos.org/sailfish-silica/qml-sailfishsilica-silicaflickable.html#pushUpMenu-prop Thanks for pointing that out, I have to try it, sounds like correct way to do it. -- Tero ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] DeclarativeGlassImageProvider
Hi,
No I haven’t got it working. I really think that this is a bug, either with the
provider or with documentation (if this is dropped feature). I’ve tried pretty
much all the different options for setting the source image path, but it fails
always. I still have the code in my app so maybe one day it starts to work
again :) But I would like to get confirmation that is this going to be
supported or not.
--
Tero
David Reinhold da...@reinholds.se kirjoitti 19.11.2013 kello 23.54:
Hi,
I’m having problems with this as well. Did you manage to solve this problem
Tero? The image shows up just fine without the provider but when using the
provider I get:
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
DeclarativeGlassImageProvider::requestImage(): source image is not
available.
Could it have something to do with how the path is specified? I specified an
absolute path. Should it be relative and if so, relative from what?
Regards,
David
24 okt 2013 kl. 21:15 skrev Tero Siironen tero.siiro...@iki.fi:
Maybe I've should give another subject to this. The problem I have is with
Glass background, introduced here:
https://sailfishos.org/sailfish-silica/sailfish-silica-introduction.html
I've ported my app to Qt5 and everything else works fine, but the image
provider for Glass background doesn't. So I'm trying to find out if the
Glass background is still supported or not. Or is there instructions
somewhere how to get similar effect to Image element. I can live without it,
but it gave nice look to the list views when current album's art was used as
background with the glass effect.
--
Tero
Jarko Vihriala kirjoitti 24.10.2013 kello 17.33:
Hi,
In Qt5 version of Silica there is no DeclarativeGlassImageProvider item as
such, the current item names of Silica can be found from plugins.qmltypes
of Silica in /usr/lib/qt5/qml/Sailfish/Silica. With quick look closest
matching to your request would be DeclarativeGlassItem.
All in all, if you have Qt4 based application done with Alpha SDK, it
should be ported to Qt5 using Alpha-Qt5 SDK as almost everything below the
APIs themselves have changed.
thanks, Jarko
From: devel-boun...@lists.sailfishos.org
[devel-boun...@lists.sailfishos.org] on behalf of Tero Siironen
[tero.siiro...@iki.fi]
Sent: Thursday, October 24, 2013 1:38 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] DeclarativeGlassImageProvider
Hi,
I've used glass background for my app successfully in the first alpha
sdk, but since the second alpha sdk, DeclarativeGlassImageProvider hasn't
worked.
Whatever I try to set to source of image element I get error similar to
this:
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
DeclarativeGlassImageProvider::requestImage(): source image is not
available.
qrc:/qml/Silica/AlbumContentPage.qml:66:5: QML Image: Failed to get image
from provider: image://glass//home/nemo/.cache/cuteremote/album/127.png
The code is here:
Image {
id: backgroundImage
source: image://glass/ + __artFileName
sourceSize { width: parent.width; height: parent.height }
}
where __artFileName changes to correct path
(/home/nemo/.cache/cuteremote/album/127.png, file does exists)
Is the DeclarativeGlassImageProvider still supported, has the API changed
or is it just broken?
--
Tero
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] DeclarativeGlassImageProvider
Thanks Mikko, that works! One slash was missing thou image://glass/file:// … Apparently I didn’t try each option. You should update the reference documentation on next update. -- Tero Mikko Harju mikko.ha...@jolla.com kirjoitti 20.11.2013 kello 12.07: On 19.11.2013 23:54, David Reinhold wrote: Hi, I’m having problems with this as well. Did you manage to solve this problem Tero? The image shows up just fine without the provider but when using the provider I get: QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified DeclarativeGlassImageProvider::requestImage(): source image is not available. Can you try if it works with a full url, ie. image:/glass/file:// .. ? Basically it fetches QUrl(source)::toLocalFile() for the part after provider identity. -- mikko ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] DeclarativeGlassImageProvider
Hi,
I've used glass background for my app successfully in the first alpha
sdk, but since the second alpha sdk, DeclarativeGlassImageProvider hasn't
worked.
Whatever I try to set to source of image element I get error similar to this:
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
DeclarativeGlassImageProvider::requestImage(): source image is not
available.
qrc:/qml/Silica/AlbumContentPage.qml:66:5: QML Image: Failed to get image from
provider: image://glass//home/nemo/.cache/cuteremote/album/127.png
The code is here:
Image {
id: backgroundImage
source: image://glass/ + __artFileName
sourceSize { width: parent.width; height: parent.height }
}
where __artFileName changes to correct path
(/home/nemo/.cache/cuteremote/album/127.png, file does exists)
Is the DeclarativeGlassImageProvider still supported, has the API changed or is
it just broken?
--
Tero
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] DeclarativeGlassImageProvider
Maybe I've should give another subject to this. The problem I have is with
Glass background, introduced here:
https://sailfishos.org/sailfish-silica/sailfish-silica-introduction.html I've
ported my app to Qt5 and everything else works fine, but the image provider for
Glass background doesn't. So I'm trying to find out if the Glass background is
still supported or not. Or is there instructions somewhere how to get similar
effect to Image element. I can live without it, but it gave nice look to the
list views when current album's art was used as background with the glass
effect.
--
Tero
Jarko Vihriala kirjoitti 24.10.2013 kello 17.33:
Hi,
In Qt5 version of Silica there is no DeclarativeGlassImageProvider item as
such, the current item names of Silica can be found from plugins.qmltypes of
Silica in /usr/lib/qt5/qml/Sailfish/Silica. With quick look closest matching
to your request would be DeclarativeGlassItem.
All in all, if you have Qt4 based application done with Alpha SDK, it should
be ported to Qt5 using Alpha-Qt5 SDK as almost everything below the APIs
themselves have changed.
thanks, Jarko
From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org]
on behalf of Tero Siironen [tero.siiro...@iki.fi]
Sent: Thursday, October 24, 2013 1:38 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] DeclarativeGlassImageProvider
Hi,
I've used glass background for my app successfully in the first alpha
sdk, but since the second alpha sdk, DeclarativeGlassImageProvider hasn't
worked.
Whatever I try to set to source of image element I get error similar to this:
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
DeclarativeGlassImageProvider::requestImage(): source image is not
available.
qrc:/qml/Silica/AlbumContentPage.qml:66:5: QML Image: Failed to get image
from provider: image://glass//home/nemo/.cache/cuteremote/album/127.png
The code is here:
Image {
id: backgroundImage
source: image://glass/ + __artFileName
sourceSize { width: parent.width; height: parent.height }
}
where __artFileName changes to correct path
(/home/nemo/.cache/cuteremote/album/127.png, file does exists)
Is the DeclarativeGlassImageProvider still supported, has the API changed or
is it just broken?
--
Tero
___
SailfishOS.org Devel mailing list
