from:"richard grooff"

Re: [SailfishDevel] How to show toast notification?

2020-03-02 Thread richard grooff via Devel

 Hi, 

Are you aware of the example at Nemo QML Plugins Notifications - Sailfish OS

| 
| 
|  | 
Nemo QML Plugins Notifications - Sailfish OS


 |

 |

 |

 Best regards, Richard 



On Monday, March 2, 2020, 1:29:02 PM GMT+1, Tamas Miklos  
wrote:  
 
 Hi,

I'd like to show a quick notification to the user of my SFOS app after 
selecting a certain PullDownMenu item.  The notification doesn't need to be 
modal or have any buttons or require any user interaction.  Much like how the 
Toast notification works in Android apps.  The closest I got to something like 
that is showing a DockedPanel and then hiding it after 2 seconds.  But, it 
would be great to achieve that without DockedPanel.


Thanks,
Tamas

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org  ___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Correct way to implement an import/export dialog

2019-10-23 Thread Richard Grooff via Devel

Maybe use the new phone app with its tabs as an example: tab import and export 
with the same component underneath...

Regards, Richard 

On Wednesday, 23 October 2019, E.S. Rosenberg wrote:
> Both pulldown and push up menus as is already have 3 options, the pull up
> menu has an import option so I want to change that to import/export and the
> page it goes to switches between import and export based on user desire.
> 
> Op wo 23 okt. 2019 om 01:43 schreef Андрей Кожевников <
> coderusin...@gmail.com>:
> 
> > like a caller ui? push up to export, pull down to import?
> >
> > вт, 22 окт. 2019 г. в 23:29, E.S. Rosenberg <
> > es.rosenberg+sailfishos@gmail.com>:
> >
> >> Hi all,
> >> I would like to build a dialog that allows both import and export on the
> >> same page or at least accessible from the same pulley menu item.
> >>
> >> At first I thought I would just have two different forms with buttons on
> >> the same page however according to:
> >>
> >> https://sailfishos.org/develop/docs/silica/sailfish-application-pitfalls.html/#using-buttons-instead-of-platform-style-gestures
> >>
> >> that seems to be the "wrong" way.
> >>
> >> So I wondered is there a "right" way to implement this while trying to
> >> stay within the SFOS UX paradigms?
> >>
> >> Thanks!
> >> Eli
> >> ___
> >> SailfishOS.org Devel mailing list
> >> To unsubscribe, please send a mail to
> >> devel-unsubscr...@lists.sailfishos.org
> >
> > ___
> > SailfishOS.org Devel mailing list
> > To unsubscribe, please send a mail to
> > devel-unsubscr...@lists.sailfishos.org
>

-- 
Sent from my Sony Xperia X with Sailfish X
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Nemo DBus typedCall

2017-06-15 Thread richard grooff via Devel

Hi, 

With the risk of being totally wrong (I'm not really into DBus): according to 
the DbusInterface example in this page: Nemo Mobile D-Bus QML Plugin — Nemo 
Mobile D-Bus QML Plugin 2.0.0 documentation, you should set signalsEnabled = 
true. 
  
|  
|   |  
Nemo Mobile D-Bus QML Plugin — Nemo Mobile D-Bus QML Plugin 2.0.0 documentation
   |  |

  |

 
Regards, rgr


  From: Dylan Van Assche via Devel 
 To: Sailfish OS Developers mailing list  
 Sent: Thursday, June 15, 2017 2:38 PM
 Subject: Re: [SailfishDevel] Nemo DBus typedCall
   
Hi,
I'm trying to listen to the MCE DBUS API for changes from the display and the 
radios.
For some reason, I won't receive the signals while writing on the /request 
endpoint works perfectly.
Someone an idea?

Seems that Slava can make this work: 
https://github.com/monich/harbour-lib/blob/master/src/HarbourSystemState.cpp

DBusInterface {
id: dbusFlight
bus: DBus.SystemBus
service: "com.nokia.mce"
path: "/com/nokia/mce/signal"
iface: "com.nokia.mce.signal"

// Signals

function radio_states_ind(state) {
console.log(JSON.stringify("MCE radio state= " + state))
}

function display_status_ind(state) {
console.log(JSON.stringify("MCE display state= " + state))
}
}

Cheers,
Dylan



 Original Message 
Subject: Re: [SailfishDevel] Nemo DBus typedCall
Local Time: June 12, 2017 12:00 AM
UTC Time: June 11, 2017 10:00 PM
From: slava.mon...@jolla.com
To: Sailfish OS Developers 
Dylan Van Assche 

 Yes, in that respect the changes are backward compatible. Whatever you are 
getting from GetProperties can be monitored by handling the PropertyChanged 
signals. You just need to be prepared that SetProperty and other calls 
(Connect, Disconnect etc.) may respond with net.connman.Error.PermissionDenied 
if your process doesn't have enough privileges for that.
 
 The idea is that the user has to be reasonably sure that a random app pulled 
from Jolla Store doesn't mess with the system configuration (e.g. doesn't 
enable mobile data behind your back). Most likely, a similar fate is awaiting 
ofono and a few other D-Bus interfaces. Right now Jolla Store apps can do way 
too much over D-Bus. We (well, at least I) will try not to not break backward 
compatibility of D-Bus APIs except when the breakage is absolutely inevitable, 
even though those are not officially supported APIs.
 
 And as always, all these changes are open for close examination at 
