Re: [Development] Diff between Qt-5.7.1 and Qt-5.8.0 on Android - Pointer Below the Cursor at Text Fields

[Robert Iakobashvili]

On Tue, Mar 21, 2017 at 4:06 PM, Olivier Goffart <oliv...@woboq.com> wrote:

> On Sonntag, 19. März 2017 09:39:57 CET Robert Iakobashvili wrote:
> > Nexus-7 with Android-6
> > The same Qt app built with 5.7.1 works properly
> > and with 5.8.0 appears a blue pointer down the cursor at text fields
> > (QTextEdit, QTextLine)
> >
> > The pointer is buggy and doesn't follow the cursor properly when
> positioning
> > and re-positioning child-windows/popups.
> How buggy?  Please report a bug on https://bugreports.qt.io
> I wonder if it's a bug with Android handles or with the widgets themself
> not
> reporting the proper cursor position.
> To be honest, i never tried widgets on a platform that have cursor handles.
>
> > How to get rid from it?
> Unfortunately there is no way.
> Maybe a input method hint should be added for it?
>
> > Were it some theme changes or something else from 5.7 to 5.8?
> > Thanks
> Yes, support for selection handle was added.
>
> --
> Olivier
>
> Woboq - Qt services and support - https://woboq.com -
> https://code.woboq.org
>
>
Dear Olivier,
Thank you for your kind reply so far the only one.

The pointer by itself is looking bad and detracts attention from the
writing done even if it is positioned properly.

Definitely, it should be arranged options:

- to get rid from the pointer (handles) completely;
- to change the image of the pointer like small image, NULL image, etc.

To reproduce the disastrous look,
one can use example of textedit in richedits, widgets.

I will try to come with my minimal example to reproduce
the issue with child widgets positioning and re-positioning over the parents
and file it via the bug reporting system.

Who is the maintainer today for the Qt-Android port?

Thank you.

Kind regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Dictation Issues with Qt-built software

[Robert Iakobashvili]

On Thu, Nov 10, 2016 at 10:47 AM, Morten Sorvig <morten.sor...@qt.io> wrote:
>
>> On 4 Nov 2016, at 13:00, Robert Iakobashvili <corobe...@gmail.com> wrote:
>>
>> Right. Most users of dictation are people with learning or motoric 
>> disabilities.
>>
>> When these users are used to a certain pattern of platform-specific habits
>> working for them, any other options to do the same could be seen as 
>> usability issues
>> breaking these habits.
>
>
> Hi, after some further investigation and offline discussion (thanks 
> Frederik!),
> I think we’re closer to solving this:
>
> Dictation input can be handled via our current input method support, where we
> implement the NSTextInputClient protocol. As a matter fact this almost works
> today (Qt 5.6): select text in a Qt text editor; starting dictation via the
> fn key should now work.
>
> So what we are looking at then is developing a bug fix to our 
> NSTextInputClient
> protocol implementation to make dictation work in all cases.
>
> Morten
>
Dear Morten,
Please, let me know when you have patches for 5.6.2.
I can apply them, rebuild and verify the fix for the common case.

Thanks!

Kind regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Dictation Issues with Qt-built software

[Robert Iakobashvili]

On Fri, Nov 4, 2016 at 1:51 PM, Morten Sorvig <morten.sor...@qt.io> wrote:

>
> > On 4 Nov 2016, at 09:53, Robert Iakobashvili <corobe...@gmail.com>
> wrote:
> >
> > On Thu, Nov 3, 2016 at 3:50 PM, Morten Sorvig <morten.sor...@qt.io>
> wrote:
> >>> People cannot dictate to Qt-software at Mac as filed:
> >>> https://bugreports.qt.io/browse/QTBUG-56811
> >>
> >> Hi,
> >>
> >> I see two possible ways to solve this:
> >>
> >> 1) Add cross-platform speech-to-text capabilities to Qt’s text input
> classes.
> >> This would be implemented using native API such as NSSpeechRecognizer,
> or an
> >> open source speech recognition library bundled with Qt. The behavior we
> get from
> >> this option may not be exactly native.
> >>
> >> 2) Use NSTextField in Qt applications. This gives us the exact native
> behavior,
> >> for speech recognition and everything else, including future NSTextEdit
> features.
> >> However, NSTextEdit would integrate on the QWindow level, and not for
> example
> >> as a Qt Quick scene graph item.
> >>
> >> Neither of these are straightforward, which is one reason why the bug
> remains
> >> open.
> >
> > Users are wondering why Qt-applications at Mac are not behaving like
> others.
> > They are expecting to be the same as TextEdit, Pages, Word, Safari,
> Firefox.
>
> Qt text edit support is more like the Google Docs editor in this regard; a
> custom
> implementation that may not support all native features. But I do agree
> that
> users are right in expecting that this should work.
>
> Morten


Right. Most users of dictation are people with learning or motoric
disabilities.

When these users are used to a certain pattern of platform-specific habits
working for them, any other options to do the same could be seen as
usability issues
breaking these habits.

Kind regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Dictation Issues with Qt-built software

[Robert Iakobashvili]

On Thu, Nov 3, 2016 at 3:50 PM, Morten Sorvig  wrote:
>> People cannot dictate to Qt-software at Mac as filed:
>> https://bugreports.qt.io/browse/QTBUG-56811
>
> Hi,
>
> I see two possible ways to solve this:
>
> 1) Add cross-platform speech-to-text capabilities to Qt’s text input classes.
> This would be implemented using native API such as NSSpeechRecognizer, or an
> open source speech recognition library bundled with Qt. The behavior we get 
> from
> this option may not be exactly native.
>
> 2) Use NSTextField in Qt applications. This gives us the exact native 
> behavior,
> for speech recognition and everything else, including future NSTextEdit 
> features.
> However, NSTextEdit would integrate on the QWindow level, and not for example
> as a Qt Quick scene graph item.
>
> Neither of these are straightforward, which is one reason why the bug remains
> open.

Users are wondering why Qt-applications at Mac are not behaving like others.
They are expecting to be the same as TextEdit, Pages, Word, Safari, Firefox.

Just dictate the same way with the same microphone window coming, etc.

Since Apple's future behavior is not predictable, I'd vote for as more
native approach
as it could be done.

>> is because a similar previous dictation related issue at Windows filed in 
>> 2014
>> is still pending without being resolved:
>>
>> https://bugreports.qt.io/browse/QTBUG-43046
>
> This is an iOS (not Windows) bug. Also worth looking at though :)

There is a dictation issue at Windows as well.
When dictating at Window-7 using native capabilities, text to speech
to QTextEdit was normal, but
giving any dictation-api commands like changing a word, deleting, etc.
is broken.

