Re: [SailfishDevel] Sharing model between pages ("by reference")

2015-02-01 Thread Dirk Zimmermann
On 01.02.2015 11:19, Andrey Kozhevnikov wrote: > Why didn't you tried before asking? This is working in exactly same way > as you described in your question. I asked because in my case it didn't work. Otherwise there wouldn't have been a reason to ask :) > Below is template pages. MainPage declar

[SailfishDevel] Sharing model between pages ("by reference")

2015-02-01 Thread Dirk Zimmermann
Hi, I have a page with an attached page. Currently, they get pushed on the stack by a parent page like this: pageStack.push(Qt.resolvedUrl("Page1.qml"), lightModel) pageStack.pushAttached(Qt.resolvedUrl("Page2.qml"), lightModel) Page1.qml will then refresh its copy with live data. I would rather

Re: [SailfishDevel] How does the mer build engine compile for armv7hl?

2015-01-10 Thread Dirk Zimmermann
On 10.01.2015 14:30, David Greaves wrote: > Typically you'll approach this by getting into the sb2 environment (like > a chroot) and running ./configure; make > > To do it more cleanly and in a manner that could eventually become part > of the OS (ie in mer-tools) you'd create a simple rpm package

Re: [SailfishDevel] How does the mer build engine compile for armv7hl?

2015-01-10 Thread Dirk Zimmermann
On 10.01.2015 11:15, jerome levreau wrote: > for all project, click the project tab and add a kit, that all. Than select > target from the build button (bottom left) > to be able to deploy you have to add a device from tool->options->mobile ; > dev mod must be enable (may need to reboot the phone)

[SailfishDevel] How does the mer build engine compile for armv7hl?

2015-01-10 Thread Dirk Zimmermann
Hi all, I was wondering how the mer build engine builds things for armv7hl. When I login, I only found a i486 gcc, none for arm. Is there any documentation how it builds a QT project for armv7hl, that is the actual commands used when one clicks the build icon in qtcreator (with a vanilla sailfish

Re: [SailfishDevel] Read-only TextArea: Always keep the lines added last visible

2015-01-08 Thread Dirk Zimmermann
On 07.01.2015 12:06, Sami Kananoja wrote: > Hi, > > This should do the trick: > > SilicaFlickable { > id: flickable > anchors.fill: parent > contentHeight: textAreaLog.height > contentY: Math.max(0, contentHeight - height) > TextArea { > id:

Re: [SailfishDevel] Read-only TextArea: Always keep the lines added last visible

2015-01-07 Thread Dirk Zimmermann
On 02.01.2015 09:21, Андрей Кожевников wrote: > 1. Why TextArea? Why not ListView + ListModel. TextArea (or anything similar) gives me nice line wrap (some lines are very long). If need I can also omit newlines and make even better use of available space. > 2. TextArea have own scroller, you dont

[SailfishDevel] Read-only TextArea: Always keep the lines added last visible

2015-01-01 Thread Dirk Zimmermann
Hi all, I was trying to use a TextArea as a UI-visible debug log, so I can see connection error details while I'm out using my app. The basic principle is that the python code (pyotherside) will make a server request and send detailed answers to the text area, which displays them. Everything works

Re: [SailfishDevel] /home/src1/ - compile hello-world application

2014-12-21 Thread Dirk Zimmermann
I encountered this error as well when I followed the getting started tutorial (error message taken from previous mail): 17:43:40: Running steps for project tag2a... 17:43:40: Starting: "/home/marcus/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-i486/qmake" /home/marcus/projects/jolla/tag2