Hi,
Am Nov 3, 2009 um 8:28 PM schrieb ext Pedro Santos:
Hello,
I have a really annoying bug in Qt-creator 1.2.1 on my linux system.
It takes
nearly 100% of the CPU time after start and continues in that way.
Then it
often hangs on close, so I have to kill it. It has worked for some
Am 04.11.2009 09:50, schrieb Eike Ziller:
I heavily suspect the indexing of the documentation files that is done
when Qt Creator finds new documentation. This should be a once-only
operation, if that successfully finished once, it should never happen
again (if you don't add more Qt versions at
Hi Eike,
Thanks for your reply. I have to make a correction to my original post: it
is *Windows 7* running in VirtualBox on MAC OS X.
Qt Creator reads the location of the devices.xml from the registry:
HKEY_LOCAL_MACHINE\Software\Symbian\EPOC SDKs\CommonPath
This key exists and is correct but
Thank you very much for answering. The problem is finally solved. The
OTHER_FILES must have a path relative to the .pri file while the include
and source files must be given with a path relative to the .pro file.
This is what confused me. My fault, sorry.
I now can also add the .html file to
Hello André,
André Pönitz wrote:
I have two pieces of information to share:
1. Today there have been changes made to Qt Creator that require very
recent Qt 4.6 sources to compile. So whoever builds Creator from sources
will most likely have to compile Qt first.
The change
Hallo, thanks this has worked. For the future it would be favorable if
Qt-creator would show a statusbar like indexing 80% #... I can
imagine that many people, specially on slow systems, can misunderstand this as
error.
There IS such a status bar; it appears above the Run button
On Tuesday 03 November 2009 18:01:10 ext Gena Cid wrote:
Hi!
I've just noticed that not all fields of simple data array are shown in a
pop-up
watch window. Better look at the screenshot.
Thanks for the report. It should be fixed now and appear in the public
repo within 12 hours from now.
There IS such a status bar; it appears above the Run button in the
left sidebar, although if you have a small screen it might get covered
up.
Well, you are right that we have a few indexing progress bars
already (e.g. when parsing your code),
but we don't show any for the Help indexing.
This is a rather simplified version of the test case I am working with, but I
assume it reproduces the issue:
class Foo
{
friend class Bar;
int m_myint;
};
class Bar
{
void doSomething() {
foo.m_myint = 5;
}
Foo foo;
};
When renaming Foo::m_myint, refactoring misses the