If somebody indeed is planning to try to fix it,
I will sit on that to create a good bug report.

> In general a good way to improve and maintain the accessibility implementation
> in Qt would be to give it a second user. UI testing and automation comes to
> mind as a good candidate.

Sorry, I do not understand.
The issues are easily reproducible.

>
> Morten
>

Thank you for your attention.

Sincerely,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Dictation Issues with Qt-built software

[Robert Iakobashvili]

Dear Qt-Management and Developers,

People cannot dictate to Qt-software at Mac as filed:

https://bugreports.qt.io/browse/QTBUG-56811

The very reason to bother you and write this email
is because a similar previous dictation related issue at Windows filed in 2014
is still pending without being resolved:

https://bugreports.qt.io/browse/QTBUG-43046

Dictation on Mac and Windows platforms is improving, and
it is vital as the input method for many people with
dyslexia, dysgraphia and motoric disorders.

Fixing these issues is not something that is supposed
to bring high profits; notwithstanding, I hope that it could get priority.

Thank you in advance.

Kind regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] HEADS UP: OSX build requirements for 5.7

[Robert Iakobashvili]

On Wed, Feb 10, 2016 at 1:00 PM, Tor Arne Vestbø
 wrote:
> Hey guys!
>
> To clear up some resources in our CI system we're moving to the following
> build process:
>
> - Build Qt on the latest OS X with the latest Xcode against the latest SDK
> available.
> - Test that build by running the auto-tests on each of the supported
> deployment targets, down to the minimum deployment target we support (which
> for the time being is 10.7).
>
> This means that we can save build time by not building Qt on those lower OS
> X versions, just running the tests there. It also means we can start
> removing SDK ifdefs in our code, since Qt should always be built against the
> latest available SDK.
>
> This is the approach recommended by Apple, and the one we've been applying
> to the iOS port in the past.
>
> Does anyone see any issues with this going forward?
>
> Tor Arne
> ___

Dear Tor Arne,
Apple has a traditional October-November mess after releasing
new versions with issues, bugs, patches that goes normally up to end-of year.

So, it could be that practically makes sense to keep
in autumn a previous version as well at least for a transition period
of several months.

Kind regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Minimum Deployment Platforms for 5.7 onwards?

[Robert Iakobashvili]

Yes, Gian, you are right.

iTunes delivers updates only to the users with appropriate iOS version.

And users with older iOS could be told to upgrade their hardware.
When they get a newer HW, they can get the updated software
in due course.

Thanks for clarifying it.

Kind regards,
Robert

On Fri, Jan 8, 2016 at 12:58 PM, Gian Maxera <gmax...@gmail.com> wrote:

> Dear Robert,
> are you sure the apple store force to keep compatibility of the very first
> iOS version ??
> From what I know, you can drop compatibility of older iOS version when you
> release a new version on the app store.
> And when someone install your app in an older phone, a popup appear
> warning the user that will be installed an older version because the last
> version of the app required a more recent iOS.
>
> Ciao,
> Gianluca.
>
>
> On 8 Jan 2016, at 10:50, Robert Iakobashvili <corobe...@gmail.com> wrote:
>
> Dear Jake,
> Unless app developers would like to drop their existing apps
> and rename/launch instead new apps,
> they're forced to keep compatibility with the very first iOS-version
> when their app was accepted to iTunes Store.
>
> So, dropping iOS-6 is a not issue for me, but dropping iOS-7 - yes.
>
> jm2c
>
> Kind regards,
> Robert
>
> On Fri, Jan 8, 2016 at 12:24 PM, Petroules Jake <
> jake.petrou...@theqtcompany.com> wrote:
>
>> We're raising the minimum OS X to 10.8 (2012). The iOS minimum is still 6
>> (also 2012), but I wonder whether we should also raise that a version (or
>> even two) considering its uniquely rapid upgrade cycle (frequently upgraded
>> hardware, less user ability to opt out of software updates).
>>
>> Bumping it to iOS 8 would also allow us to stop making static builds and
>> thus gain support for App Extensions.
>>
>> Thoughts? Tor Arne?
>> --
>> Jake Petroules - jake.petrou...@theqtcompany.com
>> Consulting Services Engineer - The Qt Company
>>
>> From: Development <development-boun...@qt-project.org> on behalf of
>> Turunen Tuukka <tuukka.turu...@theqtcompany.com>
>> Date: Thursday, January 7, 2016 at 11:18 PM
>> To: John Layt <jl...@kde.org>, "development@qt-project.org" <
>> development@qt-project.org>
>> Subject: Re: [Development] Minimum Deployment Platforms for 5.7 onwards?
>>
>>
>>
>> Hi John,
>>
>>
>>
>> This item was discussed at Qt Contributor’s Summit, please see session
>> notes: http://wiki.qt.io/QtCS2015_LTS
>>
>>
>>
>> For compilers this is also documented to the Qt Base change log:
>> http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.5.1
>>
>>
>>
>> For 5.6 the current list of supported platforms and compilers is the
>> following: http://wiki.qt.io/Qt-5.6.0-tools-and-versions (note that we
>> are working to add OS X 10.11 to CI and fully support it)
>>
>>
>>
>> The idea is that by making Qt 5.6 LTS, we gain more freedom to drop older
>> (non-c++11) compilers as well as older platforms from Qt 5.7 and subsequent
>> versions. Those who have such older platforms to support, are recommended
>> to stay with the LTS version for a while. This approach allows us to move
>> faster for new features planned for future Qt releases.
>>
>>
>>
>> For application developers the documentation is often the best source to
>> find the list of supported platforms:
>> http://doc.qt.io/QtSupportedPlatforms/index.html This has not yet been
>> updated to 5.6, but will be before the final release.
>>
>>
>>
>> Yours,
>>
>>
>>
>>   Tuukka
>>
>>
>>
>>
>>
>>
>>
>> *From:* Development [mailto:development-boun...@qt-project.org
>> <development-boun...@qt-project.org>] *On Behalf Of *John Layt
>> *Sent:* keskiviikkona 30. joulukuuta 2015 20.43
>> *To:* development@qt-project.org
>> *Subject:* [Development] Minimum Deployment Platforms for 5.7 onwards?
>>
>>
>>
>> Hi,
>>
>> Can I just clarify what the minimum deployment platforms are for 5.7
>> onwards? That is, the lowest version of each OS that the code must still
>> run on? Far as I can tell it's something like:
>>
>> Windows 7 (or Vista?)
>>
>> Windows Embedded Compact 2013
>>
>> OSX 10.8
>>
>> iOS 5.0?
>>
>> Android 4.1 (API Level 16)?
>>
>> RHEL 6.6
>>
>> Ubuntu 11.10?
>>
>> There really should be a wiki page for this...
>>
>>
>>
>> Cheers!
>>
>> John.
>>
>> ___
>> Development mailing list
>> Development@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>>
>>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Minimum Deployment Platforms for 5.7 onwards?

