On 14/08/15 08:25, "Sarajärvi Tony"
wrote:
>> -Original Message-
>> From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
>> project.org [mailto:development-
>> bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
>> Thiago Macieira
>> Sent: 14. elokuuta 2015 3:40
> -Original Message-
> From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
> project.org [mailto:development-
> bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
> Thiago Macieira
> Sent: 14. elokuuta 2015 3:40
> To: development@qt-project.org
> Subject: [Develo
I recently tried to fix a very simple bug in Qt 4.8 but I can't get the change
to integrate because the CI seems to have fallen into disrepair.
Instead of using valuable QA time in fixing the CI for 4.8, I'd like to propose
instead that we simply disable the CI for that version and close Qt 4.8
On Thursday 13 August 2015 10:29:31 Turunen Tuukka wrote:
> Like Thiago and other have pointed out we of course would like to have the
> content of the new module well suited for Qt before it can become part of a
> Qt release. I think the best way to achieve this is to do the work within
> the Qt P
On Thursday 13 August 2015 10:32:42 Dominik Holland wrote:
> > Another option is to split the category name by the dots and select the
> > first letter of each section. So "qt.qpa.windows" is "qqw", while
> > "qt.widgets.gestures" is "qwg".
>
> Using that approach i'm already getting 4 clashes of
On 13.08.2015 11:47, Oswald Buddenhagen wrote:
> moin,
>
> the qtonpi mailing list didn't have a single message in close to a year;
> interest@ and development@ serve the remaining needs much better at this
> point.
> to cut down maintenance effort, i'd like to shut the list down, leaving
> only t
Hi all.
Is it possible to show a video from the one Camera to multiple VideoOutputs?
E.g. this code:
import QtQuick 2.4
import QtMultimedia 5.4
Rectangle {
id: root
Camera { id: cam }
Column {
VideoOutput { source: cam; width: 50; height: 50 }
VideoOutput {
> -Original Message-
> From: development-bounces+tuukka.turunen=theqtcompany.com@qt-
> project.org [mailto:development-
> bounces+tuukka.turunen=theqtcompany@qt-project.org] On Behalf Of
> Dominik Holland
> Sent: 13. elokuuta 2015 12:37
> To: André Somers
> Cc: development@qt-project.o
But it has actually been used to deprecate single enum values. Here is an
example from QTextFormat:
class Q_GUI_EXPORT QTextFormat
{
Q_GADGET
public:
enum FormatType {
InvalidFormat = -1,
BlockFormat = 1,
CharFormat = 2,
ListFormat = 3,
#if QT_DEPRECATED_SI
moin,
the qtonpi mailing list didn't have a single message in close to a year;
interest@ and development@ serve the remaining needs much better at this
point.
to cut down maintenance effort, i'd like to shut the list down, leaving
only the archives intact. objections?
if you want to "nominate" ot
On 08/13/2015 11:08 AM, André Somers wrote:
>
>
>> IMHO the users of QtGeniviExtras and the DLT logging are totally aware
>> of how the system works and want to have full control over it.
>> DLT is only known in the automotive space and there it's only used for
>> GENIVI linux based systems. So
> IMHO the users of QtGeniviExtras and the DLT logging are totally aware
> of how the system works and want to have full control over it.
> DLT is only known in the automotive space and there it's only used for
> GENIVI linux based systems. So i think we talk about a logging solution
> which 90%
On 08/12/2015 04:36 PM, Thiago Macieira wrote:
> On Wednesday 12 August 2015 14:26:26 Robert Griebl wrote:
Every LoggingCategory (In DLT it's called Context) needs to have a 3
characters long unique identifier and a Description.
>>>
>>> Stupid API limitation. Can you convince GENIVI to
13 matches
Mail list logo
