Re: [Qt-creator] QtCreator 2.0.0 Does not highlight user's Types.

2010-06-29 Thread Oleg Shalnev
I see. Thanks a lot.

2010/6/28 Thorbjørn Lindeijer 

> On 06/26/2010 04:23 PM, ext Oleg Shalnev wrote:
> > It's strange because some revisions ago there were no problems with this
> > new feature.
> > Again only standard Qt types highlignt now.
>
> This feature exists on only Qt Creator master, which is to become the Qt
> Creator 2.2 release eventually. Likely you have used a master build at
> some point.
>
> Regards,
> Bjørn
>
> --
> Thorbjørn Lindeijer
> Software Engineer
> Nokia, Qt Development Frameworks
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>



-- 
Oleg Shalnev (Kalpa Project)
--
mailto: o...@kalpa.ru
skype:  oleg_shalnev
jabber:  oleg.shal...@gmail.com
http://kalpa.ru
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


[Qt-creator] Error building debug helper, MSVC Static

2010-06-29 Thread Charles N Burns
When I click "rebuild" for the debug helper for a static build of Qt
using MSVC 2008 and Creator 2.0, I get the error below. This is
probably because the debugger doesn't support static build of Qt, Qt
Creator should know this and display an error like "Debugging helper
not supported for static Qt builds."

Best regards,

--Charles Burns


-

Building debugging helper library in
C:/Qt/4.6.3-msvc-static/qtc-debugging-helper/

Running C:/Program Files (x86)/Microsoft Visual Studio
9.0/VC/BIN/nmake.exe distclean...

Microsoft (R) Program Maintenance Utility Version 9.00.30729.01

Copyright (C) Microsoft Corporation. All rights reserved.

"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\nmake.exe"
-f Makefile.Release distclean

Microsoft (R) Program Maintenance Utility Version 9.00.30729.01

Copyright (C) Microsoft Corporation. All rights reserved.

del tmp\obj\release_static\gdbmacros.obj

del tmp\obj\release_static\gdbmacros.intermediate.manifest release\gdbmacros.exp

Could Not Find 
C:\Qt\4.6.3-msvc-static\qtc-debugging-helper\tmp\obj\release_static\gdbmacros.intermediate.manifest

del release\gdbmacros.dll

Could Not Find 
C:\Qt\4.6.3-msvc-static\qtc-debugging-helper\release\gdbmacros.dll

del Makefile.Release

"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\nmake.exe"
-f Makefile.Debug distclean

Microsoft (R) Program Maintenance Utility Version 9.00.30729.01

Copyright (C) Microsoft Corporation. All rights reserved.

del tmp\obj\debug_static\gdbmacros.obj

Could Not Find 
C:\Qt\4.6.3-msvc-static\qtc-debugging-helper\tmp\obj\debug_static\gdbmacros.obj

del

--
"Be kind, for everyone you meet is fighting a hard battle." --Plato
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


Re: [Qt-creator] Printing directly to the printer instead of PDF or PS creation

2010-06-29 Thread Christophe Meessen




Le 29/06/2010 14:43, Tobias Hunger a écrit :

  On 29.06.2010 14:28, ext Christophe Meessen wrote:
  
  
Is there a way to configure QtCreator to print directly to a printer ? A
binding with CUPS would be preferable.

  
  All configured printers should show up in creator's print dialog. We 
just tested this on ubuntu 10.04 and it does work here.

Do other (Qt?) applications show the list of printers?
  


