Excellent. Looks exactly like my problem. Thanks, Mike.
On 5/4/2015 11:14 AM, Mike Chinander wrote:
Could possibly be due to the version of binutils you are using; check out
this thread on the gcc email list:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57017
On Mon, May 4, 2015 at 12:03 P
On Mon, May 04, 2015 at 05:11:38PM +0300, Robert Iakobashvili wrote:
> On Mon, May 4, 2015 at 4:47 PM, Edward Sutton
> wrote:
>
> > Hi Robert,
> >
> > Thank you for your patience and detailed steps. I understand now.
> >
> > All is good!
> >
> > -Ed
> >
>
> Great.
>
> I'd say that normall
Could possibly be due to the version of binutils you are using; check out
this thread on the gcc email list:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57017
On Mon, May 4, 2015 at 12:03 PM, Bob Hood wrote:
> I'm building the Qt Service v2.7 project under CentOS 6.6 using GCC 4.8.2:
>
> [bob@c
I'm building the Qt Service v2.7 project under CentOS 6.6 using GCC 4.8.2:
[bob@centos64 qtservice_64_dll]$ gcc --version
gcc (GCC) 4.8.2 20140120 (Red Hat 4.8.2-15)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warrant
Thanks Robert,
Yes, I was not expecting to select device under “Kits". I expected to select
it under “Devices” since that is where it displayed “Ready to use”. Thank you
for explaining.
I created a Qt Creator suggestion to add a device list next to the green debug
start button.
Add UI nex
On Mon, May 4, 2015 at 3:43 PM, Edward Sutton wrote:
> HI Robert,
>
> In Qt Creator open your project.
> Click at Project -> Manage Kits
>
> In "Manage Kits" select your iPad device instead of your iPhone
> to be used for the kit concerned.
>
> You can also get to "Manage Kits" from Preferences
>
HI Robert,
In Qt Creator open your project.
Click at Project -> Manage Kits
In "Manage Kits" select your iPad device instead of your iPhone
to be used for the kit concerned.
You can also get to "Manage Kits" from Preferences
I do not understand. "Manage Kits" displays targets rather than devic
> If you define your classes in .h files (not .cpp files) and run qmake,
> then you don't need to #include anything that moc produces.
And if I only use a Q_OBJECT based class in one .cpp file I should
now have to break it out into it's own header file just to make the
build system happy.
I acce
On 4 May 2015 at 11:43, Hamish Moffatt wrote:
>
> On 04/05/15 13:08, Nikos Chantziaras wrote:
> > On 03/05/15 13:54, Igor Mironchik wrote:
> >> Hi guys,
> >>
> >> I asked before about similar problem on Windows but now I have the same
> >> problem on Linux.
> >>
> >> I have messagebox.cpp file tha
On 05/03/2015 11:17 PM, Thiago Macieira wrote:
> On Monday 04 May 2015 06:08:55 Nikos Chantziaras wrote:
>> On 03/05/15 13:54, Igor Mironchik wrote:
>>> Hi guys,
>>>
>>> I asked before about similar problem on Windows but now I have the same
>>> problem on Linux.
>>>
>>> I have messagebox.cpp file
Does anyone have any suggestions for dealing with high-DPI environments
in Qt on Windows? Does Qt have anything built-in which helps?
On Mac we drop in @2x images, enable Qt::AA_UseHighDpiPixmaps and life
is mostly good. But I don't think this happens on Windows (and usually
devicePixelRatio is
11 matches
Mail list logo
