On sexta-feira, 1 de março de 2013 11.38.54, Иван Комиссаров wrote:
Hello, i would like to request a repository in a playground for my
QDriveInfo module.
This class allows to retrieve information about a system volumes - like
available size, filesystem, filesystem flags and so on.
Right
On Fri, Mar 1, 2013 at 8:12 AM, Thiago Macieira
thiago.macie...@intel.comwrote:
On sexta-feira, 1 de março de 2013 11.38.54, Иван Комиссаров wrote:
Hello, i would like to request a repository in a playground for my
QDriveInfo module.
This class allows to retrieve information about a
On 2013-3-1, at 上午9:12, Thiago Macieira wrote:
On sexta-feira, 1 de março de 2013 11.38.54, Иван Комиссаров wrote:
Hello, i would like to request a repository in a playground for my
QDriveInfo module.
This class allows to retrieve information about a system volumes - like
available size,
Op 1-3-2013 8:38, Иван Комиссаров schreef:
Hello, i would like to request a repository in a playground for my QDriveInfo
module.
This class allows to retrieve information about a system volumes - like
available size, filesystem, filesystem flags and so on.
Right now, repo is located here
Yes, it still exists somewhere in Qt5 code, but it's not maintained and
provides much less functionality compared to QtDriveInfo.
Also, it has flawed API, in my opinion:)
For example, it's hard to implement drive comparison (i.e. if 2 files are on
the same drive or not) using current
On Fri, Mar 1, 2013 at 8:42 AM, André Somers an...@familiesomers.nl wrote:
Wasn't there already similar functionality in QtMobility?
QSystemStorageInfo seems to provide similar functionality? Or did all
that get scrapped in Qt 5?
Ah, you are both right:
I don't think it's a good idea to try to fix QStorageInfo.
The main argument is that QStorageInfo is a monitor+info provider, but monitor
should depend on a DBus in Linux; however info provider doesn't require that.
Also, monitor requires internal thread on Mac. My point is that in many cases,
On Mar 1, 2013, at 8:27 AM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
Why are we discussing adding conversion operators from/to native objects in
QtCore/QtGui? The methods that did so were removed in Qt 5 in order to
increase modularity, why would we go the opposite
Hi all,
We would appreciate Your help in one quite trivial task. With a joint effort
together it also should be reasonable small task for individual developer.
Digia acquired all Nokia's Qt copyrights last year. We have already changed the
copyrights in main branches. All non-Nokia
On Friday 01 March 2013 18:57:47 Majid Khan wrote:
I have recently updated my local repo for Qt Creator and its failing now,
:-1: error: No rule to make target
`../../../qt-creator/share/qtcreator/templates/wizards/bb-qt5-quick2app/bar-
descriptor.xml', needed by
I suppose it would not be a detriment. Where do you draw the line? Which
platforms, what functions and types?
Here are some candidate types for constructors and conversion operators on
their corresponding Qt types, which I can think of off the top of my head:
Windows:
POINT
RECT
HICON
HBITMAP
Great! Thanks :)
On Fri, Mar 1, 2013 at 8:33 PM, Tobias Nätterlund
tobias.naetterl...@kdab.com wrote:
On Friday 01 March 2013 18:57:47 Majid Khan wrote:
I have recently updated my local repo for Qt Creator and its failing now,
:-1: error: No rule to make target
On Friday 01 March 2013 08:51:16 Laszlo Papp wrote:
qdisplayinfo_linux.cpp: In function
'{anonymous}::Q_QGS_BACKLIGHT_SYSFS_PATH::Type*
{anonymous}::Q_QGS_BACKLIGHT_SYSFS_PATH::innerFunction()':
qdisplayinfo_linux.cpp:50:1: error: lambda-expression in unevaluated context
Op 1-3-2013 10:22, ?? schreef:
I don't think it's a good idea to try to fix QStorageInfo.
The main argument is that QStorageInfo is a monitor+info provider, but
monitor should depend on a DBus in Linux; however info provider
doesn't require that. Also, monitor requires internal
On Fri, Mar 01, 2013 at 09:28:13AM +, Hirvonen Olli wrote:
1. Copyright (C) 2012 Nokia Corporation and/or its subsidiary(-ies) or
something similar with different year. For example in:
several of these repositories are just dead (and will soon be moved and
marked as such once we
On Mar 1, 2013, at 10:37 AM, Jake Thomas Petroules
jake.petrou...@petroules.com
wrote:
I suppose it would not be a detriment. Where do you draw the line? Which
platforms, what functions and types?
I would leave that decision to the platform maintainers. An initial minimal set
would be
Hi,
I suppose it would not be a detriment. Where do you draw the line?
Which platforms, what functions and types? Here are some candidate types
for constructors and conversion operators...
The thing to keep in mind is basically that the decision to remove the
pixmap conversion functions was
On Fri, Mar 1, 2013 at 9:28 AM, Hirvonen Olli olli.hirvo...@digia.comwrote:
**2. **In some repositories company copyright is missing and
there is only original author copyright. Example:
** Copyright (C) 2012 Firstname Surname em...@xyz.org
** Contact:
2013/3/1 André Somers an...@familiesomers.nl:
Op 1-3-2013 10:22, Иван Комиссаров schreef:
I don't think it's a good idea to try to fix QStorageInfo.
The main argument is that QStorageInfo is a monitor+info provider, but
monitor should depend on a DBus in Linux; however info provider doesn't
Op 1-3-2013 11:52, Konstantin Ritt schreef:
2013/3/1 André Somers an...@familiesomers.nl:
Op 1-3-2013 10:22, Иван Комиссаров schreef:
I don't think it's a good idea to try to fix QStorageInfo.
The main argument is that QStorageInfo is a monitor+info provider, but
monitor should depend on a
2013/3/1 Иван Комиссаров abba...@gmail.com:
01.03.2013, в 13:54, André Somers an...@familiesomers.nl написал(а):
Op 1-3-2013 10:22, Иван Комиссаров schreef:
I don't think it's a good idea to try to fix QStorageInfo.
The main argument is that QStorageInfo is a monitor+info provider, but
I discussed with Tuukka Turunen and his opinion was that even something is not
developed further, but it is available, copyrights should be the correct ones.
But as said this is not the most urgent issue and priority is low.
And sorry if the examples I used were fixed already. I got those
tests/prebuild/license in qtqa repo is just for that purpose though I am not
sure how it got run on every qt5 module repo.
http://qt.gitorious.org/qt/qtqa/trees/master/tests/prebuild/license
Regards,
Liang
On 2013-3-1, at 下午12:24, Hirvonen Olli wrote:
I discussed with Tuukka Turunen and his
I am trying to debug Qt Creator (working on #7044) but when I debug (its
new linux mint 14 Nadia Cinammon) my gdb gives error
Starting executable failed:
/home/majid/projects/qtcreator-build/bin/qtcreator.sh: not in executable
format: File format not recognised
but all other pet projects build
Thanks,
ptrace: Operation not permitted.
Could not attach to the process. Make sure no other debugger traces this
process.
Check the settings of
/proc/sys/kernel/yama/ptrace_scope
For more details, see /etc/sysctl.d/10-ptrace.conf
and contents of file:
kernel.yama.ptrace_scope = 1
On
Great! Thanks :)
On Sat, Mar 2, 2013 at 1:34 AM, Mitch Curtis mitch.cur...@digia.com wrote:
On 03/01/2013 03:20 PM, Majid Khan wrote:
Thanks,
ptrace: Operation not permitted.
Could not attach to the process. Make sure no other debugger traces this
process.
Check the settings
On sexta-feira, 1 de março de 2013 10.52.41, Olivier Goffart wrote:
qdisplayinfo_linux.cpp:50 is:
Q_GLOBAL_STATIC_WITH_ARGS(const QString, BACKLIGHT_SYSFS_PATH,
(QStringLiteral(/sys/class/backlight/)))
Is that something we should fix in
On sexta-feira, 1 de março de 2013 16.43.35, Joerg Bornemann wrote:
In qprocess_win.cpp there's this code for determining if the child
process crashed or not.
//### for now we assume a crash if exit code is less than -1 or the
magic number
crashed = (exitCode == 0xf291 || (int)exitCode 0);
On 01/03/2013 16:47, Pau Garcia i Quiles wrote:
http://stackoverflow.com/questions/9187021/c-application-exit-error-code-62097-what-does-that-mean
It means memory allocation failed.
Yeah I also found this comment but I cannot make my memory allocator
fail in a way that I get this exit code.
On 01/03/2013 16:53, Thiago Macieira wrote:
The value reappears:
void QProcessPrivate::killProcess()
{
if (pid)
TerminateProcess(pid-hProcess, 0xf291);
}
Oh it's Qt's magic number, no Windows sorcery. That explains it.
Thanks,
Joerg
On Fri, Mar 1, 2013 at 4:59 PM, Joerg Bornemann
joerg.bornem...@digia.comwrote:
On 01/03/2013 16:47, Pau Garcia i Quiles wrote:
http://stackoverflow.com/**questions/9187021/c-**
On 01/03/13 18:42, André Somers wrote:
Op 1-3-2013 8:38, Иван Комиссаров schreef:
Hello, i would like to request a repository in a playground for my
QDriveInfo module.
This class allows to retrieve information about a system volumes - like
available size, filesystem, filesystem flags and
On 01/03/13 18:50, Иван Комиссаров wrote:
Yes, it still exists somewhere in Qt5 code, but it's not maintained and
provides much less functionality compared to QtDriveInfo.
wrong. it is maintained. by me. or rather, has a maintainer. I haven't
seen any bug reports or code reviews for it.
On sábado, 2 de março de 2013 07.51.04, Lorn Potter wrote:
Wasn't there already similar functionality in QtMobility?
QSystemStorageInfo seems to provide similar functionality?
Yes it does.
Or did all
that get scrapped in Qt 5?
It's there in qtsystems, which is a hidden module.
As I
On 01/03/13 19:54, André Somers wrote:
Op 1-3-2013 10:22, Иван Комиссаров schreef:
I don't think it's a good idea to try to fix QStorageInfo.
The main argument is that QStorageInfo is a monitor+info provider, but
monitor should depend on a DBus in Linux; however info provider
doesn't require
On 01/03/13 20:50, Иван Комиссаров wrote:
01.03.2013, в 13:54, André Somers an...@familiesomers.nl написал(а):
Op 1-3-2013 10:22, Иван Комиссаров schreef:
I don't think it's a good idea to try to fix QStorageInfo.
The main argument is that QStorageInfo is a monitor+info provider, but
On 02/03/13 07:59, Thiago Macieira wrote:
On sábado, 2 de março de 2013 07.51.04, Lorn Potter wrote:
Wasn't there already similar functionality in QtMobility?
QSystemStorageInfo seems to provide similar functionality?
Yes it does.
Or did all
that get scrapped in Qt 5?
It's there in
On sábado, 2 de março de 2013 08.20.35, Lorn Potter wrote:
systeminfo works on all platforms, mobile or not.
I want the QtCore solution to work on all platforms too. I just want less
emphasis on mobile (and especially Symbian-inspired) features and more focus
on general use-cases.
The udisks
Hello,
On Wednesday 9 January 2013 Thiago Macieira wrote:
I'm not sure it's out of scope for Qt. In fact, I don't know yet whether it
should be part of Qt Core or not. I guess I am the person to make that
particular call.
So what I need from Glen is, at least, the proposed API docs with
On Fri, Mar 1, 2013 at 9:29 PM, Qi Liang liang...@digia.com wrote:
tests/prebuild/license in qtqa repo is just for that purpose though I am not
sure how it got run on every qt5 module repo.
http://qt.gitorious.org/qt/qtqa/trees/master/tests/prebuild/license
The license header checker autotest
On sábado, 2 de março de 2013 10.27.24, Jason McDonald wrote:
* For each file checked, the script will print a line beginning with
ok or not ok depending on the result. When not ok, it will also
print some detail about why it failed.
If you don't want to see the ok / not ok lines, simply
On Sat, Mar 2, 2013 at 12:27 AM, Jason McDonald macadd...@gmail.com wrote:
cd ~/dev/qt5
QT_MODULE_TO_TEST=qtdeclarative qtqa/tests/prebuild/tst_licenses.pl
bash: qtqa/tests/prebuild/tst_licenses.pl: No such file or directory
I will take you meant QT_MODULE_TO_TEST=qtdeclarative
Hi all!
The CI bot reported a failure in tst_qwidget when merging
https://codereview.qt-project.org/#change,42990,patchset=8
(see the last comment from Qt Continuous Integration System).
I can reproduce the same failure under ubuntu 13.04 running XFCE.
Then I removed my patch (by checking out
43 matches
Mail list logo
