Re: [Development] Problem comiling with option -qtnamespace and -qtlibinfix in Mac OS X 10.9.4

Hi Oswald thank you for the response. You were right: It seems that the known bug for the -qtlibinfix option has corrupted my directory when trying it for the first time. Running ./configure -qtamespace for a second time combined with a make clean is not sufficient to repair it. Building from

[Development] QSharedMemory POSIX implementation

Hi all, I find QSharedMemory very useful, and I'm extensively using it for cross platform IPC. I noticed in the code (qsharedmemory_unix.cpp) there are two implementations for that class, one using System V IPC and the other using POSIX IPC (mmap). On both Linux and Mac versions of Qt, the

Re: [Development] How to have equivalent of functions over-riding in Qml

Hi, the problem is that your Derived.qml isn't actually derived from Base.qml, since you're using 'Item'instead of 'Base' as a root item. This will work: Base.qmlItem {function method1() {}} Derived.qmlBase {   id: base} SomeOtherQml.qml...Derived {   id: derived1}...Calling

Re: [Development] QSharedMemory POSIX implementation

On Wednesday 09 July 2014 16:17:38 Calogero Mauceri wrote: Hi all, I find QSharedMemory very useful, and I'm extensively using it for cross platform IPC. I noticed in the code (qsharedmemory_unix.cpp) there are two implementations for that class, one using System V IPC and the other

Re: [Development] QSharedMemory POSIX implementation

On 7/9/2014 5:22 PM, Thiago Macieira wrote: On Wednesday 09 July 2014 16:17:38 Calogero Mauceri wrote: Hi all, I find QSharedMemory very useful, and I'm extensively using it for cross platform IPC. I noticed in the code (qsharedmemory_unix.cpp) there are two implementations for that

Re: [Development] How to have equivalent of functions over-riding in Qml

Thanks for the very quick reply. Thank you for clarifying my understanding of correct derivation in Qml Regards, R.kiran ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Guidelines for reporting bugs in Qt

Am 03.07.2014 16:31, schrieb Friedemann Kleint: Hi, as a result of internal discussions at Digia, I have updated http://qt-project.org/wiki/ReportingBugsInQt a bit. The motivation behind this is that we want the bug reports as good as possible since many roles in the Qt project deal with

[Development] Compiling qtmultimedia on OS X

Can anyone help me with compiling the qtmultimedia plugin on OS X? I’m getting objective-c related errors and I’m stumped. I posted details on the forum: (http://qt-project.org/forums/viewthread/44802/) Warm regards, Mike ___ Development mailing list

Re: [Development] QSharedMemory POSIX implementation

On Wednesday 09 July 2014 17:32:29 Calogero Mauceri wrote: I did not know the POSIX implementation was not supported. I think it should be supported and you should be able to choose which implementation you want at runtime. Room for contribution :-) -- Thiago Macieira - thiago.macieira (AT)

[Development] Cake and eating it too for qDebug printing to system log - https://codereview.qt-project.org/89357

== Problematic == Qt 5.3 and dev are currently able to send the output of qDebug, qWarning and the rest of the logging framework to somewhere other than stderr. That's done on Windows, BlackBerry, Android, and on Linux systems with journald. Additionally, there's a pending patch for OS X to use

Re: [Development] Cake and eating it too for qDebug printing to system log - https://codereview.qt-project.org/89357

On Wednesday 09 July 2014 14:43:36 Thiago Macieira wrote: === Log to system logs only === This causes reports like [4]. But note that the bug is actually in Creator, for failing to read the log store and display the data, like it does on Windows with the debug output. This is an option.

Re: [Development] Cake and eating it too for qDebug printing to system log - https://codereview.qt-project.org/89357

On Wednesday 09 July 2014 14:43:36 Thiago Macieira wrote: Current Linux desktops with journald: - default stderr: captured into ~/.xsession-errors - system logging available: available - is stderr useful: yes, for launching from terminal [when Linux desktops start using user-mode systemd,

Re: [Development] Cake and eating it too for qDebug printing to system log - https://codereview.qt-project.org/89357

I feel the urge to give my two cents on that. At least on unix desktop platforms, I expect to get stderr output on the console. So, detecting its presence is certainly a good approach. When there is no console, I probably don't care about the logs at all. I *may* care about error/warning

Re: [Development] Cake and eating it too for qDebug printing to system log - https://codereview.qt-project.org/89357

On Thursday 10 July 2014 02:54:12 Corentin Jabot wrote: At least on unix desktop platforms, I expect to get stderr output on the console. So, detecting its presence is certainly a good approach. When there is no console, I probably don't care about the logs at all. I *may* care about

Re: [Development] How to have equivalent of function over-riding in Qml

Thanks for the very quick reply. Thank you for clarifying my understanding of correct derivation in Qml Regards, R.kiran Hi In continuation of the previous post - I now got it working to invoke the base class / derived class implementations correctly from extenal place. Now the