> Artem.
>
>
>
> On Wed, Feb 5, 2014 at 4:58 PM, Robin Burchell
> wrote:
>>
>> On 04 Feb 2014, at 22:37, Tero Siironen wrote:
>> > Andrey Kozhevnikov kirjoitti 4.2.2014 kello
>> > 23.14:
>> >
>> >> This is messages handler i&
Andrey Kozhevnikov 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 foun
Hi,
I’ve been using qInstallMsgHandler earlier with Harmattan to get debug prints
from c++ and qml to a file. Now that I’m trying to do the same with Sailfish
and Qt5 using qInstallMessageHandler, I get only c++ prints to file, qml prints
are shown in console or qtcreator. Debug printer is inst
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 :
> Hi Ove
>
> That's pre
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 kirjoitti 23.1.2014 kello 13.55:
> 2014/1/23 Oleksii
2014/1/23 Oleksii Serdiuk :
> 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 tr
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 pushe
rce(SailfishApp::pathTo(”qml/appname.qml"));
view->show();
return app->exec();
}
--
Tero
Tero Siironen kirjoitti 30.11.2013 kello 9.57:
> Hi,
>
> I noticed that cover actions of my app had stopped working after the bigger
> update of SDK. I debugged it a bit yesterday a
Hi,
I noticed that cover actions of my app had stopped working after the bigger
update of SDK. I debugged it a bit yesterday and found out that the main seems
to be the problem. If I use the default template, actions are visible and works
in the cover:
Q_DECL_EXPORT int main(int argc, char *ar
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 kirjoitti 20.11.2013 kello 12.07:
> On 19.11.2013 23:54, David Reinhold wrote:
>> Hi,
>>
>> I’
t 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 :
>
>> Maybe I've should give another subject to this.
s
> 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:
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::op
Hi,
I used glass background for my app successfully in the first alpha
sdk, but now with qt5 alpha sdk whatever I try to set to source of
image element I get error like this:
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
DeclarativeGlassImageProvider::req
14 matches
Mail list logo