Other desktop applications do show the printer list without problem
(I'm running Gnome). But not QtCreator. 
This Ubuntu 10.04 installation is an upgrade and not a fresh install. 

Apparently I had Qt 4.6.2 installed through synaptic. I didn't
uninstalled it. It is split in many packages and I don't know which one
to remove. 

I then have downloaded the Qt 4.7 with QtCreator 2.0 and run it as root
to have it installed in /opt. I then added a soft link qt to point to
this directory. 

I then added the path to the Qt 4.7 libraries using the commands
> sudo -s
> echo "/opt/qt/lib" > /etc/ld.so.conf.d/qtlibs.conf
> ldconfig -v

ldconfig -v shows the Qt 4.7 library and the 4.6.2 too. 

I checked the QtCreator binary is static (ldd ./qtcreator), so
libraries doesn't come into play here. 

What I see is this :



As name the only options are PDF or Postscript into a file. No buttons
give access to a list of printers. I couldn't find anything in the
progam options. 

Another information is that the CUPS printers are not local, but
managed by a server. 




___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


Re: [Qt-creator] Application used to create Qt Creator screenshot in documentation

2010-06-29 Thread Jaco Naude
Thank you Prashanth,
That's it.

On Tue, Jun 29, 2010 at 9:19 AM, Prashanth Udupa
 wrote:
> You can checkout
> http://ariya.blogspot.com/2008/06/creating-fancy-screenshots-with.html
>
> / Prashanth
>
> On Tue, Jun 29, 2010 at 2:13 PM, Jaco Naude  wrote:
>> Hi
>>
>> Does someone know which tool was used to create the image with the 3
>> screenshots of creator next to each other? I've seen this before in
>> other projects like Speedcrunch
>> 9http://www.speedcrunch.org/en_US/index.html) as well.
>>
>> Thanks,
>> Jaco
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


[Qt-creator] ActiveQt and MinGW

2010-06-29 Thread Robert Caldecott
Apologies for posting this here guys but I am struggling to find the
definitive answer to this and a Creator guru may know the answer.

I am trying to develop a COM server using the latest Qt/Qt Creator SDK and
the MinGW toolchain.  My first issue was that the code fails to build
because I didn't have a copy of the MS MIDL compiler.  I installed the
latest MS Windows SDK and now MIDL runs but complains because it can't find
cl.exe (the MS compiler).  So I downloaded Visual Studio Express and added
cl.exe to the PATH and now the MIDL step works but I get an 'Failed to
register application' error (I am building the ActiveQt comapp sample).

So ... can I build ActiveQt apps using MinGW or will I have to use the MS
toolchain (and the appropriate MSVC 2008 build of Qt)?  I develop on
different machines and would like to avoid MSVC if possible but I think I'm
out of luck...

I wondered if it is possible to have MIDL use gcc instead?  If this is
possible then I'm not sure how I'd edit my .pro file to change the MIDL
steps.
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


Re: [Qt-creator] Printing directly to the printer instead of PDF or PS creation

2010-06-29 Thread Tobias Hunger
On 29.06.2010 14:28, ext Christophe Meessen wrote:
> Is there a way to configure QtCreator to print directly to a printer ? A
> binding with CUPS would be preferable.

Hi Christophe!

All configured printers should show up in creator's print dialog. We 
just tested this on ubuntu 10.04 and it does work here.

Do other (Qt?) applications show the list of printers?

Best Regards,
Tobias

-- 
Tobias Hunger
Software Engineer
Nokia, Qt Development Frameworks

Nokia gate5 GmbH
Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany
Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
Umsatzsteueridentifikationsnummer: DE 812 845 193
Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


[Qt-creator] Printing directly to the printer instead of PDF or PS creation

2010-06-29 Thread Christophe Meessen
Hello,

I'm on Ubuntu 10.4 and installed the latest SDK with QtCreator 2.0. I 
have many source files to print and hoped to find a better method than 
the pdf file generation to print a source file. I have many pages to 
print and the pdf file is laborious, though I like the output format.

Is there a way to configure QtCreator to print directly to a printer ? A 
binding with CUPS would be preferable.

--
Ch. Meessen

___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


Re: [Qt-creator] Qt Creator 2.0 does not load my old .user file

2010-06-29 Thread Tobias Hunger
On 29.06.2010 13:41, ext Danny Price wrote:
> Of course, maybe it still makes sense to have an option to disable the
> "shadow-build by default" thing for those not interested in building for
> different targets.

For those of you using the master branch:

Double-clicking on the path in the target setup page of the wizard does 
switch between shadow build (default) and in-source build. Of course 
this only works where it is possible switch between those two (and only 
for "New" builds).

I admit that this is not really obvious and welcome your suggestions on 
how to improve this page of the wizard.

Best Regards,
Tobias

-- 
Tobias Hunger
Software Engineer
Nokia, Qt Development Frameworks

Nokia gate5 GmbH
Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany
Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
Umsatzsteueridentifikationsnummer: DE 812 845 193
Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


Re: [Qt-creator] Qt Creator 2.0 does not load my old .user file

2010-06-29 Thread Danny Price
>
> A properly written .pro file should indeed not break when using shadow
> builds.
>

There's very little documentation (other than working examples like Creator
itself which are huge) on how to write a .pro file 'properly'. Creator
itself confounds this by providing overly simple templates. I had to turn to
google to figure out how to setup basic things like library links, include
paths and change-dependencies. These are functions that the IDE should
provide. Better wizards would go a long way to helping here (eg. a Wizard
for setting up a library link capable of setting up the pro file 'properly'
and a SUBDIR wizard).