[Robert Iakobashvili]

Dear Jake,
Unless app developers would like to drop their existing apps
and rename/launch instead new apps,
they're forced to keep compatibility with the very first iOS-version
when their app was accepted to iTunes Store.

So, dropping iOS-6 is a not issue for me, but dropping iOS-7 - yes.

jm2c

Kind regards,
Robert

On Fri, Jan 8, 2016 at 12:24 PM, Petroules Jake <
jake.petrou...@theqtcompany.com> wrote:

> We're raising the minimum OS X to 10.8 (2012). The iOS minimum is still 6
> (also 2012), but I wonder whether we should also raise that a version (or
> even two) considering its uniquely rapid upgrade cycle (frequently upgraded
> hardware, less user ability to opt out of software updates).
>
> Bumping it to iOS 8 would also allow us to stop making static builds and
> thus gain support for App Extensions.
>
> Thoughts? Tor Arne?
> --
> Jake Petroules - jake.petrou...@theqtcompany.com
> Consulting Services Engineer - The Qt Company
>
> From: Development  on behalf of
> Turunen Tuukka 
> Date: Thursday, January 7, 2016 at 11:18 PM
> To: John Layt , "development@qt-project.org" <
> development@qt-project.org>
> Subject: Re: [Development] Minimum Deployment Platforms for 5.7 onwards?
>
>
>
> Hi John,
>
>
>
> This item was discussed at Qt Contributor’s Summit, please see session
> notes: http://wiki.qt.io/QtCS2015_LTS
>
>
>
> For compilers this is also documented to the Qt Base change log:
> http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.5.1
>
>
>
> For 5.6 the current list of supported platforms and compilers is the
> following: http://wiki.qt.io/Qt-5.6.0-tools-and-versions (note that we
> are working to add OS X 10.11 to CI and fully support it)
>
>
>
> The idea is that by making Qt 5.6 LTS, we gain more freedom to drop older
> (non-c++11) compilers as well as older platforms from Qt 5.7 and subsequent
> versions. Those who have such older platforms to support, are recommended
> to stay with the LTS version for a while. This approach allows us to move
> faster for new features planned for future Qt releases.
>
>
>
> For application developers the documentation is often the best source to
> find the list of supported platforms:
> http://doc.qt.io/QtSupportedPlatforms/index.html This has not yet been
> updated to 5.6, but will be before the final release.
>
>
>
> Yours,
>
>
>
>   Tuukka
>
>
>
>
>
>
>
> *From:* Development [mailto:development-boun...@qt-project.org
> ] *On Behalf Of *John Layt
> *Sent:* keskiviikkona 30. joulukuuta 2015 20.43
> *To:* development@qt-project.org
> *Subject:* [Development] Minimum Deployment Platforms for 5.7 onwards?
>
>
>
> Hi,
>
> Can I just clarify what the minimum deployment platforms are for 5.7
> onwards? That is, the lowest version of each OS that the code must still
> run on? Far as I can tell it's something like:
>
> Windows 7 (or Vista?)
>
> Windows Embedded Compact 2013
>
> OSX 10.8
>
> iOS 5.0?
>
> Android 4.1 (API Level 16)?
>
> RHEL 6.6
>
> Ubuntu 11.10?
>
> There really should be a wiki page for this...
>
>
>
> Cheers!
>
> John.
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt Platform Menu on iOS - Differences 5.4 -> 5.5

[Robert Iakobashvili]

Gentlemen,

Making custom Qt Platform Menu on iOS as advised by Richard Moe
(https://bugreports.qt.io/browse/QTBUG-41275)
was working fine with Qt-5.4 on iOS 7, 8 and the recent 9.

After upgrading to Qt-5.5, I'm getting all iOS-standard menu items
additionally to my menu items, tested on iOS-9.0.2.

Is there any API to get rid from from the standard iOS menu items?
Thanks!

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5.5 accessibility of QLineEdit and QTextEdit

[Robert Iakobashvili]

FYI,

QTBUG-43046 - iOS: Accessibility for QTextEdit, QComboBox, Etc. with
VoiceOver Isn't Working
QTBUG-45980 QTextEdit and QLineEdit - Windows Speech Recognition (WSR)
Words-Related Commands Not Working


Regards,
Robert


On Mon, Sep 28, 2015 at 10:16 PM, Frederik Gladhorn
 wrote:
> Hello Germano,
>
> which platform are you on and how do you get Qt (packages/build yourself)?
> In general QWidgets like QLineEdit and QTextEdit should work on all platforms.
> It would be great if you could try C++ examples, if they work, it might be
> something with the bindings.
>
> Cheers,
> Frederik
>
> On Friday, September 18, 2015 09:49:33 PM germano carella wrote:
>> 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 make it accessible to screen readers?
>> Thanks"!
>> ___
>> Development mailing list
>> Development@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.5.1 'rc' available

[Robert Iakobashvili]

Thank you.

Regards,
Robert


On Thu, Sep 24, 2015 at 11:26 AM, Heikkinen Jani
 wrote:
> Src packages now in http://download.qt.io/snapshots/qt/5.5/5.5.1/latest_src/
>
> Br,
> Jani
>
>>>-Original Message-
>>>From: development-bounces+jani.heikkinen=theqtcompany.com@qt-
>>>project.org [mailto:development-
>>>bounces+jani.heikkinen=theqtcompany@qt-project.org] On Behalf Of
>>>Thiago Macieira
>>>Sent: 23. syyskuuta 2015 22:50
>>>To: development@qt-project.org
>>>Subject: Re: [Development] Qt 5.5.1 'rc' available
>>>
>>>On Wednesday 23 September 2015 08:37:54 Heikkinen Jani wrote:
 Hi all,


 We have finally new Qt 5.5.1 snapshot
 available


 Windows: http://download.qt.io/snapshots/qt/5.5/5.5.1/153/

 Linux: http://download.qt.io/snapshots/qt/5.5/5.5.1/190/

 Mac: http://download.qt.io/snapshots/qt/5.5/5.5.1/142/
>>>
>>>Source is missing. Can't test.
>>>
 We are targeting to release Qt 5.5.1 as soon as possible, most probably
 during next week. These packages are almost final ones, only two changes
 are still coming in (https://codereview.qt-project.org/#/c/126113/ &
 https://codereview.qt-project.org/#/c/126204/)
>>>
>>>Those two changes do not affect the binaries. One is a changelog and the 
>>>other
>>>affects only ICC on Windows. Neither change should affect our regular 
>>>testing.
>>>
 so please test these
 packages carefully and inform me immediately if you find something which
 should block the release. And remember, we aren't updating the packages
 because of any nice-to-have issue anymore...
>>>
>>>--
>>>Thiago Macieira - thiago.macieira (AT) intel.com
>>>  Software Architect - Intel Open Source Technology Center
>>>
>>>___
>>>Development mailing list
>>>Development@qt-project.org
>>>http://lists.qt-project.org/mailman/listinfo/development
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] RFC: Speech Recognition API

[Robert Iakobashvili]

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 available 
> later this year, but getting feedback only after this phase is not optimal. 
> Even if you are not an expert on speech recognition, but just interested in 
> it, please take a look and provide feedback to Tuomas and others developing 
> this.
>
> Yours,
>
> Tuukka

Hello,
Thank you for the great and valued module you are developing
that is a very good start.

The major feature still out is the ability to register callbacks for the
end of word (token) and the end of speech.

Mac OSX, iOS and Windows have such API whereas Android has
only partial and Linux ...

The feature is necessary to be knowledgeable when a word spoken is completed
and when the phrase sent to speech is completed.

Thank you once more!

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] RFC: Speech Recognition API

