On Friday 13 November 2015, René J. V. Bertin wrote:
> Richard Moore wrote:
> > 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
> That's because operator<< for QStrings always quotes them. You can do one of
> two ways to get rid of them:
>
> qDebug().noquote() << QString(MY_STRING); or
> qDebug() << MY_STRING;
>
> or, even better, if you care about the actual output format:
>
> std::cout << MY_STRING
On Friday 13 November 2015 22:26:40 Murphy, Sean wrote:
> Because the following code prints "Hello You" on the command line -
> including the quotes. However I was trying to get it to just print Hello
> You (with no quotes).
>
> #include
> #include
> #include
>
> int main(int argc, char *argv[
On Friday 13 November 2015 21:55:41 René J. V. Bertin wrote:
> Richard Moore wrote:
> > 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
Hi,
Here's something that's been bugging me: Each time I install or reinstall Qt4
or
Qt5 (Linux style "system-style" install, e.g. through under Linux or through
MacPorts) the documentation list available in the Assistant is reset.
That's a user-specific setting AFAIK; I can still imagine that
Richard Moore wrote:
> 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 supp
Ok then, I need to review all that it's clear.
Thank you a thousand times for your input, it helps a lot to know that
it's something wrong with my own code.
I'll post back when fixed
Le 13-11-2015 20:10, Edward Sutton a écrit :
>> On Nov 13, 2015, at 1:01 PM, maitai wrote:
>>
>>> And
On Nov 13, 2015, at 1:01 PM, maitai
mailto:mai...@virtual-winds.org>> wrote:
>And just to make sure I understand well, if you press your app icon "copy to
>MyApp" your app launches and all is fine? If this is the case then the problem
>must be on my side obviously
Yes. My Qt 5.5 widget app l
And just to make sure I understand well, if you press your app icon
"copy to MyApp" your app launches and all is fine? If this is the case
then the problem must be on my side obviously.
Le 13-11-2015 19:56, Edward Sutton a écrit :
>> On Nov 13, 2015, at 12:50 PM, maitai wrote:
>>
>> Thank
On Nov 13, 2015, at 12:50 PM, maitai
mailto:mai...@virtual-winds.org>> wrote:
Thanks Edward for your fast answer.
>That is working also if your app is not in the background (i.e not started)?
Yes. Since Qt 5.4 and currently using Qt 5.5.1
I just closed my app to make sure.
Then I went to i
Thanks Edward for your fast answer.
That is working also if your app is not in the background (i.e not
started)?
Le 13-11-2015 19:42, Edward Sutton a écrit :
> I am using a pure Qt 5.5.1 iOS widgets app. Disclaimer: This solution works
> but may not be the best solution. Recommendations f
I am using a pure Qt 5.5.1 iOS widgets app. Disclaimer: This solution works
but may not be the best solution. Recommendations for a cleaner approach are
welcome.
Using Qt 5.5.1 I added myApplicationDelegate.mm that posts an fileOpenEvent.
It would be nice if this was built into Qt. See below
Hello all,
Since I updated to 5.5, I cannot launch my application by opening an
email attachment or such methods, for file extensions that have been
registered for my app in info.plist
I can open the documents only if the app is already running.
I can see in the app's log the following messa
Our .pro files have things like this:
DESTDIR = $$quote(../IgorPhoenixFolder)
Does that provide any traction?
-John Weeks
WaveMetrics, Inc.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On Friday 13 November 2015 10:26:47 Kimmerle Markus wrote:
> Hi,
>
> I downloaded the sources for QtRemoteObject from
> https://github.com/qtproject/playground-qtremoteobjects as a ZIP file. When
> trying to compile it under Windows 7, Qt 5.5.1, MinGW 4.9.2 using qmake ->
> make in the root direct
On Fri, Nov 13, 2015 at 1:00 AM, Julius Bullinger <
julius.bullin...@asctec.de> wrote:
> Hello Adam,
>
>
>
> do you use the new environment variables QT_AUTO_SCREEN_SCALE_FACTOR=1 ?
>
> Additionally, make sure to unset the deprecated QT_DEVICE_PIXEL_RATIO.
>
>
>
> You can do this in your shell fo
Very probable.
The fix
Windows: Introduce delayed population to the FreeType font database.
https://codereview.qt-project.org/#/c/106411/
explictly states:
The Windows CE version is unchanged.
Nobody explains why.
Regards,
Gunnar Roth
Gesendet: Freitag, 13. November 2015 um 14:1
> My recommendation would be to go in a different direction. The only time I do
> stuff like this is when I add 3rd party code into my build trees.
> If this is your situation, then you probably have to do it.
I'm starting to lean in this direction. One additional problem I'm seeing with
this app
Could it be the same issue as QTBUG-43774 [1]?
[1] https://bugreports.qt.io/browse/QTBUG-43774
From: Interest [mailto:interest-boun...@qt-project.org] On Behalf Of Christian
Nielsen
Sent: Friday, 13 November 2015 12:08 PM
To: Gunnar Roth
Cc: interest@qt-project.org
Subject: Re: [Interest] Why d
The issue was indeed font initialization. I commented out the line in
void QWindowsFontDatabaseFT::populateFontDatabase()
that populates the font database with all system fonts. Now Qt only loads the
family of the default font at start-up.
From: Gunnar Roth [mailto:gunnar.r...@gmx.de]
Sent: Mond
Hi,
I downloaded the sources for QtRemoteObject from
https://github.com/qtproject/playground-qtremoteobjects as a ZIP file. When
trying to compile it under Windows 7, Qt 5.5.1, MinGW 4.9.2 using qmake -> make
in the root directory, it fails with
qremoteobjectsource.h:46:50: fatal error:
QtRem
On 11/13/2015 02:51 AM, Murphy, Sean wrote:
But if I want my text to be a little more interesting and have spaces in it, it
fails. Changing the DEFINES line in the .pro to:
DEFINES += MY_STRING=\\\"Hello You\\\"
refuses to compile:
I think the semi-official algorithm for quoting in .pro fil
Hello Adam,
do you use the new environment variables QT_AUTO_SCREEN_SCALE_FACTOR=1 ?
Additionally, make sure to unset the deprecated QT_DEVICE_PIXEL_RATIO.
You can do this in your shell for testing, and programmatically with qputenv
[1].
Best regards,
Julius
Von: Interest [mailto:interest-bo
23 matches
Mail list logo