git.merproject.org.
 
 Cheers,
 -Slava
 
 
 

Can I still monitor for changes and read properties? Can you give a more 
complete view what will change exactly? I am building an universal bridge 
between Python and QML with integrated Platform APIs based on DBUS and other 
stuff.

Dylan
 




 Original Message 
Subject: Re: [SailfishDevel] Nemo DBus typedCall
Local Time: June 11, 2017 7:16 PM
UTC Time: June 11, 2017 5:16 PM
From: slava.mon...@jolla.com
To: devel@lists.sailfishos.org
Dylan Van Assche 

And keep in mind that starting with Sailfish OS 2.1.1 non-privileged processes 
won't be able to set this property (as well as do a few other connman things, 
e.g. manipulate the services). In order to be able to use the restricted D-Bus 
APIs you would have to ask the launcher to run your app under nemo:privileged 
but that would automatically disqualify the app from getting accepted to Jolla 
Store. Sailfish OS is getting security conscious!

Cheers,
-Slava




You’re missing the property name. You need:
 
string:Powered variant:boolean:true
 
ref:
https://together.jolla.com/question/56437/i-would-like-to-toggle-internet-connectivity-via-terminal-with-dbus/
 
typedCall('SetProperty', [ {'type':'s', 'value': 'Powered'}, {'type':'v', 
'value': valuet}], …);
 
ref: https://talk.maemo.org/archive/index.php/t-92303.html 
 
 
-kimmo
 
From: Devel [mailto:devel-boun...@lists.sailfishos.org] On Behalf Of Dylan Van 
Assche via Devel
 Sent: 10. kesäkuuta 2017 12:45
 To: Sailfish OS Developers mailing list
 Subject: [SailfishDevel] Nemo DBus typedCall 
Hi devs,
 