[Robert Iakobashvili]

On Fri, Sep 18, 2015 at 3:48 PM, Robert Iakobashvili
<corobe...@gmail.com> wrote:
> On Fri, Sep 18, 2015 at 3:24 PM, Turunen Tuukka
> <tuukka.turu...@theqtcompany.com> 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 available 
>> later this year, but getting feedback only after this phase is not optimal. 
>> Even if you are not an expert on speech recognition, but just interested in 
>> it, please take a look and provide feedback to Tuomas and others developing 
>> this.
>>
>> Yours,
>>
>> Tuukka
>
> Hello,
> Thank you for the great and valued module you are developing
> that is a very good start.
>
> The major feature still out is the ability to register callbacks for the
> end of word (token) and the end of speech.
>
> Mac OSX, iOS and Windows have such API whereas Android has
> only partial and Linux ...
>
> The feature is necessary to be knowledgeable when a word spoken is completed
> and when the phrase sent to speech is completed.
>
> Thank you once more!
>
> Regards,
> Robert

Sorry, the above comments were for Text-to-Speech API.

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt at iOS - Issues Issues Opened for a While

[Robert Iakobashvili]

Dear Qt-iOS-Maintainers,

I was an early adapter of Qt-port for iOS (since Qt-5.2, 5.3)
and most issues opened have been fixed, thanks to
Richard Moe, Tor Arne and other developers,
whereas the 2 below are still remaining opened:

1. QTBUG-43176 - although P3, there's no workaround
and it creates very serious usability problems;

2. QTBUG-42705 - a P2 issue related to integration with
native windows with a workaround recommended by Richard.

Could you please consider fixing the above issues in your development plans?

Thank you in advance.

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.5 for Android - More Regressions Since 5.3

[Robert Iakobashvili]

thanks
Regards,
Robert


On Mon, Aug 3, 2015 at 11:39 AM, BogDan bog_dan...@yahoo.com wrote:
 Hi,

 In order to see in which version they will be included, you need to check on
 each bug its Fix/Version(s) label.
 QTBUG-44337 is still not closed yet, I'm waiting for some folks to reply
 (check https://codereview.qt-project.org/#/c/120725/ ).

 I didn't had time to check QProgressDialog bug. I'm afraid I'll not have
 soon because this bug has a low priority on my list ...

 Cheers,
 BogDan.





 On Monday, August 3, 2015 9:04 AM, Robert Iakobashvili corobe...@gmail.com
 wrote:


 Dear BogDan,
 Thank you for the 2 regressions being fixed.

 Should the fixes appear in 5.5.1?

 Sorry to bother you but it seems that the issue with QProgressDialog
 wasn't treated:
 QTBUG-47049

 [REG 5.4 - 5.5] QProgressDialog is Shown Immediately After Allocation
 and Even Despite hide() Call.

 Thank you.

 Regards,
 Robert


 On Mon, Jul 6, 2015 at 11:37 AM, Robert Iakobashvili
 corobe...@gmail.com wrote:
 Thanks, BogDan.

 QTBUG-47049

 [REG 5.4 - 5.5] QProgressDialog is Shown Immediately After Allocation
 and Even Despite hide() Call.


 Regards,
 Robert


 On Mon, Jul 6, 2015 at 10:31 AM, BogDan bog_dan...@yahoo.com wrote:
 Hi,

 1  2. I can reproduce it, I'll try to fix it soon (though it will be
 quite
 hard to make them look good on Android).
 3. Yep, please create a bug report.

 Cheers,
 BogDan.



 On Monday, July 6, 2015 9:50 AM, Robert Iakobashvili
 corobe...@gmail.com
 wrote:


 Hi,

 Trying Qt-5.5 for Android, the following regressions since
 Qt-5.3 are still inside and break it:

 1. QTBUG-44337 -

 [REG 5.3-5.4] Android: QFileDialog for Save Keeps Save Button Disabled
 until the filename contains a dot

 2. QTBUG-44271 -

 [REG 5.3 - 5.4] Android: QFontComboBox Broken


 and even worse:

 3. QProgressDialog instances are shown immediately on allocation
 and even explicit hide is not helping (Android 4.4.2, Nexus-7-2013)
 This is a regression since 5.4

 Does anybody cares? If yes, I will open the issue.


 In Qt-5.3.1 all the above was working properly.

 IMHO, Qt for iOS and Android requires serious go for stability
 instead the current run for more and fancy features.

 Still, it might be that my visibility is limited and other people
 do not feel so or sales consideration require more features ASAP
 and do not care the quality.

 Thank you.

 Regards,
 Robert
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development




___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.5 for Android - More Regressions Since 5.3

[Robert Iakobashvili]

Dear BogDan,
Thank you for the 2 regressions being fixed.

Should the fixes appear in 5.5.1?

Sorry to bother you but it seems that the issue with QProgressDialog
wasn't treated:
QTBUG-47049

[REG 5.4 - 5.5] QProgressDialog is Shown Immediately After Allocation
and Even Despite hide() Call.

Thank you.

Regards,
Robert