>
> Of course, I can sympathize with the problems many are having now and
> the lack of documentation. It was a hard choice to make between breaking
> some projects by doing shadow builds by default (which can generally be
> fixed), or not being able to support building against different Qt
> configurations properly (desktop, Maemo, S60, Simulator, etc.)


I don't understand why shadow builds were made the default - they've been an
optional feature of Creator for some time now so if you needed them, they
were there. Why the change?


> Of course, maybe it still makes sense to have an option to disable the
> "shadow-build by default" thing for those not interested in building for
> different targets.
>

Yes this would be a good idea, a return to 1.x behavior. The problem is that
the pro.user files have to be regularly being re-generated.



> Regards,
> Bjørn
>
> --
> Thorbjørn Lindeijer
> Software Engineer
> Nokia, Qt Development Frameworks
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


Re: [Qt-creator] Qt Creator 2.0 does not load my old .user file

2010-06-29 Thread Thorbjørn Lindeijer
On 06/29/2010 12:44 PM, ext John Vilburn wrote:
> Using a shadow build breaks my .pro file on Mac because my project uses
> SUBDIRS to build some frameworks, and then builds the final .app. In the
> .app I include those frameworks as private frameworks. The rule to add
> those frameworks looks something like this:
>
> PRIVATE_FRAMEWORKS.files = ../Framework1/Framework1.framework 
> ../Framework2/Framework2.framework
>
> In this case, the ../ is interpreted by the build as relative to the
> source directory, not the shadow build directory. But those frameworks
> are created in the shadow build directory. What is the proper method to
> specify those paths so they will be relative to the build directory
> whether it is a shadow build or not?

Since these are indeed products of your build, the proper way to refer 
to them is probably by doing it relative from $$OUT_PWD:

http://doc.qt.nokia.com/4.6/qmake-variable-reference.html#out-pwd

> Is the assumption being made that OBJECTS_DIR, UI_DIR, and others should 
> always be relative paths? If that assumption is true, then it seems to me 
> that specifying a shadow build directory should not break the .pro file. 
> Perhaps the difficulty with shadow builds arises when developers put absolute 
> paths in OBJECTS_DIR and such, because then the OBJECTS_DIR would override 
> the shadow build dir, rather than work with it. Am I right? If I am missing 
> something, please explain in more detail how setting the shadow build dir "is 
> quite different from setting OBJECTS_DIR, UI_DIR, etc."

I think they should really always be relative, yes. I'm not sure what 
the use-case would be of using absolute paths. A properly written .pro 
file should indeed not break when using shadow builds.

Of course, I can sympathize with the problems many are having now and 
the lack of documentation. It was a hard choice to make between breaking 
some projects by doing shadow builds by default (which can generally be 
fixed), or not being able to support building against different Qt 
configurations properly (desktop, Maemo, S60, Simulator, etc.)

