QCamera being buggy on Android is one of the reasons why we wrote
qml-cvcamera. The other is support for various devices, such as Kinect
and PointGrey cameras.
On 23. 10. 14 08:19, Kojo Tero wrote:
Hello,
Please take a look at the Qt bugreports.
For example this: https://bugreports.qt-proje
Hello,
Please take a look at the Qt bugreports.
For example this: https://bugreports.qt-project.org/browse/QTBUG-37525
Or maybe this: https://bugreports.qt-project.org/browse/QTBUG-41273
It seems that video recording on Android depends on the device manufacturer.
I suggest trying to get a log ou
Hello developers of Qt Installer Framework!
How can I get the version of the framework?
I know that the program "installerbase" returns a long string that contains the
version and it was good.
But:
- The format of this string is nowhere documented (or I just have not found it);
- The applicat
Thank you. your samples is run.
But Iwant to useqcamera to capture video.
At 2014-10-22 21:04:46, "Ayberk Özgür" wrote:
I'd recommend using the QML wrapper for the OpenCV camera that we wrote
externally: https://github.com/chili-epfl/qml-cvcamera, it works on Android.
On 22. 10. 14 14:53
Originally, I have proposed that patch in response to a question on
StackOverflow on non-intuitive Dialog behaviour. I thought it was just a
bug fix, and didn't check if QtWidgets behave differently.
If such change is not suitable for Qt 5.x, then, I'd like to suggest a
property that disables auto
> On 20 Oct 2014, at 21:06, Morten Johan Sørvig wrote:
>
>
>> On 20 Oct 2014, at 15:04, Saether Jan-Arve
>> wrote:
>>
>> Change: https://codereview.qt-project.org/97600
>>
> (comment from 97600)
> // On OS X the windows might get positioned exactly on top of each other
> // that means no re
> On 22 Oct 2014, at 15:13, Oswald Buddenhagen
> wrote:
>
> On Wed, Oct 22, 2014 at 02:53:42PM +0200, Adam Strzelecki wrote:
>>> It looks like we have to leave this to to the deployment solution
>>> (macdeployqt does not deploy the file).
>>
>> I understand, however then we get frameworks tha
On Wed, Oct 22, 2014 at 01:28:38PM +, Rutledge Shawn wrote:
> It has been proposed that in QtQuick.Dialogs, the Help, Apply and Reset
> buttons should not dismiss any dialog automatically. I agree
> conceptually, but the issue is that to be completely consistent, we need
> to change the behavi
On Wednesday 22 October 2014 14:30:54 Oswald Buddenhagen wrote:
> On Wed, Oct 22, 2014 at 12:57:49PM +0300, Orgad Shaneh wrote:
> > An alternative to constant rebasing of the current branch is using *a
> > separate clone* for pushing. This clone can share objects with the real
> > working clone (vi
Am 22.10.2014 um 15:28 schrieb Rutledge Shawn:
> It has been proposed that in QtQuick.Dialogs, the Help, Apply and Reset
> buttons should not dismiss any dialog automatically. I agree conceptually,
> but the issue is that to be completely consistent, we need to change the
> behavior of QMessage
It has been proposed that in QtQuick.Dialogs, the Help, Apply and Reset buttons
should not dismiss any dialog automatically. I agree conceptually, but the
issue is that to be completely consistent, we need to change the behavior of
QMessageBox (and various native dialog implementations) to matc
On Wed, Oct 22, 2014 at 02:53:42PM +0200, Adam Strzelecki wrote:
> > It looks like we have to leave this to to the deployment solution
> > (macdeployqt does not deploy the file).
>
> I understand, however then we get frameworks that cannot be code-signed if
> copied just straight from the folder
I'd recommend using the QML wrapper for the OpenCV camera that we wrote
externally: https://github.com/chili-epfl/qml-cvcamera, it works on
Android.
On 22. 10. 14 14:53, kl222 wrote:
*Description*
QCamera don't capture video in android. Run the attached example.
But it can work in windows a
Description
QCamera don't capture video in android. Run the attached example.
But it can work in windows and linux.
Is it bug or code is wrong? If code is wrong, tall me how to write.
* Environment:
operating system:android
qt version:
qt 5.3.1
qt 5.3.2
qt 5.4.0-beta1
custo
> It looks like we have to leave this to to the deployment solution
> (macdeployqt does not deploy the file).
I understand, however then we get frameworks that cannot be code-signed if
copied just straight from the folder just because this single .prl file.
Can you please share some details why
On Wed, Oct 22, 2014 at 12:57:49PM +0300, Orgad Shaneh wrote:
> An alternative to constant rebasing of the current branch is using *a
> separate clone* for pushing. This clone can share objects with the real
> working clone (via .git/objects/info/alternates), then you can easily git
> checkout and
> On 21 Oct 2014, at 21:09, Adam Strzelecki wrote:
>
> Just want to humbly remind that we still need to get rid of .prl files from
> Qt module frameworks roots. Either move the one level up or into Resources/
It looks like we have to leave this to to the deployment solution (macdeployqt
does n
On Tuesday 21. October 2014 12.56.41 Stottlemyer, Brett wrote:
> On Tuesday, October 21, 2014 8:19 AM Simon Hausmann wrote:
> > The QTime is literally the result of string copy&paste from the token in
> > the header file into the moc generated C++ code. There's no type lookup,
> > resolution or ana
PI documentation).
>>
>> You have to explicitly set it up for that though.
>>
>>Kevin Kofler
>
> --
> With best regards,
> Oleksii Serdiuk
>
> -- next part --
> A non-text attachment was scrubbed...
> Name: smime.p7s
gt;>
>>Kevin Kofler
>
> --
> With best regards,
> Oleksii Serdiuk
>
> -- next part --
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 4813 bytes
> Desc: S/MIME Cryptographic Signature
> Url :
> http://lists.qt-project.org/pipermail/development/attachments/20141022/d0709696/attachment-0001.bin
>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
we are in the middle of the bugfixing week, so everyone is wrangling
half a dozen mostly unrelated changes at the same time. the perfect
time to plug the awesomely improved gpush!
from the manual:
Prior to actually pushing any commits, gpush will temporarily rebase
them onto a new base. T
Hello Martin,
Yes, it uses index files. In Qt 4 times it was one file (qt-4.8.tags),
but now they're split per-module (qtcore.tags, qtgui.tags, ...).
In Doxyfile you have to set TAGFILES to path to .tags file and URL to Qt
documentation. If you need an example, you can take a look at
https://gith
22 matches
Mail list logo