I'm playing around with the Nemo DBus QML plugin but I'm a little bit stuck 
when using the function typedCall().
 
 
 
    DBusInterface {

    id: wifi

    bus: DBus.SystemBus

    service: 'net.connman'

    path: '/net/connman/technology/wifi'

    iface: 'net.connman.Technology'

 

    signalsEnabled: true

 

    function setState(powered) {

    var value = powered? 'true': 'false'

    typedCall('SetProperty',

  {'type':'s', 'value':value},

  function() { console.log('[INFO] wifi power state set') },

  function() { console.log('[ERROR] wifi power state 
failed') })

    }

 

    function propertyChanged(name, value) {

Re: [SailfishDevel] Beginning Sailfish programming?

2016-01-28 Thread Richard Grooff

And check together.jolla.com for similar questions... 

On Thu Jan 28 15:53:35 2016 GMT+0100, Amilcar Santos wrote:
> https://together.jolla.com/question/123975/sailfishosjolla-book-for-developers/
> 
> Here's thread to contribute about documentation to introduce in
> SailfishOS development
> 
> Reference to the sourcecode of a book:
> https://github.com/hardcodes/developwithsailfishos
> 
> 2016-01-28 14:45 GMT+00:00 Kimmo Lindholm :
> > 1. Install SDk
> > https://sailfishos.org/develop/sdk-overview/develop-installation-article/
> >
> > 2. Read some tutorials https://sailfishos.org/develop/tutorials/
> >
> > 3. Check api docs, specially Silica https://sailfishos.org/develop/docs/
> >
> > 4. Read Harbour FAQ https://harbour.jolla.com/faq
> >
> > 5. Code
> >
> > 6. Join us in IRC, e.g.  #sailfishos at freenode – and we like to see the
> > code :)
> >
> >
> >
> > -kimmo
> >
> >
> >
> > From: devel-boun...@lists.sailfishos.org
> > [mailto:devel-boun...@lists.sailfishos.org] On Behalf Of Paul Duncan
> > Sent: 28. tammikuuta 2016 15:59
> > To: Sailfish OS Developers 
> > Subject: Re: [SailfishDevel] Beginning Sailfish programming?
> >
> >
> >
> > Michael,
> >
> >
> >
> > Thank for the reply - I'm sure I will have more questions later :-)
> >
> >
> >
> > Just working on installing the development environment. Last time I tried
> > this there was no dedicated Linux version, so its nice to see that has
> > improved :-)
> >
> >
> >
> > Cheers!
> >
> >
> >
> > Paul.
> >
> >
> >
> > 
> >
> > From: Michael Fuchs 
> > To: devel@lists.sailfishos.org
> > Sent: Thursday, 28 January 2016, 13:28
> > Subject: Re: [SailfishDevel] Beginning Sailfish programming?
> >
> >
> > You can do a lot of things with qml and you will learn it by just using
> > it. If you want to play with inputs, take a look at componentgallery in
> > examples.
> >
> > IMHO two concepts are important to understand the code more easily:
> > Signals: http://doc.qt.io/qt-5/qtqml-syntax-signals.html
> >
> > and the Model/View Concept:
> > http://doc.qt.io/qt-5/qtquick-modelviewsdata-modelview.html
> >
> > I started qml by rebuilding a Qt-widget-based app in qml.
> >
> >
> > Am 28.01.2016 um 14:12 schrieb Paul Duncan:
> >> Hi All,
> >>
> >> I am a reasonably proficient C programmer, but I think what I need is
> >> some sort of "gentle introduction" into getting something onto the
> >> screen, getting input etc, on Sailfish. I have the Jolla phone, and also
> >> have had a Tablet on order for what is probably almost a year now.
> >>
> >> So, where do I start? Do I need to get proficient in another language
> >> first?
> >>
> >> Thanks!
> >>
> >> Paul.
> >
> >
> >>
> >>
> >>
> >>
> >>
> >>
> >> ___
> >> SailfishOS.org Devel mailing list
> >> To unsubscribe, please send a mail to
> >> devel-unsubscr...@lists.sailfishos.org
> >>
> > ___
> > SailfishOS.org Devel mailing list
> > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
> >
> >
> >
> >
> >
> >
> > ___
> > SailfishOS.org Devel mailing list
> > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
> 
> 
> 
> -- 
> Amilcar
> (djditz in the mix... ;)
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.or

-- 
Sent from my Jolla
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] ApplicationWindow.activate() does nothing

2015-06-16 Thread Richard Grooff

Apps can keep it from turning off: 
req_display_blanking_pause and when app closes: 
req_display_cancel_blanking_pause. 

I use it in harboud-hud version openrepos. 

Regards, Richard

On Tue Jun 16 17:01:13 2015 GMT+0200, Thomas Tanghus wrote:
 On Tuesday 16 June 2015 10:51:29 Simo Piiroinen wrote:
  On Tuesday, June 16, 2015 12:25:09 AM Thomas Tanghus wrote:
   On Friday 12 June 2015 12:47:42 coderusin...@gmail.com wrote:
check mce dbus. There is should be a method bot unblanking screen.
   
   Been away since Friday, but req_display_state_on looks like the one.
  
  Hi,
  
  the rule of thumb is:
User turns display on, apps can keep it from turning off.
  
  Now, if you still absolutely need to turn display on, then note that:
 
 Thanks a lot for preventing me from pursuing the wrong path, Simo.
 
 When I get the time to work on it again, I guess it will be 2) in lieu of 4) 
 - 
 but first I have to make a successful dbus call :D
 
  * Explicit display state requests like req_display_state_on, should be
