Hi alien.
I don't really follow your description of the issue with the PageStack. Are
you trying to use a Dialog, and have the 'accept' action replace the dialog
with another page that you're creating? If so, you need to use the
'acceptDestination' and 'acceptDestinationAction' properties.
ht
Hi rinigus.
I'm not sure why jb5771 is marked as the default, 'master' is the primary
development branch, and the one from which Jolla releases are derived.
The master branch includes code to delegate modification operations to a
daemon, but this is already present in the system, so you do not
Hi Oleg.
I'm sorry, the PageStack simply does not support this model. It can only work
like a stack, where pages are added and removed from one end of the list, and
the existing pages on the stack are unmodifiable while there are other pages
above them in the stack.
In this case, 'above' actu
The PageStack itself does not report the completion of transitions, but the
Page objects involved in the transition see the transition events as changes to
their 'status' property:
https://sailfishos.org/develop/docs/silica/qml-sailfishsilica-sailfish-silica-page.html/#status-prop
When a transit
Hi Georg.
There's three ways to emit notifications: via D-Bus, using the QML binding, and
using the C++ library underlying the QML library. The last one is in the
nemonotifications-qt5 library, the interface is described here:
https://sailfishos.org/develop/docs/nemo-qml-plugin-notifications/l
pgrades to version 16?
On Tue, Oct 27, 2015 at 9:37 AM, Matthew Vogt
mailto:matthew.v...@jolla.com>> wrote:
Hmm, it shouldn't be possible to have a malformed database after doing the
import. I have no idea how that could happen.
If you don't update the user_version to the correct
ead ../temp/dump.sql
c) i did NOT run this : sqlite3 new-db/contacts.db "pragma user_version =
;" (btw my VER was 15)
d) rebooted
e) "pragma integrity_check" returned OK on this latest db file.
On Tue, Oct 27, 2015 at 9:24 AM, Matthew Vogt
mailto:matthew.v...@jolla.com>
he following:
Page xx is never used
Needless to say, after reboot, contact app shows no contacts at all (of course
:) ).
Best,
tk
On Tue, Oct 27, 2015 at 12:30 AM, Matthew Vogt
mailto:matthew.v...@jolla.com>> wrote:
Hi Tone.
Yes, it sounds like you have a corrupted contacts database. Any id
Hi Tone.
Yes, it sounds like you have a corrupted contacts database. Any idea how that
might have happened?
In any case, you can try to recreate the database to fix the issue. You need
to do something along the lines of the following (but please sanity-check these
instructions before running
Thanks for the report Alex, this is now a MER bug:
https://bugs.merproject.org/show_bug.cgi?id=1388
Thanks,
Matt
From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org]
on behalf of Alexander Ladygin [fake...@gmail.com]
Sent: Monday, Octobe
Hi Mattias,
Your app's notifications are grouped according to the 'appName' property they
supply at submission (if not provided, it will default to the name from your
.desktop file, or the process name if necessary).
If you have the new SDK, the notification docs should be available in creator,
l...@thurweb.ch [christopher.l...@thurweb.ch]
Sent: Wednesday, August 12, 2015 3:12 PM
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] Sending SMS via Telepathy: Error "Channel
Dispatcher .. does not support interface CD.I.Messages"
Am 2015-08-12 04:52, schrieb Matthew Vogt:
the best way of reporting this? https://bugs.nemomobile.org/ ?
Chris
Am 2015-08-10 02:15, schrieb Matthew Vogt:
> Mission control appears to implement the
> "org.freedesktop.Telepathy.ChannelDispatcher.Interface.Messages1"
> interface now - see:
>
> https://
Mission control appears to implement the
"org.freedesktop.Telepathy.ChannelDispatcher.Interface.Messages1" interface now
- see:
https://github.com/nemomobile-packages/telepathy-qt/commit/6f0177bc024f3f7bce94c0abc283fba1c3b8a0d1
Perhaps your telepathy-qt packages and your telepathy-mission-contr
Hi Goncalo.
pageStatus will change to activated both the first time your page becomes the
current page of the PageStack, and when you change back to it from another
page. I guess that your error occurs when it tries to call pushAttached() a
second time, as the original page is re-activated.
P
urmi [jpnu...@gmail.com]
Sent: Thursday, July 17, 2014 7:45 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] A welcome dialog and pageStack's operation in
progress.
On Wed, Jul 16, 2014 at 11:25 PM, Matthew Vogt wrote:
>
> Hi, 'Page.status' is the correct prop
Hi, 'Page.status' is the correct property to watch for avoiding this problem.
Here is an example of what you could do:
import QtQuick 2.0
import Sailfish.Silica 1.0
ApplicationWindow {
initialPage: Component {
Page {
anchors.fill: parent
Hi Matze.
Try "contentHeight: dialog.y + dialog.height" in your SilicaFlickable.
Thanks,
Matt
From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org]
on behalf of Matthias Barmeier [barme...@barmeier.com]
Sent: Thursday, May 08, 2014
Hi Vivian.
All visual elements in QML inherit the properties of QtQuick.Item, described
here: http://qt-project.org/doc/qt-5.1/qtquick/qml-qtquick2-item.html
Thanks,
Matt
From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org]
on behalf of
Hi Chris. This sounds like a regression in the (unfinished) qtpim module of Qt
5, which reimplements the functions provided by QtContacts in QtMobility.
You can report bugs against this module here:
https://bugreports.qt-project.org/browse/QTBUG/component/19726
Thanks,
Matt
___
Thanks, I have filed a bug report for this issue.
Matt
From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org]
on behalf of Hendrik Borghorst [hendrikborgho...@gmail.com]
Sent: Thursday, January 16, 2014 9:30 AM
To: Sailfish OS Develo
Hi Wim.
The simplest thing to do, is to wait for the page under your dialog to be
re-activated - when the page status is 'PageStaus.Active' again, then you know
that the pop transition has finished and you can issue a new page stack change.
However, what you should probably do in this case, is
anks,
Matt
From: Wim de Vries [wsvr...@xs4all.nl]
Sent: Wednesday, August 14, 2013 5:42 PM
To: Matthew Vogt
Cc: Wim de Vries; devel@lists.sailfishos.org
Subject: RE: [SailfishDevel] Cannot pop while operation is in progress
Thanks Matt,
This is my function in main.qml (called from within c++)
Hi Wim.
"Cannot pop while operation is in progress" means that the previous PageStack
operation is still animating, and you must wait until it finishes before
issuing the next PageStack operation. There are various strategies you can use
for this, but they will all result in unattractive visua
Destination' version
will give a better user experience.
Thanks,
Matt
From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org]
on behalf of Matthew Vogt [matthew.v...@jollamobile.com]
Sent: Monday, August 12, 2013 8:58 AM
T
instantiated question-page, by some means.
Hope that helps,
Matt
From: Superpelican [superpeli...@zoho.com]
Sent: Monday, August 12, 2013 4:45 AM
To: Matthew Vogt
Cc: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] Bug in the Silica Reference docs and possible
ialog
}
}
Thanks,
Matt
From: Wim de Vries [wsvr...@xs4all.nl]
Sent: Saturday, August 10, 2013 8:52 AM
To: Matthew Vogt
Cc: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] pagestack signals for eg pageback
Hi Matt
Benoît Hervier pointed me to the status pro
Hi Wim.
There are no signals for PageBack or PageForward in the Silica PageStack. What
are you trying to do? From within a Page element, you can observe changes to
the 'pageContainer' property (when added and removed from the PageStack), or
the 'status' property (which reflects the page's sta
Hi Superpelican.
Thanks for catching the errors in the Dialog documentation, I will correct them.
In your Clamshell dialog, you do not need to explicitly pop() the dialog page
in response to the accept action; it is popped by the user's interaction
(either a drag or an 'Accept' click), and the a
Hi Stefan.
In regards to the page stack indicators question: we are aware that the current
indicators implementation does not correctly handle large depth levels. We
will develop a mechanism to ensure that the page stack works sensibly with
larger depth levels, but we haven't yet gone through
Hi Lucien.
The SilicaListView (as well as SilicaGridView and SilicaFlickable) provides the
scrollToTop() function to rapidly return to the top of the list.
You can see an example of its use in the MenuPage in the example
componentsgallery application, inside the PushUpMenu.
Thanks,
Matt
__
Hi Filip, sorry for the top-posted reply, but my client is inadequate :)
1. pushExtra() is now an official part of the PageStack API, except that it has
been renamed to pushAttached().
Until recently, pushExtra was provided to support a specific use-case, and we
hadn't fully considered whether
32 matches
Mail list logo