Of course, maybe it still makes sense to have an option to disable the 
"shadow-build by default" thing for those not interested in building for 
different targets.

Regards,
Bjørn

-- 
Thorbjørn Lindeijer
Software Engineer
Nokia, Qt Development Frameworks
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


Re: [Qt-creator] Qt Creator 2.0 does not load my old .user file

2010-06-29 Thread John Vilburn
Using a shadow build breaks my .pro file on Mac because my project uses SUBDIRS 
to build some frameworks, and then builds the final .app. In the .app I include 
those frameworks as private frameworks. The rule to add those frameworks looks 
something like this:

PRIVATE_FRAMEWORKS.files = ../Framework1/Framework1.framework 
../Framework2/Framework2.framework

In this case, the ../ is interpreted by the build as relative to the source 
directory, not the shadow build directory. But those frameworks are created in 
the shadow build directory. What is the proper method to specify those paths so 
they will be relative to the build directory whether it is a shadow build or 
not?

Perhaps cases like this are the reason for the negative reactions I have seen 
for shadow builds. Shadow builds can indeed break projects if the projects are 
not defined carefully enough. And until shadow builds became so prominent in Qt 
Creator, it was not apparent that anything was amiss in the .pro file. I like 
the idea of shadow builds, but some good documentation would be helpful. The 
only mention of shadow builds I can find is in the Windows CE section. And it 
only discusses doing shadow builds of Qt by running configure in each shadow 
build directory. I can find nothing on how to properly configure my .pro file 
for shadow builds of my product.

Thanks,
John

On Jun 29, 2010, at 12:01 AM, John Vilburn wrote:

> On Jun 28, 2010, at 11:13 PM, Thorbjørn Lindeijer wrote:
> 
>> That Qt Creator allows you to set the directory in which to do the build 
>> should not be a surprise, nor should it be surprising that this is 
>> stored in a .user file, since its up to each developer.
>> 
>> Note that this is quite different from setting OBJECTS_DIR, UI_DIR, etc. 
>> so there is no duplication here. The main purpose of the shadow builds 
>> is to build against different Qt configurations.
> 
> Is the assumption being made that OBJECTS_DIR, UI_DIR, and others should 
> always be relative paths? If that assumption is true, then it seems to me 
> that specifying a shadow build directory should not break the .pro file. 
> Perhaps the difficulty with shadow builds arises when developers put absolute 
> paths in OBJECTS_DIR and such, because then the OBJECTS_DIR would override 
> the shadow build dir, rather than work with it. Am I right? If I am missing 
> something, please explain in more detail how setting the shadow build dir "is 
> quite different from setting OBJECTS_DIR, UI_DIR, etc."
> 
> I do find it an annoyance that when loading a project into Qt Creator for the 
> first time, that I can find no way to NOT specify a shadow build. I have to 
> go into the project settings after it is loaded and uncheck the shadow build 
> option. Did I miss something there?
> 
> John
> 
> 
> 
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator

___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


Re: [Qt-creator] Qt Creator 2.0 does not load my old .user file

2010-06-29 Thread John Vilburn
On Jun 28, 2010, at 11:13 PM, Thorbjørn Lindeijer wrote:

> That Qt Creator allows you to set the directory in which to do the build 
> should not be a surprise, nor should it be surprising that this is 
> stored in a .user file, since its up to each developer.
> 
> Note that this is quite different from setting OBJECTS_DIR, UI_DIR, etc. 
> so there is no duplication here. The main purpose of the shadow builds 
> is to build against different Qt configurations.