On Mon, Jul 6, 2015 at 11:37 AM, Robert Iakobashvili
corobe...@gmail.com wrote:
 Thanks, BogDan.

 QTBUG-47049

 [REG 5.4 - 5.5] QProgressDialog is Shown Immediately After Allocation
 and Even Despite hide() Call.


 Regards,
 Robert


 On Mon, Jul 6, 2015 at 10:31 AM, BogDan bog_dan...@yahoo.com wrote:
 Hi,

 1  2. I can reproduce it, I'll try to fix it soon (though it will be quite
 hard to make them look good on Android).
 3. Yep, please create a bug report.

 Cheers,
 BogDan.



 On Monday, July 6, 2015 9:50 AM, Robert Iakobashvili corobe...@gmail.com
 wrote:


 Hi,

 Trying Qt-5.5 for Android, the following regressions since
 Qt-5.3 are still inside and break it:

 1. QTBUG-44337 -

 [REG 5.3-5.4] Android: QFileDialog for Save Keeps Save Button Disabled
 until the filename contains a dot

 2. QTBUG-44271 -

 [REG 5.3 - 5.4] Android: QFontComboBox Broken


 and even worse:

 3. QProgressDialog instances are shown immediately on allocation
 and even explicit hide is not helping (Android 4.4.2, Nexus-7-2013)
 This is a regression since 5.4

 Does anybody cares? If yes, I will open the issue.


 In Qt-5.3.1 all the above was working properly.

 IMHO, Qt for iOS and Android requires serious go for stability
 instead the current run for more and fancy features.

 Still, it might be that my visibility is limited and other people
 do not feel so or sales consideration require more features ASAP
 and do not care the quality.

 Thank you.

 Regards,
 Robert
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Backwards compatibiltiy break in Qt 5.5

[Robert Iakobashvili]

On Tue, Jul 28, 2015 at 11:48 AM, Marc Mutz marc.m...@kdab.com wrote:
 On Monday 27 July 2015 20:44:48 Thiago Macieira wrote:
 On Monday 27 July 2015 21:41:44 NIkolai Marchenko wrote:
  Yes,but this requires making override visible in every file of the
  project.

 We can solve this by having a global #ifdef that can change the setting.

 Or an environment variable, so you don't have to recompile the world...

 --
 Marc Mutz marc.m...@kdab.com | Senior Software Engineer
 KDAB (Deutschland) GmbH  Co.KG, a KDAB Group Company
 Tel: +49-30-521325470
 KDAB - The Qt Experts

Yes, it's a good idea to have an environment variable or
a pre-processing flag to preserve the existing behavior.

In Qt 5.* the default could be the old behavior,
and in Qt 6 - the new.

jm2c to add.

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.5 for Android - More Regressions Since 5.3

[Robert Iakobashvili]

Thanks, BogDan.

QTBUG-47049

[REG 5.4 - 5.5] QProgressDialog is Shown Immediately After Allocation
and Even Despite hide() Call.


Regards,
Robert


On Mon, Jul 6, 2015 at 10:31 AM, BogDan bog_dan...@yahoo.com wrote:
 Hi,

 1  2. I can reproduce it, I'll try to fix it soon (though it will be quite
 hard to make them look good on Android).
 3. Yep, please create a bug report.

 Cheers,
 BogDan.



 On Monday, July 6, 2015 9:50 AM, Robert Iakobashvili corobe...@gmail.com
 wrote:


 Hi,

 Trying Qt-5.5 for Android, the following regressions since
 Qt-5.3 are still inside and break it:

 1. QTBUG-44337 -

 [REG 5.3-5.4] Android: QFileDialog for Save Keeps Save Button Disabled
 until the filename contains a dot

 2. QTBUG-44271 -

 [REG 5.3 - 5.4] Android: QFontComboBox Broken


 and even worse:

 3. QProgressDialog instances are shown immediately on allocation
 and even explicit hide is not helping (Android 4.4.2, Nexus-7-2013)
 This is a regression since 5.4

 Does anybody cares? If yes, I will open the issue.


 In Qt-5.3.1 all the above was working properly.

 IMHO, Qt for iOS and Android requires serious go for stability
 instead the current run for more and fancy features.

 Still, it might be that my visibility is limited and other people
 do not feel so or sales consideration require more features ASAP
 and do not care the quality.

 Thank you.

 Regards,
 Robert
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt 5.5 for Android - More Regressions Since 5.3

[Robert Iakobashvili]

Hi,

Trying Qt-5.5 for Android, the following regressions since
Qt-5.3 are still inside and break it:

1. QTBUG-44337 -

[REG 5.3-5.4] Android: QFileDialog for Save Keeps Save Button Disabled
until the filename contains a dot

2. QTBUG-44271 -

[REG 5.3 - 5.4] Android: QFontComboBox Broken


and even worse:

3. QProgressDialog instances are shown immediately on allocation
and even explicit hide is not helping (Android 4.4.2, Nexus-7-2013)
This is a regression since 5.4

Does anybody cares? If yes, I will open the issue.


In Qt-5.3.1 all the above was working properly.

IMHO, Qt for iOS and Android requires serious go for stability
instead the current run for more and fancy features.

Still, it might be that my visibility is limited and other people
do not feel so or sales consideration require more features ASAP
and do not care the quality.

Thank you.

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt for iOS: API to pass Application Name to UIApplicationMain

[Robert Iakobashvili]

Hi,
To develop and use application-specific class for
an application instead the default UIApplication,
user may wish to pass the name of an UIApplication derivative
to iOS in UIApplicationMain

In qioseventdispatcher.mm nil is passed as the 3-rd argument:

return UIApplicationMain(argc, argv, nil,
NSStringFromClass([QIOSApplicationDelegate class]));

Is there any other way to pass the name of application-specific
derivative of UIApplication besides patching the sources?

Thank you in advance.

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] iOS: Fn-F1 - Fn-F12 Keys Ain't Functional

[Robert Iakobashvili]

Hi,
The issue is described in:

https://bugreports.qt.io/browse/QTBUG-43355

Qt 5 properly delivers F-key events at Android, Windows, Mac, Linux, but
not on iOS.

Is this something specific about iOS?

If not, where is the place in the code
to start digging in?

Thank you.

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt 5.4 Accessibility with QLineEdit and QTextEdit: Windows Dictation (WSR) Commands Ain't Working

[Robert Iakobashvili]

Hi,
When using Windows Native dictation (Windows Speech Recognition) in
Qt 5.4 examples using QLineEdit and QTextEdit widgets,
dictation works properly, but not word-related commands like:
- Select word;
- Correct word

There are issues also with sentence-related commands.

There are no such issues with Notepad, WordPad
and Word-2010.

It was first used:

1. Setup including Microphone Training, Voice Training, etc


rundll32.exe %windir%\system32\speech\speechux\SpeechUX.dll,
RunWizard UserEnrollment (Set Up Speech Recognition)


2. Tutorial

rundll32.exe %windir%\system32\speech\speechux\SpeechUX.dll,
RunWizard Tutorial (Speech Recognition Tutorial)



3. WSR was run as

