Hi Sean,
Den 13-11-2015 kl. 02:51 skrev Murphy, Sean:
I'm trying to add a defined string in my .pro file to be inserted by the
preprocessor at compile time and I'm having trouble when it has spaces in it.
Here's a really simplistic example:
[...]
But if I want my text to be a little more inter
By running two QtCreator processes, having the child process delay for 30
seconds, and then attaching to it using the second QtCreator after the process
in the first QtCreator start()'d it, I was able to determine that it was
segfaulting on me during its start-up. It was only doing this when be
I'm trying to add a defined string in my .pro file to be inserted by the
preprocessor at compile time and I'm having trouble when it has spaces in it.
Here's a really simplistic example:
test.pro:
QT += core
QT -= gui
TARGET = testDefinesWithSpacesConsole
CONFIG += console
We've just started testing our application using Qt 5.6 (self built from
Nov. 10 git checkout).
It appears that the behavior of QDesktopWidget::logicalDpiX (and Y) has
changed since Qt 5.5.
We bought a Dell Inspiron 15 laptop with a High DPI display. If I open
Control Panel, choose Display, and c
On Friday 13 November 2015 00:11:43 Elvis Stansvik wrote:
> Actually it's not wrong. It's the const char* version that was added in
> C++11.
>
> http://en.cppreference.com/w/cpp/error/runtime_error is wrong (I'm
> guessing that's where you looked as well).
Right. The C++98 standard in 19.1.6 [lib
2015-11-12 23:57 GMT+01:00 Elvis Stansvik :
> 2015-11-12 23:22 GMT+01:00 Igor Mironchik :
>>
>>
>> On 13.11.2015 00:44, Thiago Macieira wrote:
>>>
>>> On Thursday 12 November 2015 23:56:20 Igor Mironchik wrote:
>
> First of all, allocating memory when throwing exceptions is bad
> practi
On Thu, Nov 12, 2015 at 9:14 PM, Diego Iastrubni wrote:
> So... the official statement from Qt is that elliptic curves is a ... "safe"
> encryption to be used in the wild...?
Where did you get this quote from?
--
Giuseppe D'Angelo
___
Interest mailing
2015-11-12 23:22 GMT+01:00 Igor Mironchik :
>
>
> On 13.11.2015 00:44, Thiago Macieira wrote:
>>
>> On Thursday 12 November 2015 23:56:20 Igor Mironchik wrote:
First of all, allocating memory when throwing exceptions is bad
practice.
Avoid it by redesigning your code.
>>>
>>> Ca
On 13.11.2015 00:44, Thiago Macieira wrote:
On Thursday 12 November 2015 23:56:20 Igor Mironchik wrote:
First of all, allocating memory when throwing exceptions is bad practice.
Avoid it by redesigning your code.
Can you, please, explain why allocating memory when throwing exception
is bad pr
Thiago Macieira wrote:
> Just because it's NSA, doesn't mean it's bad.
Not the place to be opinionated about such topics here, but I'd say at least
one
verb in that statement should be in the past tense O:-)
> The project has no position on supporting LibreSSL. If we want to do that, I'd
> lik
On Thursday 12 November 2015 17:01:40 Mike Jackson wrote:
> Thanks for the verification. Didn’t want to waste time digging and reporting
> something that was already known.
>
> I will assume there are plans to move QtAssistant to QWebEngine? Qt 5.6 or
> Qt 6.0?
I haven't heard anything and Qt 5.6
Thanks for the verification. Didn’t want to waste time digging and reporting
something that was already known.
I will assume there are plans to move QtAssistant to QWebEngine? Qt 5.6 or Qt
6.0?
—
Mike Jackson
> On Nov 12, 2015, at 4:49 PM, Thiago Macieira
> wrote:
>
> On Thursday 12 November
On Thursday 12 November 2015 14:33:00 Bob Hood wrote:
> I had a look at the code for QProcess, which seems to be doing standard
> fork/exec launching of the process, whereas, if I'm not mistaken, popen()
> uses the shell to run it. Is that the only difference here? Should I be
> running the QPr
On Thursday 12 November 2015 16:19:16 Mike Jackson wrote:
> We have built Qt 5.5.1 and we noticed in QtAssistant that none of the normal
> page style is there any more. We did omit WebKit since (a) it wouldn’t
> build successfully (b) we did not need it for our project. From poking
> around at the
On Friday 13 November 2015 00:28:46 Igor Mironchik wrote:
> On 13.11.2015 00:15, Matthew Woehlke wrote:
> > On 2015-11-12 15:56, Igor Mironchik wrote:
> >> Can you, please, explain why allocating memory when throwing exception
> >> is bad practice? Or just can you give a link on any article about t
On Thursday 12 November 2015 23:56:20 Igor Mironchik wrote:
> > First of all, allocating memory when throwing exceptions is bad practice.
> > Avoid it by redesigning your code.
>
> Can you, please, explain why allocating memory when throwing exception
> is bad practice? Or just can you give a link
I have an issue with QProcess in Qt 5.5.1 under Linux. I have the following
QProcess code to launch a command-line process (also a Qt executable):
player.process = ProcessPointer(new QProcess(this));
connect(player.process.data(), &QProcess::readyReadStandardOutput, this,
&Mediator::sl
On 13.11.2015 00:15, Matthew Woehlke wrote:
On 2015-11-12 15:56, Igor Mironchik wrote:
Can you, please, explain why allocating memory when throwing exception
is bad practice? Or just can you give a link on any article about this
question Thank you.
What if the exception occurred because y
On 12 November 2015 at 20:14, Diego Iastrubni wrote:
> So... the official statement from Qt is that elliptic curves is a ...
> "safe" encryption to be used in the wild...?
>
>
We provide facilities that let you choose which ciphersuites are enabled.
We also support plain text.
> (still reme
On 2015-11-12 15:56, Igor Mironchik wrote:
> Can you, please, explain why allocating memory when throwing exception
> is bad practice? Or just can you give a link on any article about this
> question Thank you.
What if the exception occurred because you are out of memory?
--
Matthew
___
We have built Qt 5.5.1 and we noticed in QtAssistant that none of the normal
page style is there any more. We did omit WebKit since (a) it wouldn’t build
successfully (b) we did not need it for our project. From poking around at the
pre-built binaries of Qt it looks like QtAssistant uses QWebKit
On 12.11.2015 23:38, Thiago Macieira wrote:
On Thursday 12 November 2015 23:05:37 Igor Mironchik wrote:
Hi folks,
Is it a bug or feature?
First of all, allocating memory when throwing exceptions is bad practice.
Avoid it by redesigning your code.
Can you, please, explain why allocating mem
On Thursday 12 November 2015 23:05:37 Igor Mironchik wrote:
> Hi folks,
>
> Is it a bug or feature?
First of all, allocating memory when throwing exceptions is bad practice.
Avoid it by redesigning your code.
> TextFileViewException::TextFileViewException( const QString & what )
> :std::run
On Thursday 12 November 2015 22:14:38 Diego Iastrubni wrote:
> (still remember in college how I was thought that this is a safe encryption
> because the NSA developed it... and it is fast...)
The same NSA that made changes to the RSA algorithm in the 80s and made it
stronger than random occurrenc
So... the official statement from Qt is that elliptic curves is a ...
"safe" encryption to be used in the wild...?
(still remember in college how I was thought that this is a safe encryption
because the NSA developed it... and it is fast...)
If this was not clear:
I think that Thiago meant to say
Hi folks,
Is it a bug or feature?
class TextFileViewException
:public std::runtime_error
{
public:
explicit TextFileViewException( const QString & what );
~TextFileViewException() throw();
//! \return What happened as QString.
const QString & whatAsQString() const;
priv
On Thursday November 12 2015 18:21:24 André Somers wrote:
> Why else would you ever need it: QObject itself has it after all...
Exactly, I was under the impression that its functionality would be inherited.
Does it show I have little to no experience writing Qt code from scratch? :)
> See above
On Thursday 12 November 2015 16:29:03 René J.V. Bertin wrote:
> Hello,
>
> Rebuilding Qt 5.5.0 with libressl 2.2.4 installed instead of openssl I got
> this error:
>
> qt-everywhere-opensource-src-5.5.0/qtbase/src/network/ssl/qsslcontext_openss
> l.cpp:347:33: error: ‘SSL_CTRL_SET_CURVES’ was not
On Thursday 12 November 2015 15:59:06 Alejandro Exojo wrote:
> El Tuesday 10 November 2015, Thiago Macieira escribió:
> > > What's the problem with static QString?
> >
> > There's no actual error or problem, but it's just poor coding practice.
>
> That certainly has surprised me. If you just mean
> Op 12 nov. 2015 om 17:40 heeft René J. V. Bertin het
> volgende geschreven:
>
> René J.V. Bertin wrote:
>
> Hi,
>
> Sorry for forgetting completely about this thread, my bad. It turned out that
> I
> hadn't completely understood the editor class. Rather than having a single
> instance o
René J.V. Bertin wrote:
Hi,
Sorry for forgetting completely about this thread, my bad. It turned out that I
hadn't completely understood the editor class. Rather than having a single
instance of that class and then a list of open documents, there is actually a
list of instances of that editor
Hello,
Rebuilding Qt 5.5.0 with libressl 2.2.4 installed instead of openssl I got this
error:
qt-everywhere-opensource-src-5.5.0/qtbase/src/network/ssl/qsslcontext_openssl.cpp:347:33:
error: ‘SSL_CTRL_SET_CURVES’ was not declared in this scope
SSL_CTRL_SET_CURVE
El Tuesday 10 November 2015, Thiago Macieira escribió:
> > What's the problem with static QString?
>
> There's no actual error or problem, but it's just poor coding practice.
That certainly has surprised me. If you just mean that it could be abused, and
that it could
> It's a static non-trivia
33 matches
Mail list logo