Is the assumption being made that OBJECTS_DIR, UI_DIR, and others should always 
be relative paths? If that assumption is true, then it seems to me that 
specifying a shadow build directory should not break the .pro file. Perhaps the 
difficulty with shadow builds arises when developers put absolute paths in 
OBJECTS_DIR and such, because then the OBJECTS_DIR would override the shadow 
build dir, rather than work with it. Am I right? If I am missing something, 
please explain in more detail how setting the shadow build dir "is quite 
different from setting OBJECTS_DIR, UI_DIR, etc."

I do find it an annoyance that when loading a project into Qt Creator for the 
first time, that I can find no way to NOT specify a shadow build. I have to go 
into the project settings after it is loaded and uncheck the shadow build 
option. Did I miss something there?

John



___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


Re: [Qt-creator] Application used to create Qt Creator screenshot in documentation

2010-06-29 Thread Prashanth Udupa
You can checkout
http://ariya.blogspot.com/2008/06/creating-fancy-screenshots-with.html

/ Prashanth

On Tue, Jun 29, 2010 at 2:13 PM, Jaco Naude  wrote:
> Hi
>
> Does someone know which tool was used to create the image with the 3
> screenshots of creator next to each other? I've seen this before in
> other projects like Speedcrunch
> 9http://www.speedcrunch.org/en_US/index.html) as well.
>
> Thanks,
> Jaco
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


Re: [Qt-creator] Qt Creator 2.0 does not load my old .user file

2010-06-29 Thread Thorbjørn Lindeijer
On 06/29/2010 12:07 AM, ext Leo Spalteholz wrote:
> On Mon, Jun 28, 2010 at 11:56 AM, Danny Price
>   wrote:
>> Agreed but this is hardly a new problem. Some of us have been complaining 
>> about pro.user files since before v1.0 :)
>
> Right, but it seems the .user files are taking on more and more
> functionality and making this worse.
> Now we have this build directory field in the projects tab, which
> clutters my file system with top level directories even though I
> already set up my pro file just the way I like it (with OBJECTS_DIR,
> UI_DIR, RCC_DIR, MOC_DIR = ./build and so forth).

Qt Creator simply mimics the way you use qmake in this regard. You've 
always had the option of doing a shadow build in a different directory 
by simply doing something like:

$ mkdir build
$ cd build
$ qmake /path/to/myprofile.pro

I frequently use this method to test builds with different Qt versions.

That Qt Creator allows you to set the directory in which to do the build 
should not be a surprise, nor should it be surprising that this is 
stored in a .user file, since its up to each developer.

Note that this is quite different from setting OBJECTS_DIR, UI_DIR, etc. 
so there is no duplication here. The main purpose of the shadow builds 
is to build against different Qt configurations. That it also keeps your 
source directory clean is only a pleasant side-effect.

Regards,
Bjørn

-- 
Thorbjørn Lindeijer
Software Engineer
Nokia, Qt Development Frameworks
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


[Qt-creator] Application used to create Qt Creator screenshot in documentation

2010-06-29 Thread Jaco Naude
Hi

Does someone know which tool was used to create the image with the 3
screenshots of creator next to each other? I've seen this before in
other projects like Speedcrunch
9http://www.speedcrunch.org/en_US/index.html) as well.

Thanks,
Jaco
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator


Re: [Qt-creator] Menu bar grayed out when accesing it with shortcuts

2010-06-29 Thread eike.ziller

On Jun 29, 2010, at 8:24 AM, ext Tomás Ortí wrote:

> Hi.
> When I try to access the menu bar with shortcuts (Alt+MenuLetter), the menus 
> get grayed out.
> Let me give an example:
> 
> - Use Alt+E to access Edit menu.
> - Use arrow keys to move in the menu an (or A to go to Advanced menu)
> - The menus get grayed out and are not accesible.
> 
> If you do the same using the mouse, there is no problem.

If you are on Windows, this bug is fixed for the next release: QTCREATORBUG-865


-- 
Eike Ziller
Software Engineer
Nokia, Qt Development Frameworks

Nokia gate5 GmbH
Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany
Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
Umsatzsteueridentifikationsnummer: DE 812 845 193
Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori




___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator