On Jan 10, 2014, at 6:07 AM, Ziller Eike wrote:
> On Jan 9, 2014, at 6:05 PM, Kuba Ober wrote:
>
>> I’m trying to figure out the most constructive way of ensuring that an OS X
>> build of Qt, installed with the source code, can be actually debugged by
>> stepping into the C++ source code in t
Yes, I was about to write a mail about it. We don't currently officially
have maintainers for platforms, but they exist in reality, and I'd like to
make them explicit.
So if nobody disagrees, I'll add them to the list next week.
Cheers,
Lars
On 10/01/14 18:22, "David Faure" wrote:
>Could we a
On Wed, Jan 8, 2014 at 5:31 AM, Sebastian Lehmann wrote:
> Hi,
>
> I'd find it "natural" if there was something like a QtCore plugin.
> Then, QtQuick and Qt3D (and other stuff) could depend on it; i.e.
> something analogous to the existing Qt modules dependency, but in the
> QML world.
>
> I alrea
I also had a drive monitor class
https://gitorious.org/qdrive/qdrive/source/bf9f993ec64781534169a7ac630632805ef34374:src/driveinfo/qdrivecontroller.h
but it needs a bit polishing
Иван Комиссаров
11 янв. 2014 г., в 0:28, Tony Van Eerd написал(а):
> We will put up our stuff into a review next w
We will put up our stuff into a review next week. Currently it is mostly
header/API only, no implementation files. We are just trying to get the API
designed.
We looked at QDriveInfo (either that one or similar one of the same name) and,
basically, "stole" many ideas from it. Ours was also c
> -Original Message-
> From: development-bounces+alexander.blasche=digia@qt-project.org
> To: development@qt-project.org
> Subject: Re: [Development] new Jira Network assignees
>
> On sexta-feira, 10 de janeiro de 2014 11:31:47, Peter Hartmann wrote:
> > * Thiago is the default assigne
2014/1/10 Matt Broadstone
> On Fri, Jan 10, 2014 at 1:31 PM, Konstantin Ritt wrote:
>
>> https://codereview.qt-project.org/73945
>>
>>
> I looked at this, but it lacks the extra functionality that Tony indicates
> is in their classes. Specifically, not just info about the drive/device,
> but the
On Fri, Jan 10, 2014 at 1:31 PM, Konstantin Ritt wrote:
> https://codereview.qt-project.org/73945
>
>
I looked at this, but it lacks the extra functionality that Tony indicates
is in their classes. Specifically, not just info about the drive/device,
but the ability to mount/unmount the devices as
https://codereview.qt-project.org/73945
Regards,
Konstantin
2014/1/10 Matt Broadstone
>
>
> On Friday, January 10, 2014, Tony Van Eerd wrote:
>
>> There was some work going on inside BlackBerry to revamp
>> QSystemStorageInfo. Last version I saw had:
>>
>> QDrive:
>> - similar to QDir (not a
On Friday, January 10, 2014, Tony Van Eerd wrote:
> There was some work going on inside BlackBerry to revamp
> QSystemStorageInfo. Last version I saw had:
>
> QDrive:
> - similar to QDir (not a QObject!).
> - construct from URI/path (ie "dev/sda1" or "D:\")
> - mount/unmount/is-it-mounted/list-of
Could we add a table at the bottom of http://qt-project.org/wiki/Maintainers
with the platform maintainers, for each platform?
... unless I'm wrong and the concept doesn't exist within the Qt community,
but AFAIK it does?
I can't find who's the official maintainer for each platform.
--
David Fau
There was some work going on inside BlackBerry to revamp QSystemStorageInfo.
Last version I saw had:
QDrive:
- similar to QDir (not a QObject!).
- construct from URI/path (ie "dev/sda1" or "D:\")
- mount/unmount/is-it-mounted/list-of-mount-points/etc
- total/available space
QDriveWatcher:
- QOb
On sexta-feira, 10 de janeiro de 2014 13:47:34, Koehne Kai wrote:
> So, I'm wondering, can anybody check for the Intel compiler whether it cares
> about the C++ standard when it comes to variadic macros? If not, do we
> still support toolchains that do not handle variadic macros?
It's supported in
On sexta-feira, 10 de janeiro de 2014 11:31:47, Peter Hartmann wrote:
> * Thiago is the default assignee for URL bugs, as QUrl is part of QtCore
> (I guess it was like this already)
Either this should be renamed to Core: URL handling or to Network: Access
Manager.
--
Thiago Macieira - thiago.ma
On sexta-feira, 10 de janeiro de 2014 12:04:23, Koehne Kai wrote:
> And here are the results:
>
> PASS : CatLogBench::qWarningPrintf1()
> RESULT : CatLogBench::qWarningPrintf1():
> 0.0010 msecs per iteration (total: 67, iterations: 65536)
> PASS : CatLogBench::qWarningPrintf2()
>
On 1 Mar 2013, at 11:20 PM, Lorn Potter wrote:
> 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 d
Oh, yes you are totally right. Sorry for the noise.
Marius
On 1/10/2014 4:06 PM, Tor Arne Vestbø wrote:
> On 1/8/14 20:35 , cincirin wrote:
>> Hi,
>>
>> The Qt documentation [1] point us that iOS minimum deployment target is
>> iOS 5.0
>
> The issue here is that you're building against the iOS 5
On 1/8/14 20:35 , cincirin wrote:
> Hi,
>
> The Qt documentation [1] point us that iOS minimum deployment target is
> iOS 5.0
The issue here is that you're building against the iOS 5.0 SDK. The
deployment target can still be iOS 5.0 even if you build against the
latest SDK (which you should).
N
Hi,
We've code in qcompilerdetection.h that tries determine whether the
compiler/preprocessor supports variadic arguments, or not.
Specifically, Q_COMPILER_VARADIC_MACROS are right now defined for
Intel if compiled with C++11 support (__cplusplus >= 201103L)
Clang >=2.9 if compiled with C++11 s
Grr... OWA.
> And here are the results:
>
> PASS : CatLogBench::qWarningPrintf1()
> RESULT : CatLogBench::qWarningPrintf1():
> 0.0010 msecs per iteration (total: 67, iterations: 65536)
> PASS : CatLogBench::qWarningPrintf2()
> RESULT : CatLogBench::qWarningPrintf2():
> 0.0013 msecs p
Koehne Kai wrote:
> > -Original Message-
> > From: development-bounces+kai.koehne=digia@qt-project.org
> > [...]
> > As a blueprint I've started a patch for a 'qt.core.io' category:
> >
> > https://codereview.qt-project.org/#change,74862,patchset=1
>
> Andre raised concerns about the
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [...]
> As a blueprint I've started a patch for a 'qt.core.io' category:
>
> https://codereview.qt-project.org/#change,74862,patchset=1
Andre raised concerns about the (runtime/space) overhead of the Q
+1
On Thu, Jan 09, 2014 at 08:24:47PM +, Knoll Lars wrote:
> Hi,
>
> I'd like to continue on filling gaps in our maintainer list and thus want
> to propose Simon Hausmann as the new maintainer for QtQml. Guess I don't
> need to say a whole lot more about the nomination... ;-)
>
> Cheers,
> L
On Jan 9, 2014, at 6:05 PM, Kuba Ober wrote:
> I’m trying to figure out the most constructive way of ensuring that an OS X
> build of Qt, installed with the source code, can be actually debugged by
> stepping into the C++ source code in the Qt library. So far I can only step
> into disassembl
On 08 Jan 2014, at 10:12, Koehne Kai wrote:
>
> You can then use it like that:
>
> If (qtCoreIo().isDebugEnabled()) {
>QString x = expensive();
>qCDebug(qtCoreIo) << "Expensive: " << x;
> }
>
> Anyhow, note that qCDebug(qtCoreIo) expands to
>
> for (bool enabled = qtCoreIo().isDeb
Hi,
Registration is now open for the eighth annual C++Now conference
(formerly BoostCon) which will be held in Aspen, Colorado, USA, May
12th to 17th, 2014.
C++Now is a general C++ conference for C++ experts and enthusiasts.
It is not specific to any library/framework or compiler vendor and
has t
On Tue, Jan 7, 2014 at 1:43 PM, Mark Gaiser wrote:
>
> Feedback.. Anyone?
>
> If there is no feedback this week then i'm going to assume that my
> proposal is probably the best way to go and start implementing it.
> It's actually kinda demotivating since i would expect the plasma folks
> to care,
On Fri, Dec 6, 2013 at 3:08 PM, Mark Gaiser wrote:
>
> Below is my "feature" list that i'd like to have in that calendar.
> Since i have some experience in that area i will try to help out as
> much as i can.
>
> -- QML part --
> * Controls for the calendar grid
> * Controls for next/forward or j
On Tue, Jan 7, 2014 at 4:36 PM, Mark Gaiser wrote:
>
> >> * Controls for the day names (mon, tue, wed, thu, fri, sat, sun). And
> >> the ability to change the name to shorter/longer variants.
> >
> >
> > What would be the usecase for longer variants? Full screen/huuge
> calendars I
> > assume? He
Why keep the breakage though. This fix would still require a note in
porting docs and changes to code. Why fix what was never broken - just
go back to Qt 4 behavior..
Sorry for the post format, crap mail client issue...
___
Development mailing list
Devel
On 19 Dec 2013, at 02:31, Thiago Macieira wrote:
>
> I especially like memcpy_s, which takes an extra argument which is most often
> the exact same value you were already passing anyway[1]. Too bad they didn't
> make memcmp_s, that would have been funny, returning EDOOFUS if you passed
> the
On Saturday, December 21, 2013 19:50:30 Mark Gaiser wrote:
> I hope some of the plasma folks can provide some feedback on the ideas
> proposed in this thread.
Which ideas exactly? The thread is quite convoluted, and it's hard to make
sense of it to me. I also might be missing an email or two.
If
Hello,
in case somebody is interested: Rich and me just agreed on distributing
the default assignees for the Jira Network components:
Rich Network
Rich Network: Authentication
PeterNetwork: BearerManagement
PeterNetwork: Cache
Rich Network: Cookies
Rich
On Jan 6, 2014, at 11:38 AM, Marc Mutz wrote:
> On Thursday 02 January 2014 21:04:27 Jiergir Ogoerg wrote:
>> buffer() // getter
>> buffer_set(..) // setter
>> BufferSupportsFind() // bool
>>
>> selection() // getter
>> SelectionMove(..) // move selection
>> selection_set(..) // setter
>> Selec
On Thursday 9. January 2014 12.58.57 Thiago Macieira wrote:
> On quinta-feira, 9 de janeiro de 2014 20:24:47, Knoll Lars wrote:
> > Hi,
> >
> > I'd like to continue on filling gaps in our maintainer list and thus want
> > to propose Simon Hausmann as the new maintainer for QtQml. Guess I don't
> >
35 matches
Mail list logo
