So thx to special on #sailfishos :
A work around for rich text :
Add a Component.onCompleted: {
_editor.textFormat = TextFormat.RichText
}
And for the flickable : that's just a wrong binding of content-height ... i was
using childrenRect.height instead of contentItem.childrenRect.height
Re
Great idea, Filip. I think more people would be comfortable using a system
that first aggregates data user-agnostic. Then we could assign these
exchange experiences by clumped regions community members could sign up for.
On Tue, Aug 6, 2013 at 11:26 AM, FIlip Kłębczyk wrote:
> Hello,
>
> I'm org
Hello,
I'm organizing little tour in order to meet people interested in
Sailfish development and activate community a bit. The goal of the event
is to exchange experience regarding new SDK and also help people with
installing SDK (if there are some). Everybody is welcome to attend as it
is in
Hi,
If i believe the documentation of TextArea :
https://sailfishos.org/sailfish-silica/qml-sailfishsilica-textarea.html,
TextArea support rich text.
But i put the following text in a editable TextArea : 'this is a
test lfksjdlsjdf'
None decoration is made, and tag appear. I didn't see any
Other option would just to add depency to spec file (or to yaml), that way
package gets automatically installed to toolchain while building.
BuildRequires: pkgconfig(python-2.7)
re, Jonni
From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sail
On 5. aug. 2013, at 16:07, christopher.l...@thurweb.ch wrote:
> DeclarativeWindowAttached: unsupported platform: "wayland"
>
> After my app (newly ported to Alpha 2) starts up this error appears twice. So
> far I have no clue what is causing it.
Ignore it. You aren't doing anything wrong, it's a
Hi Christopher,
Indeed i think the vm was the toolchain, and not an host of the toolchain :p
That's solve my problems and I'll be able to play now with PyOtherSide on
sailfish.
Thanks a lot !
--
Benoît HERVIER - http://khertan.netLe 06/08/13 11:14
christopher.l...@thurweb.ch a écrit :
Hi Benoi
W dniu 06.08.2013 11:14, christopher.l...@thurweb.ch pisze:
Hi Benoit
B.t.w, zypper in to the MERSDK and adding packages to the toolchain via
the SDK Control Center are NOT the same thing*.
I was also a bit confused on this, but as I see it, using zypper in the
MERSDK makes stuff available to t
Hi,
On 06.08.2013 12:14, christopher.l...@thurweb.ch wrote:
Hi Benoit
B.t.w, zypper in to the MERSDK and adding packages to the toolchain via
the SDK Control Center are NOT the same thing*.
I was also a bit confused on this, but as I see it, using zypper in the
MERSDK makes stuff available to
Hi Benoit
B.t.w, zypper in to the MERSDK and adding packages to the toolchain
via the SDK Control Center are NOT the same thing*.
I was also a bit confused on this, but as I see it, using zypper in
the MERSDK makes stuff available to the underlaying operating system,
but not necessarily t
W dniu 06.08.2013 11:03, christopher.l...@thurweb.ch pisze:
Salut Benoit
Have you tried installing python-devel via the SDK Control Center in
QtCreator. (The Sailfish Icon on the left side of QtCreator)
He wrote that he installed it through Zypper so he has Python.h, the
source of problem is
Salut Benoit
Have you tried installing python-devel via the SDK Control Center in
QtCreator. (The Sailfish Icon on the left side of QtCreator)
I have just done so, an now have a python.h file in the toolchain
(before I had none).
Chris
Zitat von "Benoît HERVIER" :
Morning
I'm currentl
Morning
I'm currently facing a problem that i didn't understand :
./qpython.h:4:20: fatal error: Python.h: No such file or directory
qpython.h
#ifndef _QPYTHON_H
#define _QPYTHON_H
#include "Python.h"
I ve installed via zypper python-devel in mersdk vm.
I've even added hardcoded p
13 matches
Mail list logo
