Hi,
This we'll do as well, but typically closer (or after) having the first
binaries released.
At this point it is just the code. The goal is to make it straightforward to
use ASR and TTS functionality from Qt apps and devices. This helps in
accessibility and enables hands free operation of
Hi to all,
I'm a blind developer.
I'm writing a Qt5 app in python, with PyQt5 framework.
QLineEdit and QTextEdit doesn't work with screen reading software.
Screen reader won't read characters and words.
By pressing arrow keys it is silent.
I tried to change font, but nothing.
There are any way to m
> On 18 Sep 2015, at 17:33, Robin Burchell wrote:
>
> On Fri, Sep 18, 2015, at 05:12 PM, Nurmi J-P wrote:
>> - QtQml 2.2
>> - QtQml.Models 2.3 (++)
>> - QtQuick 2.6 (++)
>> - QtQuick.Particles 2.0
>> - QtQuick.Controls 1.5 (++)
>> - QtQuick.Layouts 1.3 (++)
>> - QtQuick.Dialogs 1.2
>
> You misse
On Fri, Sep 18, 2015 at 8:12 AM, Nurmi J-P wrote:
> Hi all,
>
> I'd like to propose that all QML imports that are part of the Qt Essentials
> start following the respective Qt version number.
>
> Let's take a look at the version history of some of the QtQml and QtQuick
> imports.
You missed a f
On Fri, Sep 18, 2015 at 1:32 PM, Sorvig Morten <
morten.sor...@theqtcompany.com> wrote:
>
> > On 17 Sep 2015, at 19:15, Dean Floyd wrote:
> >
> > Dear all,
> >
> > We have a project where we weak link our app against the Wacom framework
> which on MacOSX by default gets installed in:
> >
> > /Lib
On Fri, Sep 18, 2015, at 05:12 PM, Nurmi J-P wrote:
> - QtQml 2.2
> - QtQml.Models 2.3 (++)
> - QtQuick 2.6 (++)
> - QtQuick.Particles 2.0
> - QtQuick.Controls 1.5 (++)
> - QtQuick.Layouts 1.3 (++)
> - QtQuick.Dialogs 1.2
You missed QtQuick.Window I think :)
... which brings me to this:
> Is thi
Tuukka:
Instead of pointing us at source code to inspect, maybe a youtube
video outlining in a more visual way your current plan of attack
and some of the considerations and issues andn goals that you feel are
relevant given your current state of research.
What are the Android vs IOS tradeoffs?
Hi all,
I'd like to propose that all QML imports that are part of the Qt Essentials
start following the respective Qt version number.
Let's take a look at the version history of some of the QtQml and QtQuick
imports.
### Qt 5.0
- QtQml 2.0
- QtQuick 2.0
- QtQuick.Particles 2.0
In the beginni
Robert,
That's a good idea. I think support for that could be added to
speech-dispatcher for the linux side, at least for some of the output
modules it supports. I'll see what we can do in that regard, but it
likely wont be until after the 5.6 technical preview. I would have
time to review patches
On Fri, Sep 18, 2015 at 3:48 PM, Robert Iakobashvili
wrote:
> On Fri, Sep 18, 2015 at 3:24 PM, Turunen Tuukka
> wrote:
>>
>> Hi,
>>
>> There has been quite little comments and feedback to the new speech APIs. It
>> would be great to have people to look into this and provide comments already
>>
On Fri, Sep 18, 2015 at 3:24 PM, Turunen Tuukka
wrote:
>
> Hi,
>
> There has been quite little comments and feedback to the new speech APIs. It
> would be great to have people to look into this and provide comments already
> during the early development. We hope to have a technology preview avai
On Donnerstag, 17. September 2015 09:15:06 CEST Thiago Macieira wrote:
> On Thursday 17 September 2015 15:27:44 Milian Wolff wrote:
> > +++ b/src/testlib/qtestaccessible.h
> >
> > @@ -126,7 +126,7 @@ public:
> > static void cleanup()
> > {
> >
> > delete instance();
> >
>
Hi,
There has been quite little comments and feedback to the new speech APIs. It
would be great to have people to look into this and provide comments already
during the early development. We hope to have a technology preview available
later this year, but getting feedback only after this phase
On 18/09/15 12:40, "Blasche Alexander"
wrote:
>
>
>From: Knoll Lars
>
>
>>void setPreferredSecurityFlags(QBluetooth::SecurityFlags flags);
>>QBluetooth::SecurityFlags preferredSecurityFlags() const;
>
>It would be a behavior change. Prior to this API we use
> On 17 Sep 2015, at 19:15, Dean Floyd wrote:
>
> Dear all,
>
> We have a project where we weak link our app against the Wacom framework
> which on MacOSX by default gets installed in:
>
> /Library/Frameworks/WacomMultiTouch.framework
>
> otool -L returns the following line for the Wacom lin
From: Knoll Lars
>void setPreferredSecurityFlags(QBluetooth::SecurityFlags flags);
>QBluetooth::SecurityFlags preferredSecurityFlags() const;
It would be a behavior change. Prior to this API we used one default way to
connect. On all platforms this happ
> On 18 Sep 2015, at 10:56, Knoll Lars wrote:
>
> On 18/09/15 10:49, "Gunnar Sletta" wrote:
>
>>
>>> On 18 Sep 2015, at 09:36, Knoll Lars
>>> wrote:
>>>
>>> New properties:
>>>
>>> QQuickFramebufferObject::mirrorVertically, looks ok
>>> QQuickPaintedItem::textureSize, not ok. It’s not vers
> On 18 Sep 2015, at 09:19, Knoll Lars wrote:
>
> Looks good to me, I assume the interface is for the backend, is that
> correct?
>
Yes that’s correct.
—
Yoann
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailma
On Fri, Sep 18, 2015 at 10:59 AM, Knoll Lars
wrote:
>
>
> On 18/09/15 10:55, "Albert Astals Cid" wrote:
>
>>On Fri, Sep 18, 2015 at 10:39 AM, Knoll Lars
>> wrote:
>>> On 18/09/15 09:59, "Albert Astals Cid"
>>>wrote:
>>>
On Fri, Sep 18, 2015 at 9:36 AM, Knoll Lars
wrote:
> New pr
Only new API is
void setPreferredSecurityFlags(QBluetooth::SecurityFlags flags);
QBluetooth::SecurityFlags preferredSecurityFlags() const;
API Looks good, but I’m wondering why the default on bluez is not Secure
as on the other platforms?
Cheers,
Lars
_
On 18/09/15 10:55, "Albert Astals Cid" wrote:
>On Fri, Sep 18, 2015 at 10:39 AM, Knoll Lars
> wrote:
>> On 18/09/15 09:59, "Albert Astals Cid"
>>wrote:
>>
>>>On Fri, Sep 18, 2015 at 9:36 AM, Knoll Lars
>>>
>>>wrote:
New properties:
QQuickFramebufferObject::mirrorVertically, look
On 18/09/15 10:49, "Gunnar Sletta" wrote:
>
>> On 18 Sep 2015, at 09:36, Knoll Lars
>>wrote:
>>
>> New properties:
>>
>> QQuickFramebufferObject::mirrorVertically, looks ok
>> QQuickPaintedItem::textureSize, not ok. It’s not versioned.
>
>Like QQuickFramebufferObject, the object is not instant
On Fri, Sep 18, 2015 at 10:39 AM, Knoll Lars
wrote:
> On 18/09/15 09:59, "Albert Astals Cid" wrote:
>
>>On Fri, Sep 18, 2015 at 9:36 AM, Knoll Lars
>>wrote:
>>> New properties:
>>>
>>> QQuickFramebufferObject::mirrorVertically, looks ok
>>> QQuickPaintedItem::textureSize, not ok. It’s not versio
> On 18 Sep 2015, at 09:36, Knoll Lars wrote:
>
> New properties:
>
> QQuickFramebufferObject::mirrorVertically, looks ok
> QQuickPaintedItem::textureSize, not ok. It’s not versioned.
Like QQuickFramebufferObject, the object is not instantiated from QML, so the
two follow the same pattern, no
On Fri, Sep 18, 2015 at 10:10 AM, André Somers wrote:
> Op 18-9-2015 om 09:59 schreef Albert Astals Cid:
>>
>>> New classes:
>>>
>>> * QQuickImageResponse
>>>
>>> Isn’t this class missing some way to get the status of the response? It
>>> only has an errorString() method, but no simple way to quer
On 18/09/15 09:59, "Albert Astals Cid" wrote:
>On Fri, Sep 18, 2015 at 9:36 AM, Knoll Lars
>wrote:
>> New properties:
>>
>> QQuickFramebufferObject::mirrorVertically, looks ok
>> QQuickPaintedItem::textureSize, not ok. It’s not versioned.
>>
>> New methods:
>>
>> * QQuickTextureFactory *textureF
On 18/09/15 10:10, "André Somers" wrote:
>Op 18-9-2015 om 09:59 schreef Albert Astals Cid:
>>
>>> New classes:
>>>
>>> * QQuickImageResponse
>>>
>>> Isn’t this class missing some way to get the status of the response? It
>>> only has an errorString() method, but no simple way to query whether it
Op 18-9-2015 om 09:59 schreef Albert Astals Cid:
>
>> New classes:
>>
>> * QQuickImageResponse
>>
>> Isn’t this class missing some way to get the status of the response? It
>> only has an errorString() method, but no simple way to query whether it
>> was successful or not when finished() gets emitt
On Fri, Sep 18, 2015 at 9:36 AM, Knoll Lars wrote:
> New properties:
>
> QQuickFramebufferObject::mirrorVertically, looks ok
> QQuickPaintedItem::textureSize, not ok. It’s not versioned.
>
> New methods:
>
> * QQuickTextureFactory *textureFactoryForImage(const QImage &image), docs
> not ok IMO.
W
No changes, looks good.
On 17/09/15 12:57, "Frederik Gladhorn"
wrote:
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
New properties:
QQuickFramebufferObject::mirrorVertically, looks ok
QQuickPaintedItem::textureSize, not ok. It’s not versioned.
New methods:
* QQuickTextureFactory *textureFactoryForImage(const QImage &image), docs
not ok IMO.
New classes:
* QQuickImageResponse
Isn’t this class missing some w
No new API. Nice change in qsqlindex.h :)
Looks good.
On 17/09/15 12:56, "Frederik Gladhorn"
wrote:
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
No new API, looks good.
On 17/09/15 12:56, "Frederik Gladhorn"
wrote:
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
No new API, looks good.
On 17/09/15 12:56, "Frederik Gladhorn"
wrote:
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
New enum QAudio::Role, an audio role property for QMediaPlayer and new
QAudioRoleControl interface.
Looks good to me, I assume the interface is for the backend, is that
correct?
Cheers,
Lars
___
Development mailing list
Development@qt-project.org
htt
Nothing new here.
On 17/09/15 12:55, "Frederik Gladhorn"
wrote:
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Looks good.
On 17/09/15 12:55, "Frederik Gladhorn"
wrote:
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Nothing new, looks good.
On 17/09/15 12:54, "Frederik Gladhorn"
wrote:
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Nothing new, looks good.
On 17/09/15 12:55, "Frederik Gladhorn"
wrote:
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Looks ok. Added move semantics and one new method. Created change
https://codereview.qt-project.org/#/c/125981/ to fix the docs of that
method.
Cheers,
Lars
On 17/09/15 12:55, "Frederik Gladhorn"
wrote:
>
___
Development mailing list
Development@qt-p
40 matches
Mail list logo
