Re: [Qt-creator] Breakpoint Problem
In article <2b1e8f000910140009j4f271726h2366dda776dec...@mail.gmail.com>, Robert Caldecott wrote: > I am using 1.2.91 on Windows XP and am having a problem with breakpoints. > > I set a breakpoint and debug my applications - it triggers and all is > well. Each time I debug, that breakpoint works. However, if I remove > the breakpoint and set another one, it doesn't work and *no* > breakpoints are triggered. Only a restart of Qt Creator will fix > this. > I have the same issue with Creator in OS X. Only the first debug session works. Change anything and I have to restart Creator to get break point to trip. Very annoying. ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] QtCreator 1.2.92 is really great !
Hi ,
first eMail here , so first Thanks a lot for QtCreator is really gonna
make it so much more fun to code under linux.
at the company I work we are writing our UI in Qt but the low level libs
are in Standard C++ using Make and a lot of Boost .
I plan to use QtCreator as the IDE for all things C++ including the Core
stuff .
I created Project using the "Import of Makefile-based Project" template
and with a few tweak to the .config and .includes I was able to build
the project and get the output , auto completion etc working !! did
bring a gigantic smiles on my face :)
now to the part that I didn't managed to sort out so well .
1) Boost::shared_ptr
our low level libs are using Boost::shared_ptr around almost all our
object . and originally I though they were not supported . but trying to
build a small test for this eMail I notices that actually it was working
(an other massive smile in my face )
the original issue that I have noticed in some other place in our code is :
namespace core // our namespace for exemple
{
/// lift boost smart pointers into core namespace
using boost::shared_ptr;
}
then our pointer are declared
core::shared_ptr
this doesn't look to be supported by the completion/parser .
I can work my way around for now I think but is would be a useful
addition and is maybe not much work :)
2) Plugins
we are a fairly large team of developers and if usage of QtCreator takes
off (like I hope) it might be worth for us to write couple of customs
plugins for QtCreator to integrate it better to our workflow , is there
plugins tutorial or one of the plugins that is easy to understand that I
should look at to see what is possible ?
3) Project Template
we have couple of project type we can build and it would be great if we
could make template that would show up in "create New Project UI" ? is
that possible , changing the code and re-building qtCreator wouldn't be
a problem ?
4) Syntax Highlight for Namespace ?
I am getting greedy I guess but it would be very usefull for us to
hightlight the Class coming from a certain Namespace into certain colors
. I can see that it is not possible at the moment but I would be
interested to see if its possible without too much work , could someone
point me in the general direction ( files , class I need to look at ?)
That is it for now ,
Thanks a Lot for this Great tools !
Damien
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] GUI-Suggestion
On Fri, Oct 16, 2009 at 3:31 PM, Perepelica Alexander wrote: > Hello! > I propose create another solution (how is in Delphi) > 1. Create Object Slots Viewer, where user can see all slots (in first > column) from widget and if in code are realized methods then name of > this method (second column) > PS this is replacement for signal/slot editor > We don't need another viewer - the Designer's Signal/Slot editor is integrated into the IDE. It would be nice if for custom classes, the editor could pick up the slots defined in the class. > 2. If user double-click - create on_XXX_XXX method > 3. If enter in edit mode and enter method name then create such method > in code and place "connect" > > > * Danny Price [Fri, 16 Oct 2009 15:12:36 > +0100]: > > On Fri, Oct 16, 2009 at 3:01 PM, Andree Günther > > wrote: > > > > > Andre Poenitz schrieb: > > > > On Wed, Oct 14, 2009 at 03:52:33PM +0200, Andree Günther wrote: > > > > > > > >> Hello List, > > > >> > > > >> wouldnt it be a good Idea to create a slot by - lets say - > > > >> double-clicking a button? > > > >> > > > > > > > > Try the item in the context menu under the somewhat misleading > name > > > > "Go to slot". > > > Thats pretty much exactly what i wanted - thank you. > > > > > > > > > No, please don't do this. The standard behavior of the Designer has > been > > to > > set the name of a widget when double-clicking. It has been this way > for > > some > > time and is very convenient. This is also consistent with other GUI > > designers such as Interface Builder. When the Trolls created the MSVC > > plugin, they added the double-click-creates-slot behavor and > > 'on_xxx_clicked' syntax to appease VistualStudio users. When using the > > MSVC > > Qt Plugin, I would often create a slot by mistake when expecting the > > standard designer behaviour. Now that Nokia have removed the built-in > > designer from the MSVC plugin, this behaviour is somewhat redundant. > > > > Seperating the UI from the code is good design practice. Not only is > the > > 'on_xxx_signal' syntax ugly, it is less powerful and tightly couples > the > > name of UI widgets to the code. > > > > However, having it available via the menu is a nice compromise. > > > > > > > > > > I would suggest to select a default-Slot (ie Clicked() in case of > the > > > pushbutton) and set this > > > as default-behaviour for doubleclicks. I think thats what people > > expect, > > > isn't it? > > > > > > > That's fine for buttons but what abour everything else? Creator has > > awesome > > signal-slot completion - use it :) > > > > > > > > > > > > > I think i found a Bug with this: > > > > > > Creator doesnt remove the Metacall for the auto-generated Slot (for > > > example "on_startButton_clicked") when > > > the slot (and the Button in my case) is removed. Therfore > compilation > > > fails: > > > > > > undefined reference to `MainWindow::on_pushButton_clicked()' > > > > > > > Which is exactly why you should avoid doing this. Qt is NOT MFC. > > > > > > > > > > Dont know how to fix this, because the "MainWindow::qt_metacall" is > > not > > > part of "my" code and im not supposed > > > to twiddle with it, right? > > > > > > > > > BTW: Just a thought: When i change the pushButtons name to lets say: > > > startButton - it would be a good idea > > > to automatically change all depending slotnames - ie. > > > "on_pushButton_clicked". > > > > > > > > > Andre > > > > > > > > > > > > > > > Materialpruefungsamt Nordrhein-Westfalen > > > Marsbruchstrasse 186 > > > D-44287 Dortmund > > > Telefon: +49 (231) 4502-0 > > > Telefax: +49 (231) 458549 > > > E-mail: i...@mpanrw.de > > > Internet: www.mpanrw.de > > > USt.-IdNr.: DE 124 728 648 > > > > > > Brandpruefzentrum Erwitte > > > Auf den Thraenen 2 > > > D-59597 Erwitte > > > > > > Telefon: +49 (2943) 897-0 > > > Telefax: +49 (2943) 897-33 > > > ___ > > > 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 > > > > > -- > Thank you. > Perepelica Alexander > ___ > 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] When can we expect rename-file functionality?
Definately. The process currently is: 1) Select Remove file using right-click menu. 2) Cancel dialog offering to delete item. 3) Cancel SCM dialog offering to remove item from source control. 4) Switch to file system. 5) Use SCM client to rename file. 6) Switch to Creator and re-add file. 7) Cancel dialog offering to add file to SCM. 8) Re-run qmake if the file contained resources, ui or Q_OBJECT classes. 8 steps! Laborious! MSVC can do this. Eclipse can do this. And they're 3rd party tools. Why can't Creator do this?! On Fri, Oct 16, 2009 at 3:27 PM, Robert Caldecott < robert.caldec...@gmail.com> wrote: > This would be very useful. It should also offer to rename the file in > your version control system. > > > When can we expect to be able to rename files within the IDE? > ___ > 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] GUI-Suggestion
Hello! I propose create another solution (how is in Delphi) 1. Create Object Slots Viewer, where user can see all slots (in first column) from widget and if in code are realized methods then name of this method (second column) PS this is replacement for signal/slot editor 2. If user double-click - create on_XXX_XXX method 3. If enter in edit mode and enter method name then create such method in code and place "connect" * Danny Price [Fri, 16 Oct 2009 15:12:36 +0100]: > On Fri, Oct 16, 2009 at 3:01 PM, Andree Günther > wrote: > > > Andre Poenitz schrieb: > > > On Wed, Oct 14, 2009 at 03:52:33PM +0200, Andree Günther wrote: > > > > > >> Hello List, > > >> > > >> wouldnt it be a good Idea to create a slot by - lets say - > > >> double-clicking a button? > > >> > > > > > > Try the item in the context menu under the somewhat misleading name > > > "Go to slot". > > Thats pretty much exactly what i wanted - thank you. > > > > > No, please don't do this. The standard behavior of the Designer has been > to > set the name of a widget when double-clicking. It has been this way for > some > time and is very convenient. This is also consistent with other GUI > designers such as Interface Builder. When the Trolls created the MSVC > plugin, they added the double-click-creates-slot behavor and > 'on_xxx_clicked' syntax to appease VistualStudio users. When using the > MSVC > Qt Plugin, I would often create a slot by mistake when expecting the > standard designer behaviour. Now that Nokia have removed the built-in > designer from the MSVC plugin, this behaviour is somewhat redundant. > > Seperating the UI from the code is good design practice. Not only is the > 'on_xxx_signal' syntax ugly, it is less powerful and tightly couples the > name of UI widgets to the code. > > However, having it available via the menu is a nice compromise. > > > > > > I would suggest to select a default-Slot (ie Clicked() in case of the > > pushbutton) and set this > > as default-behaviour for doubleclicks. I think thats what people > expect, > > isn't it? > > > > That's fine for buttons but what abour everything else? Creator has > awesome > signal-slot completion - use it :) > > > > > > > > I think i found a Bug with this: > > > > Creator doesnt remove the Metacall for the auto-generated Slot (for > > example "on_startButton_clicked") when > > the slot (and the Button in my case) is removed. Therfore compilation > > fails: > > > > undefined reference to `MainWindow::on_pushButton_clicked()' > > > > Which is exactly why you should avoid doing this. Qt is NOT MFC. > > > > > > Dont know how to fix this, because the "MainWindow::qt_metacall" is > not > > part of "my" code and im not supposed > > to twiddle with it, right? > > > > > > BTW: Just a thought: When i change the pushButtons name to lets say: > > startButton - it would be a good idea > > to automatically change all depending slotnames - ie. > > "on_pushButton_clicked". > > > > > > Andre > > > > > > > > > > Materialpruefungsamt Nordrhein-Westfalen > > Marsbruchstrasse 186 > > D-44287 Dortmund > > Telefon: +49 (231) 4502-0 > > Telefax: +49 (231) 458549 > > E-mail: i...@mpanrw.de > > Internet: www.mpanrw.de > > USt.-IdNr.: DE 124 728 648 > > > > Brandpruefzentrum Erwitte > > Auf den Thraenen 2 > > D-59597 Erwitte > > > > Telefon: +49 (2943) 897-0 > > Telefax: +49 (2943) 897-33 > > ___ > > 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 -- Thank you. Perepelica Alexander ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] When can we expect rename-file functionality?
This would be very useful. It should also offer to rename the file in your version control system. > When can we expect to be able to rename files within the IDE? ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] GUI-Suggestion
I couldn't agree more. Please leave this as is! >Not only is the 'on_xxx_signal' syntax ugly, it is less powerful >and tightly couples the name of UI widgets to the code. ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] When can we expect rename-file functionality?
I know that this has been a requested feature for a long time and it *really* should have been available from the start. When I'm showing off creator to colleagues and I have to explain that it cannot rename files, their eyes roll! When can we expect to be able to rename files within the IDE? ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] GUI-Suggestion
On Fri, Oct 16, 2009 at 3:01 PM, Andree Günther wrote: > Andre Poenitz schrieb: > > On Wed, Oct 14, 2009 at 03:52:33PM +0200, Andree Günther wrote: > > > >> Hello List, > >> > >> wouldnt it be a good Idea to create a slot by - lets say - > >> double-clicking a button? > >> > > > > Try the item in the context menu under the somewhat misleading name > > "Go to slot". > Thats pretty much exactly what i wanted - thank you. > No, please don't do this. The standard behavior of the Designer has been to set the name of a widget when double-clicking. It has been this way for some time and is very convenient. This is also consistent with other GUI designers such as Interface Builder. When the Trolls created the MSVC plugin, they added the double-click-creates-slot behavor and 'on_xxx_clicked' syntax to appease VistualStudio users. When using the MSVC Qt Plugin, I would often create a slot by mistake when expecting the standard designer behaviour. Now that Nokia have removed the built-in designer from the MSVC plugin, this behaviour is somewhat redundant. Seperating the UI from the code is good design practice. Not only is the 'on_xxx_signal' syntax ugly, it is less powerful and tightly couples the name of UI widgets to the code. However, having it available via the menu is a nice compromise. > > I would suggest to select a default-Slot (ie Clicked() in case of the > pushbutton) and set this > as default-behaviour for doubleclicks. I think thats what people expect, > isn't it? > That's fine for buttons but what abour everything else? Creator has awesome signal-slot completion - use it :) > > > I think i found a Bug with this: > > Creator doesnt remove the Metacall for the auto-generated Slot (for > example "on_startButton_clicked") when > the slot (and the Button in my case) is removed. Therfore compilation > fails: > > undefined reference to `MainWindow::on_pushButton_clicked()' > Which is exactly why you should avoid doing this. Qt is NOT MFC. > > Dont know how to fix this, because the "MainWindow::qt_metacall" is not > part of "my" code and im not supposed > to twiddle with it, right? > > > BTW: Just a thought: When i change the pushButtons name to lets say: > startButton - it would be a good idea > to automatically change all depending slotnames - ie. > "on_pushButton_clicked". > > > Andre > > > > > Materialpruefungsamt Nordrhein-Westfalen > Marsbruchstrasse 186 > D-44287 Dortmund > Telefon: +49 (231) 4502-0 > Telefax: +49 (231) 458549 > E-mail: i...@mpanrw.de > Internet: www.mpanrw.de > USt.-IdNr.: DE 124 728 648 > > Brandpruefzentrum Erwitte > Auf den Thraenen 2 > D-59597 Erwitte > > Telefon: +49 (2943) 897-0 > Telefax: +49 (2943) 897-33 > ___ > 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] GUI-Suggestion
Andre Poenitz schrieb: > On Wed, Oct 14, 2009 at 03:52:33PM +0200, Andree Günther wrote: > >> Hello List, >> >> wouldnt it be a good Idea to create a slot by - lets say - >> double-clicking a button? >> > > Try the item in the context menu under the somewhat misleading name > "Go to slot". Thats pretty much exactly what i wanted - thank you. I would suggest to select a default-Slot (ie Clicked() in case of the pushbutton) and set this as default-behaviour for doubleclicks. I think thats what people expect, isn't it? I think i found a Bug with this: Creator doesnt remove the Metacall for the auto-generated Slot (for example "on_startButton_clicked") when the slot (and the Button in my case) is removed. Therfore compilation fails: undefined reference to `MainWindow::on_pushButton_clicked()' Dont know how to fix this, because the "MainWindow::qt_metacall" is not part of "my" code and im not supposed to twiddle with it, right? BTW: Just a thought: When i change the pushButtons name to lets say: startButton - it would be a good idea to automatically change all depending slotnames - ie. "on_pushButton_clicked". Andre Materialpruefungsamt Nordrhein-Westfalen Marsbruchstrasse 186 D-44287 Dortmund Telefon: +49 (231) 4502-0 Telefax: +49 (231) 458549 E-mail: i...@mpanrw.de Internet: www.mpanrw.de USt.-IdNr.: DE 124 728 648 Brandpruefzentrum Erwitte Auf den Thraenen 2 D-59597 Erwitte Telefon: +49 (2943) 897-0 Telefax: +49 (2943) 897-33 ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] GDB Debug helper
Friedmann, Friedemann Kleint wrote: > Thank you very much for your efforts. > The dumper DLL is injected into the debuggee process (see > sc/plugins/debugger/sharedlibraryinjector.*) by acquiring an access token, > opening the process and creating a remote thread that calls LoadLibrary (with > the name written to remote memory). > The OpenProcess() call, which according to the documentation requires the > SE_DEBUG privilege, fails. So I had half an our of time to check out qt-creator:1.3.0-beta from qt.gitorious.org before I will leave to Stralsund to run Rügenmarathon tomorrow. I made a debug version against the current Qt 4.6beta. This one is able to load the debug helper in unprivileged mode for both Qt4.6beta and Qt4.5.2. The QtCreator 1.3beta binary package is still not able to load the helper dll. regards Lars ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Problem with compile simple code
Yeah the Trolls love their lower-case names... On Fri, Oct 16, 2009 at 2:14 PM, André Pönitz wrote: > On Friday 16 October 2009 13:30:08 ext Danny Price wrote: > > > > > #include < QApplication.h > > > > #include < QMainWindow.h > > > > > That, by the way, should be > > > > #include > > #include > > > > The original version does not compile on case-sensitive file systems. > > > > Andre' > > > > > > Really? Is that why C++ libraries tend to use stub-include files with no > extensions? Surely '.h' is consistent on all platforms? > > There is no "QApplication.h" header with exact that capitalization. > There's only "qapplication.h" and "QApplication". On NTFS or such > "qapplication.h" will be found when using "QApplication.h", but it > will fail on, say, ext3. > > Andre' > ___ > 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] Problem with compile simple code
> It's not a case-sensitivity issue (C++ STL wasn't designed with > Windows in mind) but I don't know the true rationale. My hypotheses > include: .h is for C headers, not C++ headers; or the STL headers > don't have to actually exist on disk and are free to be provided by > the compiler. The truth may not be either of these. I don't know. > > Well I tend to use .hpp for c++ headers which fixes that 'issue'. I like that about Creator :) ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Problem with compile simple code
On Friday 16 October 2009 13:30:08 ext Danny Price wrote: > > > #include < QApplication.h > > > #include < QMainWindow.h > > > That, by the way, should be > > #include > #include > > The original version does not compile on case-sensitive file systems. > > Andre' > > > Really? Is that why C++ libraries tend to use stub-include files with no > extensions? Surely '.h' is consistent on all platforms? There is no "QApplication.h" header with exact that capitalization. There's only "qapplication.h" and "QApplication". On NTFS or such "qapplication.h" will be found when using "QApplication.h", but it will fail on, say, ext3. Andre' ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Problem with compile simple code
> Really? Is that why C++ libraries tend to use stub-include files with no > extensions? Surely '.h' is consistent on all platforms? It's not a case-sensitivity issue (C++ STL wasn't designed with Windows in mind) but I don't know the true rationale. My hypotheses include: .h is for C headers, not C++ headers; or the STL headers don't have to actually exist on disk and are free to be provided by the compiler. The truth may not be either of these. I don't know. /s/ Adam ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] Fwd: Attention: Some internal things were renamed
Umpf, now I forgot one import part after all :) * This change will be on qt.gitorious.org in about 12 hours (SHA1 is 77efc921c25bca81d7e4629c5f1d6e0ccb110c54) ++ Eike Begin forwarded message: > From: "Ziller Eike (Nokia-D-Qt/Berlin)" > Date: 16. Oktober 2009 14:58:39 MESZ > To: "qt-creator@trolltech.com" > Subject: [Qt-creator] Attention: Some internal things were renamed > > This is a notice to all of you compiling Qt Creator directly from git, > or even hack around it, or even in it. > (If you are merely using a binary package, you may ignore this mail.) > > The outstanding task to rename the internal classes/plugin that > implements "Locator" from "QuickOpen" to "Locator" has finally been > done. > We have the global renaming tool in the Qt Creator 1.3.0 beta now, so > that was an opportunity to finally do this boring task :) > > What that means for you, is that you'll need to make a clean build. > > At the very least you must run "qmake -r" and remove all occurrances > of QuickOpen.pluginspec and libQuickOpen.* from your lib/ folder (or, > mac users, from your application bundle). But I don't recommend to try > that minimal approach, best to remove your shadowbuild directory, or, > if you are doing in-source builds, consider using "git clean -dxf" > which removes all untracked files. > > "make clean" is *not* sufficient. And I'd suppose even "make > distclean" isn't. > > Have a nice weekend! > > ++ Eike > ___ > 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] Attention: Some internal things were renamed
This is a notice to all of you compiling Qt Creator directly from git, or even hack around it, or even in it. (If you are merely using a binary package, you may ignore this mail.) The outstanding task to rename the internal classes/plugin that implements "Locator" from "QuickOpen" to "Locator" has finally been done. We have the global renaming tool in the Qt Creator 1.3.0 beta now, so that was an opportunity to finally do this boring task :) What that means for you, is that you'll need to make a clean build. At the very least you must run "qmake -r" and remove all occurrances of QuickOpen.pluginspec and libQuickOpen.* from your lib/ folder (or, mac users, from your application bundle). But I don't recommend to try that minimal approach, best to remove your shadowbuild directory, or, if you are doing in-source builds, consider using "git clean -dxf" which removes all untracked files. "make clean" is *not* sufficient. And I'd suppose even "make distclean" isn't. Have a nice weekend! ++ Eike ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Problem with compile simple code
> > #include < QApplication.h > > > #include < QMainWindow.h > > > That, by the way, should be > > #include > #include > > The original version does not compile on case-sensitive file systems. > > Andre' > > Really? Is that why C++ libraries tend to use stub-include files with no extensions? Surely '.h' is consistent on all platforms? ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] 'smart' / 'type-aware' auto-complete
2009/10/16 Prashanth Udupa : > Yes it does.. probably the best auto complete implementation out there.. Apart from Intellisense, and possibly the C++ one in netbeans. The autocompleter in KDevelop4 also looks promising: http://zwabel.wordpress.com/2008/11/11/c-code-completion-rethought-kdevelop4-in-action/ Still it's not far off! :-) ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Keyboard shortcut for next/prev build error?
On Friday 16 October 2009 09:47:20 ext Robert Caldecott wrote: > I'm sure there are keyboard shortcuts that will navigate > forwards/backwards through the list of build errors, etc. but I can't > find any reference to this in the Qt Creator manual. Does anyone know > what they are? Much obliged! > F6, Shift F6. (Also works for search results.) Or Alt+number gives focus to the output pane, which can then be navigated with cursor keys and enter. Esc moves the focus back to the editor. Another Esc closes the output panes. daniel ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Keyboard shortcut for next/prev build error?
On Fri, Oct 16, 2009 at 08:47:20AM +0100, Robert Caldecott wrote: > I'm sure there are keyboard shortcuts that will navigate > forwards/backwards through the list of build errors, etc. but I can't > find any reference to this in the Qt Creator manual. Does anyone know > what they are? Much obliged! > hovering the little yellow arrows will reveal it: (shift-)f6. i think you need the to-be 1.3 branch for that, though. ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] GDB Debug helper
Hi, > I will try to investigate this and report about the results. Could you > point out, what the CreateProcess call looks like. Thank you very much for your efforts. The dumper DLL is injected into the debuggee process (see sc/plugins/debugger/sharedlibraryinjector.*) by acquiring an access token, opening the process and creating a remote thread that calls LoadLibrary (with the name written to remote memory). The OpenProcess() call, which according to the documentation requires the SE_DEBUG privilege, fails. Regards, Friedemann -- Friedemann Kleint Nokia, Qt Development Frameworks ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] 'smart' / 'type-aware' auto-complete
Yes it does.. probably the best auto complete implementation out there.. / Prashanth On Fri, Oct 16, 2009 at 1:31 PM, Christopher Rasch-Olsen Raa < christop...@technophile.info> wrote: > Hi, > > It might be that Qt Creator has this already but I've still not seen it. > Are > there any plans to make any support for type-aware autocomplete? Like if I > write > int myvariable = myobject->get > I'd then get a list of the methods on 'myobject' that starts with 'get' and > returns an integer or integer-compatible type first, followed by a list of > all > the other methods, > > Am I asking for something that's already there? > > ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] 'smart' / 'type-aware' auto-complete
Hi, It might be that Qt Creator has this already but I've still not seen it. Are there any plans to make any support for type-aware autocomplete? Like if I write int myvariable = myobject->get I'd then get a list of the methods on 'myobject' that starts with 'get' and returns an integer or integer-compatible type first, followed by a list of all the other methods, Am I asking for something that's already there? -- Med vennlig hilsen, Christopher Rasch-Olsen Raa Daglig Leder Technophile ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] GDB Debug helper
Friedemann, Friedemann Kleint wrote: >> Currently I don't have the time to dive deeper into this. But maybe you may >> help make QtCreator more verbose than just saying 'access denied'. > > This error message is unfortunately the the most verbose message we can get > at > this point ;-) I love it. > As Andre mentioned, we cannot really reproduce it; so, I can't quite put my > finger on it, but I have a feeling that this is caused by one of the security > restrictions to be found at: > > Control Panel\Administrative Tools\Local Security Policy\Local Policies > > The user should have at least: > > User Rights Assignment: Debug Programs > > permission (although debugging works for non-administrative users that do not > have that right on my machine). The documentation says this right is necessary for user who want to attach to any process (not only their own ones). This should not be the case for debug processes started out of QtCreator. Anyway, granting this right to my unprivileged account does not change the behaviour. > If that is granted and the dumper still fails, there might be some other > setting in the way (eg Security Options). I will try to investigate this and report about the results. Could you point out, what the CreateProcess call looks like. regards Lars > > Regards, > Friedemann ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] Keyboard shortcut for next/prev build error?
I'm sure there are keyboard shortcuts that will navigate forwards/backwards through the list of build errors, etc. but I can't find any reference to this in the Qt Creator manual. Does anyone know what they are? Much obliged! http://qtcreator.blogspot.com/ ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] GDB Debug helper
Hi, > I saw that it tries to load the dll. with / as path separators instead of > \. May that cause problems? Gdb actually wants forward slashes. > Currently I don't have the time to dive deeper into this. But maybe you may > help make QtCreator more verbose than just saying 'access denied'. This error message is unfortunately the the most verbose message we can get at this point ;-) As Andre mentioned, we cannot really reproduce it; so, I can't quite put my finger on it, but I have a feeling that this is caused by one of the security restrictions to be found at: Control Panel\Administrative Tools\Local Security Policy\Local Policies The user should have at least: User Rights Assignment: Debug Programs permission (although debugging works for non-administrative users that do not have that right on my machine). If that is granted and the dumper still fails, there might be some other setting in the way (eg Security Options). Regards, Friedemann -- Friedemann Kleint Nokia, Qt Development Frameworks ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