Speech Recognition floating window (WSR):

%windir%\speech\common\sapisvr.exe -SpeechUX


Is there some configuration to be done on

Qt-side or is it a known issue?


Thanks.

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Allowing event delivery prior to and after QCoreApplication

[Robert Iakobashvili]

On Tue, Apr 14, 2015 at 6:27 PM, Thiago Macieira
thiago.macie...@intel.com wrote:
 On Tuesday 14 April 2015 16:56:19 René J.V. Bertin wrote:
 [cut]
 ObjC is so intricately linked to OS X, because from a few quick attempts it
 seems to be perfectly possible to use an ObjC++ wrapper class to extend the
 retain/release scheme to C++ classes.

 Is this clear enough?

 Yes, thank you.

 C++ already has that, it's called reference counting. You may have heard we
 use it in Qt :-)

 The problem here is that QCoreApplication is not reference counted and we
 can't change it without breaking *every* *single* *application*, since this is
 what people usually do:

 int main(int argc, char **argv)
 {
 SomeApplication app(argc, argv);
 [rest of the application]
 }

 That stack declaration is the problem here. The app object will be destroyed
 at the closing brace, whether we want it or not, and there's nothing we can do
 to prevent it, delay it or even hook something as it begins.

 We can only catch it half-way through, when the destruction has reached one of
 our classes (~QApplication, ~QGuiApplication or ~QCoreApplication), by which
 time the virtual table has already changed and it's too late.

C++ idiom with protected destructor
enforces heap-allocation of objects and prevents stack allocation.
It requires some public destroy() calling delete this inside.

jm2c

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QML bindings for native Android controls

[Robert Iakobashvili]

On Sun, Apr 12, 2015 at 11:45 AM, Nurmi J-P jpnu...@theqtcompany.com wrote:
 Hello,

 I'd like to request a playground repository for the former hackathon project 
 of mine: QML bindings for native Android controls - 
 https://youtu.be/Mo8J-g5XPGQ

 Before proceeding to a formal request, the baby needs a name. I was hoping 
 you could help me choose one.

 Factors that affect the naming:
 - This is not cross-platform, but highly Android specific. The convenience of 
 QML and and full access to the underlying platform APIs combined.
 - This is not integrated with Qt Quick. Only QML engine  native controls 
 (via JNI) are used. Gives great performance with 100% perfect native behavior.

 Credits for the groundwork go to Attila Csipa
 - http://achipa.blogspot.no/2014/11/qml-wrappers-for-native-android.html
 - http://achipa.blogspot.no/2014/11/native-ui-in-qt-on-android-without.html

 --
 J-P Nurmi

It looks cool!

QtBuzzDroid
CuteBuzzDroid

jm2c

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt for iOS: Management Retina vs Non-Retina Images

[Robert Iakobashvili]

On Thu, Feb 19, 2015 at 3:03 PM, Sorvig Morten
morten.sor...@theqtcompany.com wrote:

 On 18 Feb 2015, at 10:59, Robert Iakobashvili corobe...@gmail.com wrote:

 What about support for @3x?
 Is it inside or is it planned?

 I’ve started implementing @3x support here:

 https://codereview.qt-project.org/106717
 https://codereview.qt-project.org/106705

 There’s some refactoring work to be done as well to reduce the logic 
 duplication.

 Morten

The first patch (106717) was applied to 4.4.0 and 4.4.1 and found to
be working great
for iPhone-6-plus target with 3x images as well as for older targets
with 2x images.

Thank you very much

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt for iOS: Management Retina vs Non-Retina Images

[Robert Iakobashvili]

On Thu, Feb 19, 2015 at 3:03 PM, Sorvig Morten
morten.sor...@theqtcompany.com wrote:

 On 18 Feb 2015, at 10:59, Robert Iakobashvili corobe...@gmail.com wrote:

 What about support for @3x?
 Is it inside or is it planned?

 I’ve started implementing @3x support here:

 https://codereview.qt-project.org/106717
 https://codereview.qt-project.org/106705

 There’s some refactoring work to be done as well to reduce the logic 
 duplication.

 Morten

Looks great. Thank you.

Is it something to be coming only in 5.5 or could
be expected in 5.4.2 as well?

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt for iOS: Management Retina vs Non-Retina Images

[Robert Iakobashvili]

On Wed, Oct 8, 2014 at 2:56 PM, Ziller Eike
eike.zil...@theqtcompany.com wrote:
 On Oct 8, 2014, at 1:36 PM, Thiago A. Corrêa thiago.cor...@gmail.com wrote:

 On Wed, Oct 8, 2014 at 5:10 AM, Ziller Eike
 eike.zil...@theqtcompany.com wrote:

 QIcon does automatic loading of @2x images afair. QPixmap and QImage only 
 set the devicePixelRatio corresponding to the file name automatically, but 
 you have to define yourself if you want to load a @2x or not.


 This behavior isn't documented in QIcon[1].

 It actually is in 5.4:
 http://doc-snapshot.qt-project.org/qt5-5.4/qicon.html#addFile

 Eike Ziller, Senior Software Engineer - Digia, Qt

The doc says:

If a high resolution version of the image exists (identified by the
suffix @2x on the base name),
it is automatically loaded and added with the device pixel ratio set
to a value of 2. 

What about support for @3x?
Is it inside or is it planned?

Thanks

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Running Qt 5.4.0 Applicationat Mac 10.6

[Robert Iakobashvili]

Hello,

Qt-5.4.0 was built from sources at 10.9 build machine
with flag -no-c++11
and in qtbase/mkspecs/macx-clang/qmake.conf
was set:
QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.6

The application does run at 10.6 target but crashes:

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   org.qt-project.QtWidgets0x000100fcb762 0x100fbe000 +
55138
1   org.qt-project.QtWidgets0x0001010589f5
QStyleFactory::create(QString const) + 181
2   org.qt-project.QtWidgets0x000100fec2d2
QApplication::style() + 370
3   org.qt-project.QtWidgets0x000100feb624
QApplicationPrivate::initializ
e() + 100
4   org.qt-project.QtWidgets0x000100feb460
QApplicationPrivate::construct() + 96
5   com.mydomain.MyApp   0x0001b7b9 main + 41
6   com.mydomain.MyApp  0x00015e74 start + 52

It seems that QStyle returns 0.

Should I create some style in advance and pass it to application?
Which style could be appropriate for 10.6?

Yes, I know that 10.6 is not a supported target for 5.4.0,
but any advise or direction would be very much appreciated.

Thank you in advance.

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Running Qt 5.4.0 Applicationat Mac 10.6

[Robert Iakobashvili]

Dear Morten,
Thank you very much!

Sincerely,
Robert

