> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [...]
> On the contrary, the end-user on Windows expects the application logs to be
> in a file somewhere near the executable if it's not a system service. So in my
> opinion the logs shouldn't write in
On Wed, Jul 9, 2014 at 8:41 PM, travik wrote:
>>
>> 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
>
> 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
Hello everyone,
I partly agree with Corentin on that.
On Linux the end-user application should use journald to write logs
since the user expects it to be there. The in-development application
though should still use stderr or both since it's much easier to look
into Creator's Application Output w
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 abou
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 message
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 syste
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 optio
== 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
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) i
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
D
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 wit
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
We have the same problem here in Designer. The 4 MB restriction of System V
shared memory makes it really useless for cross platform use.
Maybe we could use a mmap version for Mac? Best would be a switchable version.
;-)
Best, Marco
From: development-boun
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
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
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 derived1.method1()
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 Sys
Hi, I would like to have equivalent of compile time polymorphism in in
Qml. a.k.a function overriding.
I know inheritance can be obtained by including the base-class in derived
class. (A realisation of the principle called inheritance by composition)
I also want to have some default implementati
19 matches
Mail list logo