avoided - they can cause subtle problems and/or easily end up ignored
altogether
  
  * Getting display to turn on does not mean the ui can be shown if the
display/device is locked
  
  Least problematic way depends on what the app is/does - terms of
  similarity to sw existing on the device:
  
  1) Just show something on screen if applicable, no user interaction
 i.e. notification banners and such
  
  Start notification type blanking policy exception for relatively short
  period that is not extended due to touch interaction - display comes
  up during that period when/if sensor states etc allows it
  
  com.nokia.mce.request.notification_begin_req(context, 2500, 0)
  
  The context needs to be a string that is unique enough within the
  process that is using it.
  
  If process exits, the exception state is automatically canceled, so
  these can't really be tested with dbus-send  like. The mcetool
  utility can be instructed not to exit when done, so something like
  mcetool --begin-notification=foo,5000,1000 --block works.
  
  Note that the app should do this even if the display happens to
  be on to make overlapping notifications work as expected (mce
  blanks display only if it was off at start of the 1st notification).
  
  2) Prompt something simple from user i.e. likes of usb mode
 selection, headset volume warning, etc
  
  Start notification exception with long enough time for user to
  understand what is happening, optionally extend the duration on touch
  interaction (if user needs to type lock code or something)
  
  com.nokia.mce.request.notification_begin_req(context, 15000, 2500)
  
  When done, terminate exception but (optionally) keep the display on
  for a while longer to give user a chance to continue with something
  else without display blanking in between
  
  com.nokia.mce.request.notification_end_req(context, 2500)
  
  3) Novel call like ui
  
  incoming call:
  
  com.nokia.mce.request.req_call_state_change(ringing,normal)
  
  answered/outgoing call:
  
  com.nokia.mce.request.req_call_state_change(active,normal)
  
  call ended:
  
  com.nokia.mce.request.req_call_state_change(none,normal)
  
  The display should turn on/off just like with normal calls.
  
  The call state tracking uses sender identification too, so several
  processes can at least in theory do this without interfering with
  each other. And state gets canceled automatically when process
  drops from system bus, so dbus-send  co will not work.
  
  4) Novel alarm like ui
  
  I guess to get this working properly it would need some new logic in
  timed and/or mce. But the notifiction methods should work to some
  extent.
  
  Hope this helps.
  
  simo
 
 -- 
 Med venlig hilsen / Best regards
 
 Thomas Tanghu

-- 
Sent from my Jolla
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] ApplicationWindow.activate() does nothing

2015-06-16 Thread richard grooff

Hey Thomas, 
Unfortunately not publicly available. Relevant part is: 
==import QtQuick 2.0
import Sailfish.Silica 1.0
import org.nemomobile.dbus 1.0