On Mon, Jan 26, 2015 at 10:53 AM, Sorvig Morten 
morten.sor...@theqtcompany.com wrote:


  On 26 Jan 2015, at 09:09, Robert Iakobashvili corobe...@gmail.com
 wrote:
 
  It seems that QStyle returns 0.
 
  Should I create some style in advance and pass it to application?
  Which style could be appropriate for 10.6?
 
  Yes, I know that 10.6 is not a supported target for 5.4.0,
  but any advise or direction would be very much appreciated.
 
  Thank you in advance.

 The code paths that provide 10.6 support have been removed from Qt 5.4.
 The commits I am aware of are:

 a198ce8d (QMacStyle)
 fc11798e8 (QMacStyle)
 9c92a18b (QCoreWLanEngine)

 You could use the fusion style to avoid QMacStyle, but there would still
 be no guarantee that the application runs. Your other option then is to
 revert the changes that removes 10.6 support on your local copy of the Qt
 source code.

 Morten
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] New Qt5.4 snapshot available

[Robert Iakobashvili]

On Mon, Oct 27, 2014 at 7:27 PM, Alex Montgomery apmontgom...@gmail.com
wrote:

 Are source packages somehow harder to make than packages for particular
 platforms? Many of the people who would bother trying out a beta have
 special needs like maintaining their own patches or static linking and it
 is annoying to have to resort to git. Would it be possible to make source
 packages available at every stage of the beta release process?


+1 for source snapshots.

Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] iOS with current 5.4 git

[Robert Iakobashvili]

Gentlemen,
With 5.4 taken yesterday (and all recent commits are seen in log),
somehow QTBUG-39981 issues are still inside, updated,
and QTBUG-41275 was reopened.
Thanks.
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Important OSX 10.9.5 10.10 codesign changes

[Robert Iakobashvili]

Many thanks for your tip!

On Wed, Oct 8, 2014 at 10:08 AM, Ziller Eike
eike.zil...@theqtcompany.com wrote:

 On Oct 7, 2014, at 8:43 AM, Robert Iakobashvili corobe...@gmail.com wrote:

 On Mon, Sep 22, 2014 at 1:03 PM, Sorvig Morten morten.sor...@digia.com 
 wrote:

 On 19 Sep 2014, at 11:28, Sorvig Morten morten.sor...@digia.com wrote:

 This will indeed receive attention in the coming days. There are already 
 some patches attached to the QTBUGs. I’ll post back here once we have a 
 complete patch set ready. Target branches are Qt 5.3 and Qt 4.8.

 I’m using QTBUG-32896 as a metabug to track the effort.

 Here’s the current patch set (5.3):

 qmake - framework bundle hierarchy (QTBUG-32895): 
 https://codereview.qt-project.org/95454
 qmake - “_debug in CFBundleExecutable  (QTBUG-32894): 
 https://codereview.qt-project.org/95455
 qmake - add CFBundleVersion: https://codereview.qt-project.org/95456
 macdeployqt - “Current” version symlinks: 
 https://codereview.qt-project.org/#/c/95442/

 Are these patches sufficient? If not, what’s missing?

 Morten


 I see that they were integrated to 5.3.
 But when I get the 5.3 branch from git, the last commits seen in log are
 dated August and these patches have been merged on October 1.

 git clone git://gitorious.org/qt/qt5.git qt-5
 cd gt5
 git checkout 5.3

 Shall I take some another branch or switch to something?

 The commits referenced for the submodules in the qt5.git are always a bit 
 behind. To get the absolutely latest commit for a submodule, go into that 
 submodule and checkout the corresponding branch there:

 cd qt5/qtbase
 git checkout 5.3
 git pull


Eike Ziller,
Thank you very much for this tip.
Kind regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt for iOS: Management Retina vs Non-Retina Images

[Robert Iakobashvili]

On Wed, Oct 8, 2014 at 10:03 AM, Ziller Eike
eike.zil...@theqtcompany.com wrote:

 On Oct 6, 2014, at 1:59 PM, Robert Iakobashvili corobe...@gmail.com wrote:

 Gentlemen,
 If images are placed to resource file,
 is there any option for an automatic management
 of using either Retina or non-Retina images
 using Apple's naming convention or the manual
 management is the only option like for Mac OS X?

 Here's an example of what Qt developers
 are doing:
 http://qt-project.org/forums/viewthread/44805/

 Are there any other approaches or
 best practices?


 Just use

 Image {
 source: “foo.png”
 }

 and it will try “f...@2x.png” on 2x screens on OS X and iOS automatically.

 Br, Eike


Thank you for your response.
This is a widget-based application, though.

Kind regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt for iOS: Management Retina vs Non-Retina Images

[Robert Iakobashvili]

On Wed, Oct 8, 2014 at 11:10 AM, Ziller Eike
eike.zil...@theqtcompany.com wrote:

 On Oct 8, 2014, at 9:18 AM, Robert Iakobashvili corobe...@gmail.com wrote:

 On Wed, Oct 8, 2014 at 10:03 AM, Ziller Eike
 eike.zil...@theqtcompany.com wrote:

 On Oct 6, 2014, at 1:59 PM, Robert Iakobashvili corobe...@gmail.com wrote:

 Gentlemen,
 If images are placed to resource file,
 is there any option for an automatic management
 of using either Retina or non-Retina images
 using Apple's naming convention or the manual
 management is the only option like for Mac OS X?

 Here's an example of what Qt developers
 are doing:
 http://qt-project.org/forums/viewthread/44805/

 Are there any other approaches or
 best practices?


 Just use

 Image {
source: “foo.png”
 }

 and it will try “f...@2x.png” on 2x screens on OS X and iOS automatically.

 Br, Eike


 Thank you for your response.
 This is a widget-based application, though.

 QIcon does automatic loading of @2x images afair. QPixmap and QImage only set 
 the devicePixelRatio corresponding to the file name automatically, but you 
 have to define yourself if you want to load a @2x or not.

 Br, Eike

QIcon could be useful. This is helpful.
Thank you.

Kind regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Important OSX 10.9.5 10.10 codesign changes

[Robert Iakobashvili]

On Mon, Sep 22, 2014 at 1:03 PM, Sorvig Morten morten.sor...@digia.com wrote:

 On 19 Sep 2014, at 11:28, Sorvig Morten morten.sor...@digia.com wrote:

 This will indeed receive attention in the coming days. There are already 
 some patches attached to the QTBUGs. I’ll post back here once we have a 
 complete patch set ready. Target branches are Qt 5.3 and Qt 4.8.

 I’m using QTBUG-32896 as a metabug to track the effort.

 Here’s the current patch set (5.3):

 qmake - framework bundle hierarchy (QTBUG-32895): 
 https://codereview.qt-project.org/95454
 qmake - “_debug in CFBundleExecutable  (QTBUG-32894): 
 https://codereview.qt-project.org/95455
 qmake - add CFBundleVersion: https://codereview.qt-project.org/95456
 macdeployqt - “Current” version symlinks: 
 https://codereview.qt-project.org/#/c/95442/

 Are these patches sufficient? If not, what’s missing?

 Morten


