>You can do this, given:
Nobody does that. We always write: * You bla, or you boo, or you foo, and in
this case we would normally write: You bla, you boo, or you foo. Even better:
You bla, boo, or foo. You are inventing problems that don't exist.
From:
Op 02/06/2016 om 21:47 schreef André Pönitz:
On Wed, Jun 01, 2016 at 03:36:43PM +0200, Olivier Goffart wrote:
On Mittwoch, 1. Juni 2016 12:56:12 CEST Simon Hausmann wrote:
Hi,
I'm in favorof changing our coding style to adopt the model you call "butt
ugly" because I find it more appealing an
Hi,
Op 03/06/2016 om 08:28 schreef Martin Smith:
but it is very structurally clean and in some circumstances I prefer it due to
that.
The structure is a comma separated list. Historically, the comma has always been placed directly
after the first of two list items. The comma tells the reader
>but it is very structurally clean and in some circumstances I prefer it due to
>that.
The structure is a comma separated list. Historically, the comma has always
been placed directly after the first of two list items. The comma tells the
reader that another list item will follow. There is noth
On Wednesday 01 June 2016, Marc Mutz wrote:
> Hi,
>
> There seems to have been a silent underground move to uglify the Qt sources
> , by using commas to introduce lines
> . I have no idea where this came from
>
I am probably one of those introducing it since it comes from WebKit coding
style. So
>
> Why would anyone bother to count votes before any (theoretically binding
> or non-binding, doesn't seem to matter) result of voting gets ignored by
> the next submitter anyway?
I think the votes are meant for 'ratifying' the coding guidelines. And
the hope that submitters _will_ follow the rul
On Wed, Jun 01, 2016 at 03:36:43PM +0200, Olivier Goffart wrote:
> On Mittwoch, 1. Juni 2016 12:56:12 CEST Simon Hausmann wrote:
> > Hi,
> >
> > I'm in favorof changing our coding style to adopt the model you call "butt
> > ugly" because I find it more appealing and I find that it makes diffs
> >
On Wed, Jun 01, 2016 at 02:57:27PM +0200, Dominik Holland wrote:
> +1 for changing they coding style
-1 for anything that's not applied uniformly within a reasonably short
time to the whole codebase.
More often than not I really don't care too much *what* the change is,
but I am getting sick of s
Hi,
just a short note, we already added API for overwriting the timeout in 5.7. See
http://doc-snapshots.qt.io/qt5-5.7/qmodbusrtuserialmaster.html#setInterFrameDelay
But as seen here
http://code.qt.io/cgit/qt/qtserialbus.git/tree/src/serialbus/qmodbusrtuserialmaster_p.h#n294
we missed to upda
> You can't do that with timing on a non-real-time task.
Quite so! The Modbus spec has been written for the PLC's, where are used
the Real-Time OS (or for 'bare metal' hardwares).
I have added some ideas, how to avoid it to QTBUG-53767
BR,
Denis
2016-06-02 16:02 GMT+03:00 Thiago Macieira :
>
On quinta-feira, 2 de junho de 2016 11:42:27 BRT Alexander Blasche wrote:
> Certain error cases can only be detected if you make assumptions about
> timeouts. Otherwise there is no way to determine where one packet stops and
> where the next one begins.
You can't do that with timing on a non-real-
On 2nd June 2016 at 13:32, Milla Pohjanheimo mentioned
> We bumped into a compiler bug specific for g++ 5.2.1 ...
> There are issues with gcc 4.9.2 also ...
and asked
> What do you think, where is the best place to document these issues?
> Is it
> supported platforms page,
This should, at least,
Nevermind, for some reason I was not able to read the docs properly:
If the minimum frame rate is equal to the maximum frame rate, the frame rate is
fixed. If not, the actual frame rate fluctuates between the minimum and the
maximum.
Sorry
From: Tobias Haslop
Hello,
I want to implement a backend for SVS-Vistek Gigabit Ethernet cameras, but I
see no way to set the camera's framerate.
There is the FrameRateRange, but I am not sure about its meaning:
Does setting a framerate range guarantee for each consecutive frame to arrive
in a certain timespan?
On quinta-feira, 2 de junho de 2016 11:59:20 BRT Marc Mutz wrote:
> On Saturday 20 February 2016 19:04:18 Thiago Macieira wrote:
> > It would buy us, if we raised to GCC 4.8 too:
> > - deleted and defaulted members
> >
> > (nsdmi, delegating constructors, template aliases require GCC 4.7)
>
> A
Yes ! That's it. Thanks Eike.
My request is toward 5.7.0 though. Targeting 5.8 means other 6 months of broken
videos :)
- Messaggio originale -
Da: Eike Ziller
A: Massimo Callegari
Cc: Sergio Martins ; "development@qt-project.org"
Inviato: Giovedì 2 Giugno 2016 14:30
Oggetto: Re: [D
> On Jun 2, 2016, at 12:03 PM, Massimo Callegari via Development
> wrote:
>
> 1) Ubuntu 16.04 delivers Qt 5.5.1
> 2) I am using Qt 5.6.0 official release (Linux x64). Not some PPA, nor Ubuntu
> stuff.
>
https://bugreports.qt.io/browse/QTBUG-53668 ?
Br, Eike
>
> - Messaggio originale -
On Thursday 02 June 2016 13:17:45 Martin Smith wrote:
> >The two space indented colon in the coding style is even more awkward,
> >having to manually indent the colon instead of using the editor's tab
> >feature, plus it breaks the "put things at the end rule".
>
> emacs has handled it correctly f
> -Original Message-
> From: Development [mailto:development-
> bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Denis Shienkov
> Sent: Thursday, 2 June 2016 7:11
> To: development@qt-project.org
> Subject: Re: [Development] modbus over serial port on windows 7 ?
>
> > only t
We bumped into a compiler bug specific for g++ 5.2.1 when running CI for dev
branch on RHEL 7.2 (gcc 5.2.1). Nested structs don't get their constructors
called under some circumstances. See:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67550.
A possible workaround for the issue can be found fr
>The two space indented colon in the coding style is even more awkward, having
>to
>manually indent the colon instead of using the editor's tab feature, plus it
>breaks the
>"put things at the end rule".
emacs has handled it correctly for me for at least two decades. I just hit
return it goes
On 01/06/16 14:56, Simon Hausmann wrote:
Hi,
I'm in favorof changing our coding style to adopt the model you call
"butt ugly" because I find it more appealing and I find that it makes
diffs easier to read.
+2
Bar::Bar(Bla *b)
: Foo(b)
, m_baz(123)
, m_biz(321)
{
}
aligns and read
01.06.2016, 15:41, "Marc Mutz" :
> Hi,
>
> There seems to have been a silent underground move to uglify the Qt sources
> , by using commas to introduce lines
> . I have no idea where this came from
It's codified by WebKit coding style, and many people here have contributed to
QtWebKit:
https:/
Also, if you don't believe me, this is what comes out from Qt's CI system:
ldd Qt5.6.0/5.6/gcc_64/plugins/mediaservice/libgstmediaplayer.so
linux-vdso.so.1 => (0x7fff4da5f000)
libqgsttools_p.so.1 =>
/opt/Qt5.6.0/5.6/gcc_64/plugins/mediaservice/../../lib/libqgsttools_p.so.1
(0x7f25ddfb
1) Ubuntu 16.04 delivers Qt 5.5.1
2) I am using Qt 5.6.0 official release (Linux x64). Not some PPA, nor Ubuntu
stuff.
- Messaggio originale -
Da: Sergio Martins
A: development@qt-project.org; Massimo Callegari
Inviato: Giovedì 2 Giugno 2016 12:00
Oggetto: Re: [Development] Video playb
On Thursday, 2 June 2016 08:17:08 WEST Massimo Callegari via Development
wrote:
> Hi everyone,
>
> is it just me or QtMultimedia 5.6.0 video playback is quite broken on Ubuntu
> 16.04 ?
>
> I think the reason is that Qt 5.6.0 (and 5.7.0 as well) are still built
> against gstreamer 0.10, which is
On Saturday 20 February 2016 19:04:18 Thiago Macieira wrote:
> It would buy us, if we raised to GCC 4.8 too:
> - deleted and defaulted members
> (nsdmi, delegating constructors, template aliases require GCC 4.7)
According to qcompilerdetection.h, deleted and defaulted members are available
from
Le mercredi 01 juin 2016 à 15:36 +0200, Olivier Goffart a écrit :
>
> Anyone has a config file for clang-format to use with qt so it can be used
> with git-clang-format?
>
This is the most relevant question in this kinda trollish kind of topic.
Everyone has different opinion on these matter
Hi everyone,
is it just me or QtMultimedia 5.6.0 video playback is quite broken on Ubuntu
16.04 ?
I think the reason is that Qt 5.6.0 (and 5.7.0 as well) are still built against
gstreamer 0.10, which is quite obsolete now.
In fact, I built Qt 5.7.0 myself with gstreamer 1.0 and video playback w
29 matches
Mail list logo