Page {
    id: page    property alias blankingtimer : timer    Component.onCompleted: {
    positionSource.start()
    timer.restart()
    }
    onStatusChanged: timer.restart()    Component.onDestruction: {
    positionSource.stop()
    //screenSaver.setScreenSaverDelayed(false)
    timer.stop()
    }    Timer { id: timer
    property alias suspend:  timer.running    interval : 600
    repeat : true
    triggeredOnStart: true
    onTriggered: dbus.call(req_display_blanking_pause, undefined)    
onRunningChanged: {
    if (!running){
    dbus.call(req_display_cancel_blanking_pause, undefined)
    }
    }    property DBusInterface _dbus: DBusInterface{
    id: dbus    destination: com.nokia.mce
    path: /com/nokia/mce/request
    iface: com.nokia.mce.request    busType: 
DBusInterface.SystemBus    }
    } 
=
I would expect you can find the required command at: 
https://github.com/nemomobile/mce-dev/blob/master/include/mce/dbus-names.h 
Regards, Richard    From: Thomas Tanghus tho...@tanghus.net
 To: Sailfish OS Developers devel@lists.sailfishos.org 
 Sent: Tuesday, June 16, 2015 7:55 PM
 Subject: Re: [SailfishDevel] ApplicationWindow.activate() does nothing
   
On Tuesday 16 June 2015 15:27:15 Richard Grooff wrote:
 Apps can keep it from turning off:
 req_display_blanking_pause and when app closes:
 req_display_cancel_blanking_pause.

Thanks Richard, but I don't want it to stop blanking, as the alarms can be up 
to 1 hour; I rather want it to unblank when the time has passed. Otherwise it 
would drain too much on the battery.

 I use it in harboud-hud version openrepos.

Do you have your code publicly available, so I could see an example on how to 
use it?

 Regards, Richard

/Thomas

 On Tue Jun 16 17:01:13 2015 GMT+0200, Thomas Tanghus wrote:
  On Tuesday 16 June 2015 10:51:29 Simo Piiroinen wrote:
   On Tuesday, June 16, 2015 12:25:09 AM Thomas Tanghus wrote:
On Friday 12 June 2015 12:47:42 coderusin...@gmail.com wrote:
 check mce dbus. There is should be a method bot unblanking screen.

Been away since Friday, but req_display_state_on looks like the one.
   
   Hi,
   
   the rule of thumb is:
    User turns display on, apps can keep it from turning off.
   
   Now, if you still absolutely need to turn display on, then note that:
  Thanks a lot for preventing me from pursuing the wrong path, Simo.
  
  When I get the time to work on it again, I guess it will be 2) in lieu of
  4) - but first I have to make a successful dbus call :D
  
   * Explicit display state requests like req_display_state_on, should be
   
    avoided - they can cause subtle problems and/or easily end up ignored
    altogether
   
   * Getting display to turn on does not mean the ui can be shown if the
   
    display/device is locked
   
   Least problematic way depends on what the app is/does - terms of
   similarity to sw existing on the device:
   
   1) Just show something on screen if applicable, no user interaction
   
      i.e. notification banners and such
   
   Start notification type blanking policy exception for relatively short
   period that is not extended due to touch interaction - display comes
   up during that period when/if sensor states etc allows it
   
   com.nokia.mce.request.notification_begin_req(context, 2500, 0)
   
   The context needs to be a string that is unique enough within the
   process that is using it.
   
   If process exits, the exception state is automatically canceled, so
   these can't really be tested with dbus-send  like. The mcetool
   utility can be instructed not to exit when done, so something like
   mcetool --begin-notification=foo,5000,1000 --block works.
   
   Note that the app should do this even if the display happens to
   be on to make overlapping notifications work as expected (mce
   blanks display only if it was off at start of the 1st notification).
   
   2) Prompt something simple from user i.e. likes of usb mode
   
      selection, headset volume warning, etc
   
   Start notification exception with long enough time for user to
   understand what is happening, optionally extend the duration on touch
   interaction (if user needs to type lock code or something)
   
   com.nokia.mce.request.notification_begin_req(context, 15000, 2500)
   
   When done, terminate exception but (optionally) keep the display on
   for a while longer to give user a chance to continue with something
   else without display blanking in between
   
   com.nokia.mce.request.notification_end_req(context, 2500)
   
   3) Novel call like ui
   
   incoming call:
   
   com.nokia.mce.request.req_call_state_change(ringing,normal

Re: [SailfishDevel] Build a Model with fixed items + dynamic ones

2015-04-20 Thread Richard Grooff

Hi, 

In qml it would be something like this: 
 state = Loaded
  for (var i = 0; i  xmlOverstapgegevens.count+6; i++) {
   if (i6)
 {// first we load the FixedValues
 // (use select case? )
 if (i=0){
  list_model2.append({StationVan   :  FixedValue1
 }
 if (i=1){
  list_model2.append({StationVan   :  FixedValue2
 }
 .
 .
 .
 .
 if (i=5){
  list_model2.append({StationVan   :  FixedValue6
 }
   }
   else {// Then we load the dynamic values
 // don't forget to correct the counter for the FixedValues
 var item = get(i-6)
 list_model2.append({StationVan   :  item.StationVan
   }

Don't use two step creation, it caused terrible timing issues for me. 

On Mon Apr 20 10:49:56 2015 GMT+0200, François K. wrote:
 Hi Michael, hi Lucien, hi devs,
 
 
  I support this idea:
  Why don't you build a model that is built in two step during
  creation, first, build the 6 entries, then build the rest ?
 
 Do you suggest to do this in C++ (which is my idea n°1) or mix C++ and QML 
 (see below) ?
 
 
   Is'nt it possible to add the items in the QML-part?
 
 I don't know... I just don't know how to do this with QML :/
 With a SilicaListView, I guess Qt would overwrite the fixed items as soon as 
 I set the model property on the SilicaListView, wouldn't it ?
 
 Cheers,
 
 -- 
 François
 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.or

-- 
Sent from my Jolla
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] (no subject)

2014-11-07 Thread Richard Grooff

Hi, 

In a page I have a fuction to update the xmllistmodel en then the listview with 
it.

fuction previous(){ 
   list_model2.clear()
   xmllistmodel.reload()
   listview.update() 

In the page calling the function  works, the information in the listview is 
replaced with the new information. 
When I call this function from the cover (with pageid.previous() ) the 
listmodel on the page is not cleared and the new information is added to the 
listview (and not replacing the old information). 
Why are the commands working in the page and is listmodel.clear() not working 
from the cover?

Regards, Richard
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] Fuction working on page, but not working called from cover?

2014-11-07 Thread Richard Grooff


(Sorry for my earlier mail without subject )

 Hi, 
 
 In a page I have a fuction to update the xmllistmodel en then the listview 
 with it.
 
 fuction previous(){ 
list_model2.clear()
xmllistmodel.reload()
listview.update() 
 
 In the page calling the function  works, the information in the listview is 
 replaced with the new information. 
 When I call this function from the cover (with pageid.previous() ) the 
 listmodel on the page is not cleared and the new information is added to the 
 listview (and not replacing the old information). 
 Why are the commands working in the page and is listmodel.clear() not working 
 from the cover?
 
 Regards, Richar

-- 
Sent from my Jolla
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] Documentation on listview on cover

2014-11-07 Thread Richard Grooff

Hi, 
I have tried to get a listview on the cover of my app, but haven't succeeded so 
far. Is there any documentation how to do this. The silica reference is very 
short on covers (and has no information on listview on the cover)?

Thanks in advance

Richard
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Documentation on listview on cover

2014-11-07 Thread richard grooff

Hi Jarmo, 
Thanks for your swift response. 
The listmodel is created on thirdpage. I would like the data of the listmodel 
on the coverpage (using listview with reference to thirdpage.listmodel).
Regards, 
Richard  

   From: Jarmo Lahtiranta jarmo.lahtira...@iki.fi
 To: devel@lists.sailfishos.org 
 Sent: Friday, November 7, 2014 4:36 PM
 Subject: Re: [SailfishDevel] Documentation on listview on cover

On 11/07/2014 04:08 PM, Richard Grooff wrote:

 Hi, I have tried to get a listview on the cover of my app, but
 haven't succeeded so far. Is there any documentation how to do this.
 The silica reference is very short on covers (and has no information
 on listview on the cover)?

ListView is pretty well documented on the Qt side.
http://qt-project.org/doc/qt-5/qml-qtquick-listview.html

I don't think using it in the cover is that different from using it in
the main app. Getting data from app to the cover might be another issue
though, so I suggest trying to get it to work with dummy data first.

Maybe this example will help you:
https://github.com/naranek/routeskipper/blob/master/qml/pages/CoverPage.qml
It's from my app and there's a big ListView in the center of the cover
page. It shows just one delegate at a time and swiping left and right
changes the ListView index.

-Jarmo
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

  ___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] How to show toast notification?

Re: [SailfishDevel] Correct way to implement an import/export dialog

Re: [SailfishDevel] Nemo DBus typedCall

Re: [SailfishDevel] Beginning Sailfish programming?

Re: [SailfishDevel] ApplicationWindow.activate() does nothing

Re: [SailfishDevel] ApplicationWindow.activate() does nothing

Re: [SailfishDevel] Build a Model with fixed items + dynamic ones

[SailfishDevel] (no subject)

[SailfishDevel] Fuction working on page, but not working called from cover?

[SailfishDevel] Documentation on listview on cover

Re: [SailfishDevel] Documentation on listview on cover

11 matches

Site Navigation

Mail list logo

Footer information