I see that they were integrated to 5.3.
But when I get the 5.3 branch from git, the last commits seen in log are
dated August and these patches have been merged on October 1.

git clone git://gitorious.org/qt/qt5.git qt-5
cd gt5
git checkout 5.3

Shall I take some another branch or switch to something?

Thanks,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt for iOS: Management Retina vs Non-Retina Images

[Robert Iakobashvili]

Gentlemen,
If images are placed to resource file,
is there any option for an automatic management
of using either Retina or non-Retina images
using Apple's naming convention or the manual
management is the only option like for Mac OS X?

Here's an example of what Qt developers
are doing:
http://qt-project.org/forums/viewthread/44805/

Are there any other approaches or
best practices?

Thank you.

Kind regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Important OSX 10.9.5 10.10 codesign changes

[Robert Iakobashvili]

On Thu, Sep 18, 2014 at 11:07 PM, Adam Strzelecki o...@java.pl wrote:
 Reported already 24/Jan/14 QTBUG-36429

 FYI more recent and prioritized bug report is QTBUG-38511

 I think it deserves a lot of attention now since 10.9.5 is live.

 --Adam

Agree.

The v2 signatures will be enforced starting from November 1 in the Store,
and with 10.10 Gatekeeper deployment immediately,
so that it looks like not too much time left to make the bundle
structure to comply
with expected by codesign for v2.

I've voted for all the bugs above; could the priority of the issues to
be increased?
Thank you.
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt-5.3 Broken Deployment to Mac OS 10.6, Snow Leopard

[Robert Iakobashvili]

Gentlemen,

Are there other people on the list who encountered by using either
custom or pre-built 5.3.0?

https://bugreports.qt-project.org/browse/QTBUG-39282

If yes, does somebody has patches to overcome it?
Thank you in advance.

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] No SSL on iOS ?

[Robert Iakobashvili]

On Fri, May 2, 2014 at 11:31 AM, Kurt Pattyn pattyn.k...@gmail.com wrote:
 Could this be a solution: https://github.com/x2on/OpenSSL-for-iPhone ?
 This project provides a script to make a static build of OpenSSL to be used 
 on iOS 4.3 - iOS 7.1.

 Cheers,

 Kurt

It works properly when Qt built as described here:

https://bugreports.qt-project.org/browse/QTBUG-36891

-- 
Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Question about Qt's future

[Robert Iakobashvili]

On Mon, Apr 28, 2014 at 6:53 AM, Thiago Macieira
thiago.macie...@intel.comwrote:

 Em dom 27 abr 2014 15:01:10 você escreveu:
   It's not the only available choice. Widgets are available. They just
 look
   horrible because no one has done any work to make them look native.
 
  Is my understating correct that:
 
  1. at least QML apps in iOS already have a native look?
  Any examples beyond the most basic?

 The point I was trying to make is that they will have a native look, if
 they
 don't already. I don't know if they do. I don't do iOS development and
 don't
 care to follow the development there.

 However, QtWidgets will never have native look on iOS.

  2. there are any Qt-related benchmarks demonstrating
  opengl versus i.e. raster performance advantages for iOS and Android?
  Any links?

 That's pretty basic information. OpenGL always beats, hands down. Try to do
 nice effects in raster and you'll see a huge CPU spike, eating battery, or
 not
 able to finish at all.

 I don't have links for this. it should be easy to find on Google.

  3. opengl issues on Android have been addressed and it is stable?

 I'm not aware of any issues. But I don't follow Android development closely
 either.

  4. memory footprint, particularly on iOS devices with
  1GB of RAM, best case, for QML is reasonable and does
   not cost a foot and leg?
   Any data?

 I don't know either. Like I said, I don't follow iOS development. I don't
 have
 an SDK for it installed and don't care to try it.

 If you had asked for 256 MB, I'd be worried. For 1 GB, it shouldn't be a
 problem, but I can't give you data.

 --
 Thiago Macieira - thiago.macieira (AT) intel.com
   Software Architect - Intel Open Source Technology Center


Sorry, but the above is not helpful.

I'd never jump to conclusions and statements without
in-hands knowledge of the subject to talk about.

Thank you.

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt-iOS: Popover-Like Styled Frames

[Robert Iakobashvili]

Dear Richard,
Thank you very much for the direction of using
nativeResourceForWindow that looks promising.

Nativity issue seems be even more sensitive for iOS  than for Android;
it could actually be a ground for not accepting apps to the only store.

Is there any place to vote for these iOS-natives?

Thank you once more.

Kind regards,
Robert

On Tue, Apr 8, 2014 at 11:41 AM, Gustavsen Richard
richard.gustav...@digia.com wrote:
 Hi!
 Native menus are on the todo list, but currently not implemented on iOS. You 
 can take a look at this example (https://github.com/richardmg/qtdd13_qmlapp) 
 to get an idea on how you can make use of native view controllers (like a 
 UIPopoverController ) in your app.

 -Richard
 
 Fra: development-bounces+richard.gustavsen=digia@qt-project.org 
 [development-bounces+richard.gustavsen=digia@qt-project.org] p#229; 
 vegne av Robert Iakobashvili [corobe...@gmail.com]
 Sendt: 7. april 2014 18:07
 To: development@qt-project.org
 Emne: [Development] Qt-iOS: Popover-Like Styled Frames

 Hi,
 There are some icons on the top toolbar of my Qt-application.

 I'd like to have dropdown popover-like frames i.e. for fast selection
 of some settings or selection of applications to share with, etc
 with maximum nativity like have most iPad applications.

 Is there any way to code it with Qt?

 If not, are there any ideas how to make the integration between
 QMenu action menu over QMainWindow with Objective-C written Controllers.

 Your directions would be very much appreciated.
 Thank you in advance!

 Regards,
 Robert
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt-iOS: Popover-Like Styled Frames

[Robert Iakobashvili]

Hi,
There are some icons on the top toolbar of my Qt-application.

I'd like to have dropdown popover-like frames i.e. for fast selection
of some settings or selection of applications to share with, etc
with maximum nativity like have most iPad applications.

Is there any way to code it with Qt?

If not, are there any ideas how to make the integration between
QMenu action menu over QMainWindow with Objective-C written Controllers.

Your directions would be very much appreciated.
Thank you in advance!

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development