Re: [Qt-creator] Feature Request: separate keys to (un)comment

[M. Bashir Al-Noimi]

Mar wrote:
> Hi,
>
> I can see that it is a smart option to have one shortcut for 
> comment/uncomment. But I would prefare the option to set two different 
> shortcuts, one for comment and one for uncomment. E.g. when I wand to 
> uncomment a block, then I have to mark the exact block, if I mark a line 
> too much (e.g. a line in the midle whitch is not comment out) then a 
> separate key for uncomment would be much bether.
>   
I'm absolutely agree with you and i want to add a sub request too.

I suggest to add a shortcut for documentation comments (like /** */).

What you think?



-
Best Regards
Muhammad Bashir Al-Noimi
My Blog: http://mbnoimi.net/


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

Re: [Qt-creator] Backtracking from a ctrl+click on method ?

[Tim Hutt]

>>> and there is also the arrows (on the top of the edit pane)
>>>
>> Sorry, I couldn't see these. I just see the scroll pane with the
>> functions (very useful) and the scroll pane for the opened files.
>> The navigation arrows are only visible in the help browser, not with the
>> edit window.
>
> Strange. What version of Qt Creator is that?

They aren't in 1.2.1, but the video on the Qt labs blogs shows they
definitely are in 1.3.
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Backtracking from a ctrl+click on method ?

[Andre Poenitz]

On Mon, Oct 26, 2009 at 10:16:03PM +0100, Christophe Meessen wrote:
> Thank you. It works great, thank you.
>
> I guess it is documented, but I couldn't find it in the QtCreator  
> documentation. Do you have a link to the documentation page for these  
> features ? I would like to check and learn other shortcuts. I searched  
> in Qt Creator's documentation.

Check out Tools->Options->Environment->Keyboard.

> Brian McGillion wrote:
>> and there is also the arrows (on the top of the edit pane)
>>   
> Sorry, I couldn't see these. I just see the scroll pane with the  
> functions (very useful) and the scroll pane for the opened files.
> The navigation arrows are only visible in the help browser, not with the  
> edit window.

Strange. What version of Qt Creator is that?

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

Re: [Qt-creator] plugin_qtestlib

[Coda Highland]

On Mon, Oct 26, 2009 at 4:05 PM, Bravo.Alex  wrote:
> Adam, you are exactly correct.
> Then following your logic, if test is run, but not recompiled,
> then there's no build stage happening and no running of a test.
> (if running of test is part of building).

I think you missed my point. The test phase is BETWEEN the "build" and
"run" phases but it is more closely linked to the "build" phase than
the "run" phase and therefore would not be inappropriate for it to
output its results into the "Build Issues" tab. I was never proposing
to run the tests as part of the build process itself.

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

Re: [Qt-creator] Backtracking from a ctrl+click on method ?

[Brian McGillion]

Hi,

I am not sure which version they appeared in, but if you use the snapshot
from
ftp://ftp.trolltech.com/qtcreator/snapshots/latest/

they will be there.  As regards documentation I am not sure where the
latest is.

Br,
Brian


> Thank you. It works great, thank you.
>
> I guess it is documented, but I couldn't find it in the QtCreator
> documentation. Do you have a link to the documentation page for these
> features ? I would like to check and learn other shortcuts. I searched
> in Qt Creator's documentation.
>
> Brian McGillion wrote:
>> and there is also the arrows (on the top of the edit pane)
>>
> Sorry, I couldn't see these. I just see the scroll pane with the
> functions (very useful) and the scroll pane for the opened files.
> The navigation arrows are only visible in the help browser, not with the
> edit window.
>
> --
> Ch. Meessen
> ___
> 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] Backtracking from a ctrl+click on method ?

[Christophe Meessen]

Thank you. It works great, thank you.

I guess it is documented, but I couldn't find it in the QtCreator 
documentation. Do you have a link to the documentation page for these 
features ? I would like to check and learn other shortcuts. I searched 
in Qt Creator's documentation.


Brian McGillion wrote:

and there is also the arrows (on the top of the edit pane)
  
Sorry, I couldn't see these. I just see the scroll pane with the 
functions (very useful) and the scroll pane for the opened files.
The navigation arrows are only visible in the help browser, not with the 
edit window.


--
Ch. Meessen


smime.p7s
Description: S/MIME Cryptographic Signature
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] plugin_qtestlib

[Bravo.Alex]

Adam, you are exactly correct.
Then following your logic, if test is run, but not recompiled, 
then there's no build stage happening and no running of a test.
(if running of test is part of building).


I think we are just talking about different things here.

Let's clarify the scenario we are talking about here.
First facts:
1. You are saying there's a main application, say app.exe, right?
2. There's unit testing code for some classes of that application. 

Now questions:
1. Do you have test code separate from you production code or together with it?
2. How do you run these tests? Do you have test.exe or do you have a test mode 
of app.exe?
3. What happens if app.exe is actually not an application, but a library 
library.dll?

When answering these questions, just remember that we need to cover all the 
cases...

-Original Message-
From: qt-creator-boun...@trolltech.com 
[mailto:qt-creator-boun...@trolltech.com] On Behalf Of Coda Highland
Sent: Monday, October 26, 2009 1:47 PM
To: qt-creator@trolltech.com
Subject: Re: [Qt-creator] plugin_qtestlib

Running the unit tests is conceptually part of building your
application. You don't have to clean and recompile your entire
application every time you make a little change; why is this any
different? Running the "Test" step doesn't have to recompile the whole
mess if it's already built (and, ideally, up to date).

/s/ Adam

On Mon, Oct 26, 2009 at 3:30 PM, Bravo.Alex  wrote:
> If running is part of building, then how do run the test several times (most 
> likely to step through it with debugger)? Do you also build several times?
>
> That's one of the reasons building is separate from running - you build once 
> and then run as many times as you want.
>
>
>
> -Original Message-
> From: qt-creator-boun...@trolltech.com 
> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Thomas Dähling
> Sent: Monday, October 26, 2009 1:21 PM
> To: qt-creator@trolltech.com
> Subject: Re: [Qt-creator] plugin_qtestlib
>
> I have always considered running the unit tests to be part of the build
> process; personally I always set unit tests up in a way that they are
> run once I compiled a project. Keeps the turnaround time as short as
> possible.
>
> So, with that background, I am fairly much in favour of using the "build
> issues" panel for these kind of things.
>
> jm2c
>
> /Thomas
>
> Bravo.Alex schrieb:
>> Adam,
>>
>>> Build Issues would be a valid output target
>>
>> What happens when the test itself has build issues - which is very common 
>> due to changes in the code being tested?
>> Are you saying that running of test can be considered part of building?
>>
>> Aren't building and running separate things according to Qt Creator design?
>>
>>
>> -Original Message-
>> From: qt-creator-boun...@trolltech.com 
>> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Coda Highland
>> Sent: Monday, October 26, 2009 12:39 PM
>> To: qt-creator@trolltech.com
>> Subject: Re: [Qt-creator] plugin_qtestlib
>>
>> Honestly I don't know if I want to set the precedent of allowing
>> plugins to just arbitrarily add new tabs there.
>>
>> I think Build Issues would be a valid output target, though; it's
>> already intended for jumping to the relevant places in the code and
>> one could argue that failing a unit test is a build issue.
>>
>> /s/ Adam
>>
>> On Mon, Oct 26, 2009 at 2:18 PM, Robert Caldecott
>>  wrote:
>>> I like the idea of a dedicated QTest output pane - will you be able to 
>>> double-click on failures to jump directly to the code?  That would be 
>>> brilliant.
>>>
>>> 2009/10/26 Bravo.Alex 
> Plus that it's not so high in the list of things to do.


 If you are talking about qtcrea...@nokia team, it makes a lot of sense.

 But that's why you guys opened development to outside world, right?

 So that we can help you improve already great product.





 So, back to qtestlibplugin:

 After bringing it back from the dead, I realized that the architecture of 
 this plugin might need adjustment:

 Right now it has its own type of output "Test Results" (just like "Build 
 Issues", "Application Output" and 2 more).

 But, as this picture shows, there's not much space for different types of 
 output:



 Besides it doesn't make much sense to "pollute" IDE's screen with "Test 
 Results" button and list entry

 for applications that have nothing to do with QTestLib.



 It looks like there should be as little presence for this plugin as 
 possible in the IDE's GUI.

 Ideally, this plugin should show itself only if output of a program is in 
 QTestLib format.



 Thus this plugin really provides a different format of "Application 
 Output", not a different output pane.



 So proposed adjustment to this plugin is to be able to have several 
 formats of "Application Output".
>>

Re: [Qt-creator] plugin_qtestlib

[Thomas Dähling]

If I have to debug my unit tests then usually something smells about the 
test already - normally each test should be rather simple and be 
stand-alone runnable (i.e. test B should not have to rely upon a run of 
test A); so in most cases I should end up with some really small piece 
of code where I can see the error from reading the code without actually 
having to debug this. Being very verbose in your "test failed" messages 
helps a lot with this, too.

However, in the (very rare) case of actually having to debug the test I 
usually explicitely set the test project to be the debuggee.

Also, changing the test *and* the code to be tested at the same time is 
rarely a good idea, as you might not directly know why the test is broken.

/Thomas

Bravo.Alex schrieb:
> If running is part of building, then how do run the test several times (most 
> likely to step through it with debugger)? Do you also build several times?
> 
> That's one of the reasons building is separate from running - you build once 
> and then run as many times as you want.
> 
> 
> 
> -Original Message-
> From: qt-creator-boun...@trolltech.com 
> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Thomas Dähling
> Sent: Monday, October 26, 2009 1:21 PM
> To: qt-creator@trolltech.com
> Subject: Re: [Qt-creator] plugin_qtestlib
> 
> I have always considered running the unit tests to be part of the build 
> process; personally I always set unit tests up in a way that they are 
> run once I compiled a project. Keeps the turnaround time as short as 
> possible.
> 
> So, with that background, I am fairly much in favour of using the "build 
> issues" panel for these kind of things.
> 
> jm2c
> 
> /Thomas
> 
> Bravo.Alex schrieb:
>> Adam,
>>
>>> Build Issues would be a valid output target
>> What happens when the test itself has build issues - which is very common 
>> due to changes in the code being tested? 
>> Are you saying that running of test can be considered part of building?
>>
>> Aren't building and running separate things according to Qt Creator design?
>>
>>
>> -Original Message-
>> From: qt-creator-boun...@trolltech.com 
>> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Coda Highland
>> Sent: Monday, October 26, 2009 12:39 PM
>> To: qt-creator@trolltech.com
>> Subject: Re: [Qt-creator] plugin_qtestlib
>>
>> Honestly I don't know if I want to set the precedent of allowing
>> plugins to just arbitrarily add new tabs there.
>>
>> I think Build Issues would be a valid output target, though; it's
>> already intended for jumping to the relevant places in the code and
>> one could argue that failing a unit test is a build issue.
>>
>> /s/ Adam
>>
>> On Mon, Oct 26, 2009 at 2:18 PM, Robert Caldecott
>>  wrote:
>>> I like the idea of a dedicated QTest output pane - will you be able to 
>>> double-click on failures to jump directly to the code?  That would be 
>>> brilliant.
>>>
>>> 2009/10/26 Bravo.Alex 
> Plus that it's not so high in the list of things to do.

 If you are talking about qtcrea...@nokia team, it makes a lot of sense.

 But that's why you guys opened development to outside world, right?

 So that we can help you improve already great product.





 So, back to qtestlibplugin:

 After bringing it back from the dead, I realized that the architecture of 
 this plugin might need adjustment:

 Right now it has its own type of output "Test Results" (just like "Build 
 Issues", "Application Output" and 2 more).

 But, as this picture shows, there's not much space for different types of 
 output:



 Besides it doesn't make much sense to "pollute" IDE's screen with "Test 
 Results" button and list entry

 for applications that have nothing to do with QTestLib.



 It looks like there should be as little presence for this plugin as 
 possible in the IDE's GUI.

 Ideally, this plugin should show itself only if output of a program is in 
 QTestLib format.



 Thus this plugin really provides a different format of "Application 
 Output", not a different output pane.



 So proposed adjustment to this plugin is to be able to have several 
 formats of "Application Output".

 By default it's "raw" output, with the ability to switch to a different 
 format.

 In case of qtestlibplugin it can be "test results" and "benchmark results" 
 formats.

 Other plugins could have/add their own formats.



 What do you guys think?



 Alex





 -Original Message-
 From: qt-creator-boun...@trolltech.com 
 [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Eike Ziller
 Sent: Monday, October 26, 2009 4:00 AM
 To: qt-creator@trolltech.com
 Subject: Re: [Qt-creator] plugin_qtestlib





 On Oct 20, 2009, at 

Re: [Qt-creator] plugin_qtestlib

[Coda Highland]

Running the unit tests is conceptually part of building your
application. You don't have to clean and recompile your entire
application every time you make a little change; why is this any
different? Running the "Test" step doesn't have to recompile the whole
mess if it's already built (and, ideally, up to date).

/s/ Adam

On Mon, Oct 26, 2009 at 3:30 PM, Bravo.Alex  wrote:
> If running is part of building, then how do run the test several times (most 
> likely to step through it with debugger)? Do you also build several times?
>
> That's one of the reasons building is separate from running - you build once 
> and then run as many times as you want.
>
>
>
> -Original Message-
> From: qt-creator-boun...@trolltech.com 
> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Thomas Dähling
> Sent: Monday, October 26, 2009 1:21 PM
> To: qt-creator@trolltech.com
> Subject: Re: [Qt-creator] plugin_qtestlib
>
> I have always considered running the unit tests to be part of the build
> process; personally I always set unit tests up in a way that they are
> run once I compiled a project. Keeps the turnaround time as short as
> possible.
>
> So, with that background, I am fairly much in favour of using the "build
> issues" panel for these kind of things.
>
> jm2c
>
> /Thomas
>
> Bravo.Alex schrieb:
>> Adam,
>>
>>> Build Issues would be a valid output target
>>
>> What happens when the test itself has build issues - which is very common 
>> due to changes in the code being tested?
>> Are you saying that running of test can be considered part of building?
>>
>> Aren't building and running separate things according to Qt Creator design?
>>
>>
>> -Original Message-
>> From: qt-creator-boun...@trolltech.com 
>> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Coda Highland
>> Sent: Monday, October 26, 2009 12:39 PM
>> To: qt-creator@trolltech.com
>> Subject: Re: [Qt-creator] plugin_qtestlib
>>
>> Honestly I don't know if I want to set the precedent of allowing
>> plugins to just arbitrarily add new tabs there.
>>
>> I think Build Issues would be a valid output target, though; it's
>> already intended for jumping to the relevant places in the code and
>> one could argue that failing a unit test is a build issue.
>>
>> /s/ Adam
>>
>> On Mon, Oct 26, 2009 at 2:18 PM, Robert Caldecott
>>  wrote:
>>> I like the idea of a dedicated QTest output pane - will you be able to 
>>> double-click on failures to jump directly to the code?  That would be 
>>> brilliant.
>>>
>>> 2009/10/26 Bravo.Alex 
> Plus that it's not so high in the list of things to do.


 If you are talking about qtcrea...@nokia team, it makes a lot of sense.

 But that's why you guys opened development to outside world, right?

 So that we can help you improve already great product.





 So, back to qtestlibplugin:

 After bringing it back from the dead, I realized that the architecture of 
 this plugin might need adjustment:

 Right now it has its own type of output "Test Results" (just like "Build 
 Issues", "Application Output" and 2 more).

 But, as this picture shows, there's not much space for different types of 
 output:



 Besides it doesn't make much sense to "pollute" IDE's screen with "Test 
 Results" button and list entry

 for applications that have nothing to do with QTestLib.



 It looks like there should be as little presence for this plugin as 
 possible in the IDE's GUI.

 Ideally, this plugin should show itself only if output of a program is in 
 QTestLib format.



 Thus this plugin really provides a different format of "Application 
 Output", not a different output pane.



 So proposed adjustment to this plugin is to be able to have several 
 formats of "Application Output".

 By default it's "raw" output, with the ability to switch to a different 
 format.

 In case of qtestlibplugin it can be "test results" and "benchmark results" 
 formats.

 Other plugins could have/add their own formats.



 What do you guys think?



 Alex





 -Original Message-
 From: qt-creator-boun...@trolltech.com 
 [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Eike Ziller
 Sent: Monday, October 26, 2009 4:00 AM
 To: qt-creator@trolltech.com
 Subject: Re: [Qt-creator] plugin_qtestlib





 On Oct 20, 2009, at 7:24 PM, ext Bravo.Alex wrote:



> Why is it dead:
> a)      it's obsolete, we now have a new XYZ plugin supporting
> QTestLib in Qt Creator
> b)      the author is working on something else and doesn't have
> time/interest to work on it
> c)       it didn't do much, so it's not worth maintaining
> d)      nobody needs it, we are satisfied with running tests 

Re: [Qt-creator] plugin_qtestlib

[Bravo.Alex]

If running is part of building, then how do run the test several times (most 
likely to step through it with debugger)? Do you also build several times?

That's one of the reasons building is separate from running - you build once 
and then run as many times as you want.



-Original Message-
From: qt-creator-boun...@trolltech.com 
[mailto:qt-creator-boun...@trolltech.com] On Behalf Of Thomas Dähling
Sent: Monday, October 26, 2009 1:21 PM
To: qt-creator@trolltech.com
Subject: Re: [Qt-creator] plugin_qtestlib

I have always considered running the unit tests to be part of the build 
process; personally I always set unit tests up in a way that they are 
run once I compiled a project. Keeps the turnaround time as short as 
possible.

So, with that background, I am fairly much in favour of using the "build 
issues" panel for these kind of things.

jm2c

/Thomas

Bravo.Alex schrieb:
> Adam,
> 
>> Build Issues would be a valid output target
> 
> What happens when the test itself has build issues - which is very common due 
> to changes in the code being tested? 
> Are you saying that running of test can be considered part of building?
> 
> Aren't building and running separate things according to Qt Creator design?
> 
> 
> -Original Message-
> From: qt-creator-boun...@trolltech.com 
> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Coda Highland
> Sent: Monday, October 26, 2009 12:39 PM
> To: qt-creator@trolltech.com
> Subject: Re: [Qt-creator] plugin_qtestlib
> 
> Honestly I don't know if I want to set the precedent of allowing
> plugins to just arbitrarily add new tabs there.
> 
> I think Build Issues would be a valid output target, though; it's
> already intended for jumping to the relevant places in the code and
> one could argue that failing a unit test is a build issue.
> 
> /s/ Adam
> 
> On Mon, Oct 26, 2009 at 2:18 PM, Robert Caldecott
>  wrote:
>> I like the idea of a dedicated QTest output pane - will you be able to 
>> double-click on failures to jump directly to the code?  That would be 
>> brilliant.
>>
>> 2009/10/26 Bravo.Alex 
 Plus that it's not so high in the list of things to do.
>>>
>>>
>>> If you are talking about qtcrea...@nokia team, it makes a lot of sense.
>>>
>>> But that's why you guys opened development to outside world, right?
>>>
>>> So that we can help you improve already great product.
>>>
>>>
>>>
>>>
>>>
>>> So, back to qtestlibplugin:
>>>
>>> After bringing it back from the dead, I realized that the architecture of 
>>> this plugin might need adjustment:
>>>
>>> Right now it has its own type of output "Test Results" (just like "Build 
>>> Issues", "Application Output" and 2 more).
>>>
>>> But, as this picture shows, there's not much space for different types of 
>>> output:
>>>
>>>
>>>
>>> Besides it doesn't make much sense to "pollute" IDE's screen with "Test 
>>> Results" button and list entry
>>>
>>> for applications that have nothing to do with QTestLib.
>>>
>>>
>>>
>>> It looks like there should be as little presence for this plugin as 
>>> possible in the IDE's GUI.
>>>
>>> Ideally, this plugin should show itself only if output of a program is in 
>>> QTestLib format.
>>>
>>>
>>>
>>> Thus this plugin really provides a different format of "Application 
>>> Output", not a different output pane.
>>>
>>>
>>>
>>> So proposed adjustment to this plugin is to be able to have several formats 
>>> of "Application Output".
>>>
>>> By default it's "raw" output, with the ability to switch to a different 
>>> format.
>>>
>>> In case of qtestlibplugin it can be "test results" and "benchmark results" 
>>> formats.
>>>
>>> Other plugins could have/add their own formats.
>>>
>>>
>>>
>>> What do you guys think?
>>>
>>>
>>>
>>> Alex
>>>
>>>
>>>
>>>
>>>
>>> -Original Message-
>>> From: qt-creator-boun...@trolltech.com 
>>> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Eike Ziller
>>> Sent: Monday, October 26, 2009 4:00 AM
>>> To: qt-creator@trolltech.com
>>> Subject: Re: [Qt-creator] plugin_qtestlib
>>>
>>>
>>>
>>>
>>>
>>> On Oct 20, 2009, at 7:24 PM, ext Bravo.Alex wrote:
>>>
>>>
>>>
 Why is it dead:
 a)  it's obsolete, we now have a new XYZ plugin supporting
 QTestLib in Qt Creator
 b)  the author is working on something else and doesn't have
 time/interest to work on it
 c)   it didn't do much, so it's not worth maintaining
 d)  nobody needs it, we are satisfied with running tests through
 test.pl
>>>
>>>
>>> I suppose it's b) and c). Plus that it's not so high in the list of
>>>
>>> things to do.
>>>
>>> The only "maybe" still useful parts of the code in the plugin is
>>>
>>> probably the interaction/parsing of the QTestLib output.
>>>
>>>
>>>
>>> ++ Eike
>>>
>>>
>>>
   Alex
 On Tuesday 20 October 2009 17:47:42 ext Bravo.Alex wrote:
> I'm not very successful in finding any info about plugin_qtestlib.
> There's not many comments in the source code either.
> plugins.pro says this:
>>>

Re: [Qt-creator] Backtracking from a ctrl+click on method ?

[Brian McGillion]

Hi,

That exact functionality is in creator.

Alt + Left arrow (back)
Alt + right (forward)

and there is also the arrows (on the top of the edit pane)

Br,
Brian


> Hello,
>
> I searched the documentation and the web without finding any hint or
> solution to the following quest. I use the ctrl-click on methods a lot
> to peek at a method declaration or definition, but I couldn't find an
> easy way to get back to where I clicked on the method.
> Eclipse has this feature. Something like the back button of a web browser.
>
> --
> Ch. Meessen
> ___
> 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] Backtracking from a ctrl+click on method ?

[Kris Wong]

> Hello,
>
> I searched the documentation and the web without finding any hint or
> solution to the following quest. I use the ctrl-click on
> methods a lot
> to peek at a method declaration or definition, but I couldn't find an
> easy way to get back to where I clicked on the method.
> Eclipse has this feature. Something like the back button of a
> web browser.
>
> --
> Ch. Meessen
>

Alt + Left arrow key navigates backwards and Alt + Right arrow key navigates 
forwards. Also, Ctrl + tab switches back to the previous document.

-Kris Wong

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

Re: [Qt-creator] plugin_qtestlib

[Thomas Dähling]

I have always considered running the unit tests to be part of the build 
process; personally I always set unit tests up in a way that they are 
run once I compiled a project. Keeps the turnaround time as short as 
possible.

So, with that background, I am fairly much in favour of using the "build 
issues" panel for these kind of things.

jm2c

/Thomas

Bravo.Alex schrieb:
> Adam,
> 
>> Build Issues would be a valid output target
> 
> What happens when the test itself has build issues - which is very common due 
> to changes in the code being tested? 
> Are you saying that running of test can be considered part of building?
> 
> Aren't building and running separate things according to Qt Creator design?
> 
> 
> -Original Message-
> From: qt-creator-boun...@trolltech.com 
> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Coda Highland
> Sent: Monday, October 26, 2009 12:39 PM
> To: qt-creator@trolltech.com
> Subject: Re: [Qt-creator] plugin_qtestlib
> 
> Honestly I don't know if I want to set the precedent of allowing
> plugins to just arbitrarily add new tabs there.
> 
> I think Build Issues would be a valid output target, though; it's
> already intended for jumping to the relevant places in the code and
> one could argue that failing a unit test is a build issue.
> 
> /s/ Adam
> 
> On Mon, Oct 26, 2009 at 2:18 PM, Robert Caldecott
>  wrote:
>> I like the idea of a dedicated QTest output pane - will you be able to 
>> double-click on failures to jump directly to the code?  That would be 
>> brilliant.
>>
>> 2009/10/26 Bravo.Alex 
 Plus that it's not so high in the list of things to do.
>>>
>>>
>>> If you are talking about qtcrea...@nokia team, it makes a lot of sense.
>>>
>>> But that's why you guys opened development to outside world, right?
>>>
>>> So that we can help you improve already great product.
>>>
>>>
>>>
>>>
>>>
>>> So, back to qtestlibplugin:
>>>
>>> After bringing it back from the dead, I realized that the architecture of 
>>> this plugin might need adjustment:
>>>
>>> Right now it has its own type of output "Test Results" (just like "Build 
>>> Issues", "Application Output" and 2 more).
>>>
>>> But, as this picture shows, there's not much space for different types of 
>>> output:
>>>
>>>
>>>
>>> Besides it doesn't make much sense to "pollute" IDE's screen with "Test 
>>> Results" button and list entry
>>>
>>> for applications that have nothing to do with QTestLib.
>>>
>>>
>>>
>>> It looks like there should be as little presence for this plugin as 
>>> possible in the IDE's GUI.
>>>
>>> Ideally, this plugin should show itself only if output of a program is in 
>>> QTestLib format.
>>>
>>>
>>>
>>> Thus this plugin really provides a different format of "Application 
>>> Output", not a different output pane.
>>>
>>>
>>>
>>> So proposed adjustment to this plugin is to be able to have several formats 
>>> of "Application Output".
>>>
>>> By default it's "raw" output, with the ability to switch to a different 
>>> format.
>>>
>>> In case of qtestlibplugin it can be "test results" and "benchmark results" 
>>> formats.
>>>
>>> Other plugins could have/add their own formats.
>>>
>>>
>>>
>>> What do you guys think?
>>>
>>>
>>>
>>> Alex
>>>
>>>
>>>
>>>
>>>
>>> -Original Message-
>>> From: qt-creator-boun...@trolltech.com 
>>> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Eike Ziller
>>> Sent: Monday, October 26, 2009 4:00 AM
>>> To: qt-creator@trolltech.com
>>> Subject: Re: [Qt-creator] plugin_qtestlib
>>>
>>>
>>>
>>>
>>>
>>> On Oct 20, 2009, at 7:24 PM, ext Bravo.Alex wrote:
>>>
>>>
>>>
 Why is it dead:
 a)  it's obsolete, we now have a new XYZ plugin supporting
 QTestLib in Qt Creator
 b)  the author is working on something else and doesn't have
 time/interest to work on it
 c)   it didn't do much, so it's not worth maintaining
 d)  nobody needs it, we are satisfied with running tests through
 test.pl
>>>
>>>
>>> I suppose it's b) and c). Plus that it's not so high in the list of
>>>
>>> things to do.
>>>
>>> The only "maybe" still useful parts of the code in the plugin is
>>>
>>> probably the interaction/parsing of the QTestLib output.
>>>
>>>
>>>
>>> ++ Eike
>>>
>>>
>>>
   Alex
 On Tuesday 20 October 2009 17:47:42 ext Bravo.Alex wrote:
> I'm not very successful in finding any info about plugin_qtestlib.
> There's not many comments in the source code either.
> plugins.pro says this:
> plugin_qtestlib \ # this seems to be dead
> The source tree on gitorious.org is missing
 QTestLibPlugin.pluginspec for
>   it.
> Does anybody know what it was supposed to do?
 It's dead and the code probably is not very useful anymore either.
 daniel
 
>>>
>>>
>>> --
>>>
>>> Eike Ziller
>>>
>>> Software Engineer
>>>
>>> Nokia, Qt Development Frameworks
>>>
>>> Phone  +49 (0)30 6392 3255
>>>
>>> Fax+49 (0)30 6392 3256
>>>
>>> E-mail eike.zil...@nokia.com
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>

[Qt-creator] Backtracking from a ctrl+click on method ?

[Christophe Meessen]

Hello,

I searched the documentation and the web without finding any hint or 
solution to the following quest. I use the ctrl-click on methods a lot 
to peek at a method declaration or definition, but I couldn't find an 
easy way to get back to where I clicked on the method.

Eclipse has this feature. Something like the back button of a web browser.

--
Ch. Meessen


smime.p7s
Description: S/MIME Cryptographic Signature
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] plugin_qtestlib

[Coda Highland]

On Mon, Oct 26, 2009 at 2:50 PM, Bravo.Alex  wrote:
> Adam,
>
>> Build Issues would be a valid output target
>
> What happens when the test itself has build issues - which is very common due 
> to changes in the code being tested?
> Are you saying that running of test can be considered part of building?
>
> Aren't building and running separate things according to Qt Creator design?

Probably. I'm thinking from a user's perspective; I don't know how
much of an issue this is for Creator.

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

Re: [Qt-creator] plugin_qtestlib

[Bravo.Alex]

Adam,

> Build Issues would be a valid output target

What happens when the test itself has build issues - which is very common due 
to changes in the code being tested? 
Are you saying that running of test can be considered part of building?

Aren't building and running separate things according to Qt Creator design?


-Original Message-
From: qt-creator-boun...@trolltech.com 
[mailto:qt-creator-boun...@trolltech.com] On Behalf Of Coda Highland
Sent: Monday, October 26, 2009 12:39 PM
To: qt-creator@trolltech.com
Subject: Re: [Qt-creator] plugin_qtestlib

Honestly I don't know if I want to set the precedent of allowing
plugins to just arbitrarily add new tabs there.

I think Build Issues would be a valid output target, though; it's
already intended for jumping to the relevant places in the code and
one could argue that failing a unit test is a build issue.

/s/ Adam

On Mon, Oct 26, 2009 at 2:18 PM, Robert Caldecott
 wrote:
>
> I like the idea of a dedicated QTest output pane - will you be able to 
> double-click on failures to jump directly to the code?  That would be 
> brilliant.
>
> 2009/10/26 Bravo.Alex 
>>
>> > Plus that it's not so high in the list of things to do.
>>
>>
>>
>> If you are talking about qtcrea...@nokia team, it makes a lot of sense.
>>
>> But that's why you guys opened development to outside world, right?
>>
>> So that we can help you improve already great product.
>>
>>
>>
>>
>>
>> So, back to qtestlibplugin:
>>
>> After bringing it back from the dead, I realized that the architecture of 
>> this plugin might need adjustment:
>>
>> Right now it has its own type of output "Test Results" (just like "Build 
>> Issues", "Application Output" and 2 more).
>>
>> But, as this picture shows, there's not much space for different types of 
>> output:
>>
>>
>>
>> Besides it doesn't make much sense to "pollute" IDE's screen with "Test 
>> Results" button and list entry
>>
>> for applications that have nothing to do with QTestLib.
>>
>>
>>
>> It looks like there should be as little presence for this plugin as possible 
>> in the IDE's GUI.
>>
>> Ideally, this plugin should show itself only if output of a program is in 
>> QTestLib format.
>>
>>
>>
>> Thus this plugin really provides a different format of "Application Output", 
>> not a different output pane.
>>
>>
>>
>> So proposed adjustment to this plugin is to be able to have several formats 
>> of "Application Output".
>>
>> By default it's "raw" output, with the ability to switch to a different 
>> format.
>>
>> In case of qtestlibplugin it can be "test results" and "benchmark results" 
>> formats.
>>
>> Other plugins could have/add their own formats.
>>
>>
>>
>> What do you guys think?
>>
>>
>>
>> Alex
>>
>>
>>
>>
>>
>> -Original Message-
>> From: qt-creator-boun...@trolltech.com 
>> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Eike Ziller
>> Sent: Monday, October 26, 2009 4:00 AM
>> To: qt-creator@trolltech.com
>> Subject: Re: [Qt-creator] plugin_qtestlib
>>
>>
>>
>>
>>
>> On Oct 20, 2009, at 7:24 PM, ext Bravo.Alex wrote:
>>
>>
>>
>> > Why is it dead:
>>
>> > a)  it's obsolete, we now have a new XYZ plugin supporting
>>
>> > QTestLib in Qt Creator
>>
>> > b)  the author is working on something else and doesn't have
>>
>> > time/interest to work on it
>>
>> > c)   it didn't do much, so it's not worth maintaining
>>
>> > d)  nobody needs it, we are satisfied with running tests through
>>
>> > test.pl
>>
>>
>>
>> I suppose it's b) and c). Plus that it's not so high in the list of
>>
>> things to do.
>>
>> The only "maybe" still useful parts of the code in the plugin is
>>
>> probably the interaction/parsing of the QTestLib output.
>>
>>
>>
>> ++ Eike
>>
>>
>>
>> >  Alex
>>
>> >
>>
>> > On Tuesday 20 October 2009 17:47:42 ext Bravo.Alex wrote:
>>
>> > > I'm not very successful in finding any info about plugin_qtestlib.
>>
>> > > There's not many comments in the source code either.
>>
>> > >
>>
>> > > plugins.pro says this:
>>
>> > > plugin_qtestlib \ # this seems to be dead
>>
>> > >
>>
>> > > The source tree on gitorious.org is missing
>>
>> > QTestLibPlugin.pluginspec for
>>
>> > >  it.
>>
>> > >
>>
>> > > Does anybody know what it was supposed to do?
>>
>> > It's dead and the code probably is not very useful anymore either.
>>
>> >
>>
>> > daniel
>>
>> >
>>
>> > 
>>
>>
>>
>> --
>>
>> Eike Ziller
>>
>> Software Engineer
>>
>> Nokia, Qt Development Frameworks
>>
>> Phone  +49 (0)30 6392 3255
>>
>> Fax    +49 (0)30 6392 3256
>>
>> E-mail eike.zil...@nokia.com
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ___
>>
>> 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 ma

Re: [Qt-creator] parser bug(s)

[roberto.raggi]

Hi Onay,

On Oct 24, 2009, at 1:03 PM, ext Onay Urfalioglu wrote:

Hi,

1) There is a bug (in current snapshots too) with parsing code like the
following:

c.f()(x)(y)(z);

Oops, well it's parsed correctly but it looks like I forgot to handle this case 
in the type checker :) I will try to fix it before the 1.3 release.


Is C++0x support planned in the short term? I heard that Qt is also going to
use some C++0x elements for the next versions already.

Yeah, would be nice to have some support for c++0x in Creator. For sure it's 
too late for Creator 1.3 but I will see what I can do for our next major 
release.

Thanks for your report.

ciao robe

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

Re: [Qt-creator] plugin_qtestlib

[Coda Highland]

Honestly I don't know if I want to set the precedent of allowing
plugins to just arbitrarily add new tabs there.

I think Build Issues would be a valid output target, though; it's
already intended for jumping to the relevant places in the code and
one could argue that failing a unit test is a build issue.

/s/ Adam

On Mon, Oct 26, 2009 at 2:18 PM, Robert Caldecott
 wrote:
>
> I like the idea of a dedicated QTest output pane - will you be able to 
> double-click on failures to jump directly to the code?  That would be 
> brilliant.
>
> 2009/10/26 Bravo.Alex 
>>
>> > Plus that it's not so high in the list of things to do.
>>
>>
>>
>> If you are talking about qtcrea...@nokia team, it makes a lot of sense.
>>
>> But that's why you guys opened development to outside world, right?
>>
>> So that we can help you improve already great product.
>>
>>
>>
>>
>>
>> So, back to qtestlibplugin:
>>
>> After bringing it back from the dead, I realized that the architecture of 
>> this plugin might need adjustment:
>>
>> Right now it has its own type of output “Test Results” (just like “Build 
>> Issues”, “Application Output” and 2 more).
>>
>> But, as this picture shows, there’s not much space for different types of 
>> output:
>>
>>
>>
>> Besides it doesn’t make much sense to “pollute” IDE’s screen with “Test 
>> Results” button and list entry
>>
>> for applications that have nothing to do with QTestLib.
>>
>>
>>
>> It looks like there should be as little presence for this plugin as possible 
>> in the IDE’s GUI.
>>
>> Ideally, this plugin should show itself only if output of a program is in 
>> QTestLib format.
>>
>>
>>
>> Thus this plugin really provides a different format of “Application Output”, 
>> not a different output pane.
>>
>>
>>
>> So proposed adjustment to this plugin is to be able to have several formats 
>> of “Application Output”.
>>
>> By default it’s “raw” output, with the ability to switch to a different 
>> format.
>>
>> In case of qtestlibplugin it can be “test results” and “benchmark results” 
>> formats.
>>
>> Other plugins could have/add their own formats.
>>
>>
>>
>> What do you guys think?
>>
>>
>>
>> Alex
>>
>>
>>
>>
>>
>> -Original Message-
>> From: qt-creator-boun...@trolltech.com 
>> [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Eike Ziller
>> Sent: Monday, October 26, 2009 4:00 AM
>> To: qt-creator@trolltech.com
>> Subject: Re: [Qt-creator] plugin_qtestlib
>>
>>
>>
>>
>>
>> On Oct 20, 2009, at 7:24 PM, ext Bravo.Alex wrote:
>>
>>
>>
>> > Why is it dead:
>>
>> > a)  it’s obsolete, we now have a new XYZ plugin supporting
>>
>> > QTestLib in Qt Creator
>>
>> > b)  the author is working on something else and doesn’t have
>>
>> > time/interest to work on it
>>
>> > c)   it didn’t do much, so it’s not worth maintaining
>>
>> > d)  nobody needs it, we are satisfied with running tests through
>>
>> > test.pl
>>
>>
>>
>> I suppose it's b) and c). Plus that it's not so high in the list of
>>
>> things to do.
>>
>> The only "maybe" still useful parts of the code in the plugin is
>>
>> probably the interaction/parsing of the QTestLib output.
>>
>>
>>
>> ++ Eike
>>
>>
>>
>> >  Alex
>>
>> >
>>
>> > On Tuesday 20 October 2009 17:47:42 ext Bravo.Alex wrote:
>>
>> > > I'm not very successful in finding any info about plugin_qtestlib.
>>
>> > > There's not many comments in the source code either.
>>
>> > >
>>
>> > > plugins.pro says this:
>>
>> > > plugin_qtestlib \ # this seems to be dead
>>
>> > >
>>
>> > > The source tree on gitorious.org is missing
>>
>> > QTestLibPlugin.pluginspec for
>>
>> > >  it.
>>
>> > >
>>
>> > > Does anybody know what it was supposed to do?
>>
>> > It's dead and the code probably is not very useful anymore either.
>>
>> >
>>
>> > daniel
>>
>> >
>>
>> > 
>>
>>
>>
>> --
>>
>> Eike Ziller
>>
>> Software Engineer
>>
>> Nokia, Qt Development Frameworks
>>
>> Phone  +49 (0)30 6392 3255
>>
>> Fax    +49 (0)30 6392 3256
>>
>> E-mail eike.zil...@nokia.com
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ___
>>
>> 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 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] plugin_qtestlib - Entry 254483 in Task Tracker

[Bravo.Alex]

Clicking on failures is probably the main reason to integrate QTestLib with the 
IDE.

Filtering different types of test results and generating a stub implementation 
for a tested class would be other features of this plugin.

There's Entry 254483 in Task Tracker that mentions this feature. It doesn't 
have neither priority nor scheduling assigned though...



From: qt-creator-boun...@trolltech.com 
[mailto:qt-creator-boun...@trolltech.com] On Behalf Of Robert Caldecott
Sent: Monday, October 26, 2009 12:19 PM
To: qt-creator@trolltech.com
Subject: Re: [Qt-creator] plugin_qtestlib

I like the idea of a dedicated QTest output pane - will you be able to 
double-click on failures to jump directly to the code?  That would be brilliant.
2009/10/26 Bravo.Alex mailto:alex.br...@igt.com>>

> Plus that it's not so high in the list of things to do.



If you are talking about qtcrea...@nokia team, it makes a lot of sense.

But that's why you guys opened development to outside world, right?

So that we can help you improve already great product.





So, back to qtestlibplugin:

After bringing it back from the dead, I realized that the architecture of this 
plugin might need adjustment:

Right now it has its own type of output "Test Results" (just like "Build 
Issues", "Application Output" and 2 more).

But, as this picture shows, there's not much space for different types of 
output:

[cid:image001.jpg@01CA5638.3B794100]



Besides it doesn't make much sense to "pollute" IDE's screen with "Test 
Results" button and list entry

for applications that have nothing to do with QTestLib.



It looks like there should be as little presence for this plugin as possible in 
the IDE's GUI.

Ideally, this plugin should show itself only if output of a program is in 
QTestLib format.



Thus this plugin really provides a different format of "Application Output", 
not a different output pane.



So proposed adjustment to this plugin is to be able to have several formats of 
"Application Output".

By default it's "raw" output, with the ability to switch to a different format.

In case of qtestlibplugin it can be "test results" and "benchmark results" 
formats.

Other plugins could have/add their own formats.



What do you guys think?



Alex





-Original Message-
From: qt-creator-boun...@trolltech.com 
[mailto:qt-creator-boun...@trolltech.com]
 On Behalf Of Eike Ziller
Sent: Monday, October 26, 2009 4:00 AM
To: qt-creator@trolltech.com
Subject: Re: [Qt-creator] plugin_qtestlib





On Oct 20, 2009, at 7:24 PM, ext Bravo.Alex wrote:



> Why is it dead:

> a)  it's obsolete, we now have a new XYZ plugin supporting

> QTestLib in Qt Creator

> b)  the author is working on something else and doesn't have

> time/interest to work on it

> c)   it didn't do much, so it's not worth maintaining

> d)  nobody needs it, we are satisfied with running tests through

> test.pl



I suppose it's b) and c). Plus that it's not so high in the list of

things to do.

The only "maybe" still useful parts of the code in the plugin is

probably the interaction/parsing of the QTestLib output.



++ Eike



>  Alex

>

> On Tuesday 20 October 2009 17:47:42 ext Bravo.Alex wrote:

> > I'm not very successful in finding any info about plugin_qtestlib.

> > There's not many comments in the source code either.

> >

> > plugins.pro says this:

> > plugin_qtestlib \ # this seems to be dead

> >

> > The source tree on gitorious.org is missing

> QTestLibPlugin.pluginspec for

> >  it.

> >

> > Does anybody know what it was supposed to do?

> It's dead and the code probably is not very useful anymore either.

>

> daniel

>

> 



--

Eike Ziller

Software Engineer

Nokia, Qt Development Frameworks

Phone  +49 (0)30 6392 3255

Fax+49 (0)30 6392 3256

E-mail eike.zil...@nokia.com













___

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 mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] plugin_qtestlib

[Robert Caldecott]

I like the idea of a dedicated QTest output pane - will you be able to
double-click on failures to jump directly to the code?  That would be
brilliant.

2009/10/26 Bravo.Alex 

>  > Plus that it's not so high in the list of things to do.
>
>
>
> If you are talking about qtcrea...@nokia team, it makes a lot of sense.
>
> But that's why you guys opened development to outside world, right?
>
> So that we can help you improve already great product.
>
>
>
>
>
> So, back to qtestlibplugin:
>
> After bringing it back from the dead, I realized that the architecture of
> this plugin might need adjustment:
>
> Right now it has its own type of output “Test Results” (just like “Build
> Issues”, “Application Output” and 2 more).
>
> But, as this picture shows, there’s not much space for different types of
> output:
>
>
>
> Besides it doesn’t make much sense to “pollute” IDE’s screen with “Test
> Results” button and list entry
>
> for applications that have nothing to do with QTestLib.
>
>
>
> It looks like there should be as little presence for this plugin as
> possible in the IDE’s GUI.
>
> Ideally, this plugin should show itself only if output of a program is in
> QTestLib format.
>
>
>
> Thus this plugin really provides a different format of “Application
> Output”, not a different output pane.
>
>
>
> So proposed adjustment to this plugin is to be able to have several formats
> of “Application Output”.
>
> By default it’s “raw” output, with the ability to switch to a different
> format.
>
> In case of qtestlibplugin it can be “test results” and “benchmark results”
> formats.
>
> Other plugins could have/add their own formats.
>
>
>
> What do you guys think?
>
>
>
> Alex
>
>
>
>
>
> -Original Message-
> From: qt-creator-boun...@trolltech.com [mailto:
> qt-creator-boun...@trolltech.com] On Behalf Of Eike Ziller
> Sent: Monday, October 26, 2009 4:00 AM
> To: qt-creator@trolltech.com
> Subject: Re: [Qt-creator] plugin_qtestlib
>
>
>
>
>
> On Oct 20, 2009, at 7:24 PM, ext Bravo.Alex wrote:
>
>
>
> > Why is it dead:
>
> > a)  it’s obsolete, we now have a new XYZ plugin supporting
>
> > QTestLib in Qt Creator
>
> > b)  the author is working on something else and doesn’t have
>
> > time/interest to work on it
>
> > c)   it didn’t do much, so it’s not worth maintaining
>
> > d)  nobody needs it, we are satisfied with running tests through
>
> > test.pl
>
>
>
> I suppose it's b) and c). Plus that it's not so high in the list of
>
> things to do.
>
> The only "maybe" still useful parts of the code in the plugin is
>
> probably the interaction/parsing of the QTestLib output.
>
>
>
> ++ Eike
>
>
>
> >  Alex
>
> >
>
> > On Tuesday 20 October 2009 17:47:42 ext Bravo.Alex wrote:
>
> > > I'm not very successful in finding any info about plugin_qtestlib.
>
> > > There's not many comments in the source code either.
>
> > >
>
> > > plugins.pro says this:
>
> > > plugin_qtestlib \ # this seems to be dead
>
> > >
>
> > > The source tree on gitorious.org is missing
>
> > QTestLibPlugin.pluginspec for
>
> > >  it.
>
> > >
>
> > > Does anybody know what it was supposed to do?
>
> > It's dead and the code probably is not very useful anymore either.
>
> >
>
> > daniel
>
> >
>
> > 
>
>
>
> --
>
> Eike Ziller
>
> Software Engineer
>
> Nokia, Qt Development Frameworks
>
> Phone  +49 (0)30 6392 3255
>
> Fax+49 (0)30 6392 3256
>
> E-mail eike.zil...@nokia.com
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
>
> 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 mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] parser bug(s)

[Murphy, Sean M.]

>>> 1) There is a bug (in current snapshots too) with parsing code like
>>> the following:
>>> 
>>> c.f()(x)(y)(z);
>>> 
>>> But, this is legal c++.
>> 
>> Curious question of the day, what does the above line of code do?
>> I've never seen a C++ construct like that before!
> 
> c.f() returns a function pointer or a functor (either one works),
> which is invoked with the parameter x; this function returns another
> function pointer/functor, which is invoked with parameter y; this
> function returns another pointer/functor which is invoked with
parameter z.
> 
> Basically, imagine this class:
> class Functor {
> public:
> Functor operator()(int param);
> };

Thanks, I was slowly coming to that conclusion on my own, but since I
had never seen that convention of writing function pointers, I wasn't
really even sure what to Google on.  

The C++ class I took only briefly touched on function pointers, and it
never described a member function of a class returning a function
pointer, it only talked about passing a function pointer into a class
member function.  I think they specifically did it where the class had a
sort() function, and then we'd write different sorting algorithm
functions (insertion, bubble, heap, etc.) and pass those in to learn
about the speed of different sorting algorithms.

Sean

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

Re: [Qt-creator] parser bug(s)

[Coda Highland]

On Mon, Oct 26, 2009 at 1:26 PM, Murphy, Sean M.  wrote:
>> 1) There is a bug (in current snapshots too) with parsing code like
> the
>> following:
>>
>> c.f()(x)(y)(z);
>>
>> But, this is legal c++.
>
> Curious question of the day, what does the above line of code do?  I've
> never seen a C++ construct like that before!

c.f() returns a function pointer or a functor (either one works),
which is invoked with the parameter x; this function returns another
function pointer/functor, which is invoked with parameter y; this
function returns another pointer/functor which is invoked with
parameter z.

Basically, imagine this class:
class Functor {
public:
Functor operator()(int param);
};

/s/ Adam

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

Re: [Qt-creator] parser bug(s)

[Murphy, Sean M.]

> 1) There is a bug (in current snapshots too) with parsing code like
the
> following:
> 
> c.f()(x)(y)(z);
> 
> But, this is legal c++.

Curious question of the day, what does the above line of code do?  I've
never seen a C++ construct like that before!

Sean

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

Re: [Qt-creator] plugin_qtestlib

[Bravo.Alex]

> Plus that it's not so high in the list of things to do.



If you are talking about qtcrea...@nokia team, it makes a lot of sense.

But that's why you guys opened development to outside world, right?

So that we can help you improve already great product.





So, back to qtestlibplugin:

After bringing it back from the dead, I realized that the architecture of this 
plugin might need adjustment:

Right now it has its own type of output "Test Results" (just like "Build 
Issues", "Application Output" and 2 more).

But, as this picture shows, there's not much space for different types of 
output:

[cid:image002.jpg@01CA562A.6089A8D0]



Besides it doesn't make much sense to "pollute" IDE's screen with "Test 
Results" button and list entry

for applications that have nothing to do with QTestLib.



It looks like there should be as little presence for this plugin as possible in 
the IDE's GUI.

Ideally, this plugin should show itself only if output of a program is in 
QTestLib format.



Thus this plugin really provides a different format of "Application Output", 
not a different output pane.



So proposed adjustment to this plugin is to be able to have several formats of 
"Application Output".

By default it's "raw" output, with the ability to switch to a different format.

In case of qtestlibplugin it can be "test results" and "benchmark results" 
formats.

Other plugins could have/add their own formats.



What do you guys think?



Alex





-Original Message-
From: qt-creator-boun...@trolltech.com 
[mailto:qt-creator-boun...@trolltech.com] On Behalf Of Eike Ziller
Sent: Monday, October 26, 2009 4:00 AM
To: qt-creator@trolltech.com
Subject: Re: [Qt-creator] plugin_qtestlib





On Oct 20, 2009, at 7:24 PM, ext Bravo.Alex wrote:



> Why is it dead:

> a)  it's obsolete, we now have a new XYZ plugin supporting

> QTestLib in Qt Creator

> b)  the author is working on something else and doesn't have

> time/interest to work on it

> c)   it didn't do much, so it's not worth maintaining

> d)  nobody needs it, we are satisfied with running tests through

> test.pl



I suppose it's b) and c). Plus that it's not so high in the list of

things to do.

The only "maybe" still useful parts of the code in the plugin is

probably the interaction/parsing of the QTestLib output.



++ Eike



>  Alex

>

> On Tuesday 20 October 2009 17:47:42 ext Bravo.Alex wrote:

> > I'm not very successful in finding any info about plugin_qtestlib.

> > There's not many comments in the source code either.

> >

> > plugins.pro says this:

> > plugin_qtestlib \ # this seems to be dead

> >

> > The source tree on gitorious.org is missing

> QTestLibPlugin.pluginspec for

> >  it.

> >

> > Does anybody know what it was supposed to do?

> It's dead and the code probably is not very useful anymore either.

>

> daniel

>

> 



--

Eike Ziller

Software Engineer

Nokia, Qt Development Frameworks

Phone  +49 (0)30 6392 3255

Fax+49 (0)30 6392 3256

E-mail eike.zil...@nokia.com













___

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] Breakpoint Problem

[Daniel Teske]

On Monday 26 October 2009 18:31:09 ext Danny Price wrote:
> They tend to appear in spurts - I assume it's a manual process. There's not
>  been a mac version for some time now.

Actually it's automated. Though we had never a release where we didn't 
massively change the way we create packages on at least one platform. (And 
thus broke them for extended periods.)

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

Re: [Qt-creator] Breakpoint Problem

[Danny Price]

They tend to appear in spurts - I assume it's a manual process. There's not
been a mac version for some time now.

On Mon, Oct 26, 2009 at 5:22 PM, Stephen Chu  wrote:

> In article <20091026161823.ga1...@troll08.nokia.trolltech.de>,
>  Oswald Buddenhagen  wrote:
>
> > On Mon, Oct 26, 2009 at 04:09:26PM +, Robert Caldecott wrote:
> > > Eh?  That's the latest Windows version of Qt Creator I can find on
> > > your FTP snapshot server.
> > >
> > well, that means that our nightly build system is kinda lagging. from
> > the developers' pov it is still *wy* outdated when it comes to "hot"
> > code. and you'll find that it is smoking hot if you check the git log. :)
>
> Is there ever a Mac version of snapshot? I don't see one anywhere on the
> FTP site other than the beta.
>
> --
> Stephen Chu
> ___
> 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] Breakpoint Problem

[Stephen Chu]

In article <20091026161823.ga1...@troll08.nokia.trolltech.de>,
 Oswald Buddenhagen  wrote:

> On Mon, Oct 26, 2009 at 04:09:26PM +, Robert Caldecott wrote:
> > Eh?  That's the latest Windows version of Qt Creator I can find on
> > your FTP snapshot server.
> > 
> well, that means that our nightly build system is kinda lagging. from
> the developers' pov it is still *wy* outdated when it comes to "hot"
> code. and you'll find that it is smoking hot if you check the git log. :)

Is there ever a Mac version of snapshot? I don't see one anywhere on the 
FTP site other than the beta.

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

Re: [Qt-creator] Breakpoint Problem

[Robert Caldecott]

I'll look for an update first thing in the morning...

2009/10/26 Oswald Buddenhagen :
> On Mon, Oct 26, 2009 at 04:09:26PM +, Robert Caldecott wrote:
>> Eh?  That's the latest Windows version of Qt Creator I can find on
>> your FTP snapshot server.
>>
> well, that means that our nightly build system is kinda lagging. from
> the developers' pov it is still *wy* outdated when it comes to "hot"
> code. and you'll find that it is smoking hot if you check the git log. :)
> ___
> 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] Breakpoint Problem

[Oswald Buddenhagen]

On Mon, Oct 26, 2009 at 04:09:26PM +, Robert Caldecott wrote:
> Eh?  That's the latest Windows version of Qt Creator I can find on
> your FTP snapshot server.
> 
well, that means that our nightly build system is kinda lagging. from
the developers' pov it is still *wy* outdated when it comes to "hot"
code. and you'll find that it is smoking hot if you check the git log. :)
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Breakpoint Problem

[Daniel Molkentin]

Oha, good point. There will be new ones up in a few hours (unless 
compilation breaks :).

ext Robert Caldecott schrieb:
> Eh?  That's the latest Windows version of Qt Creator I can find on
> your FTP snapshot server.
> 
> 2009/10/26 Oswald Buddenhagen :
>> On Mon, Oct 26, 2009 at 03:46:21PM +, Robert Caldecott wrote:
>>> OK, re-creating this is easy for me.  I am running Qt Creator 1.2.93
>>> rev 97e7b7bbf9 (Oct 21).
>>>
>> that's stone age. please try something *current*.

-- 
Daniel Molkentin, Software Engineer,
Nokia, Qt Development Frameworks
website: http://qt.nokia.com
Rudower Chaussee 13, DE-12489 Berlin

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] Breakpoint Problem

[Robert Caldecott]

Eh?  That's the latest Windows version of Qt Creator I can find on
your FTP snapshot server.

2009/10/26 Oswald Buddenhagen :
> On Mon, Oct 26, 2009 at 03:46:21PM +, Robert Caldecott wrote:
>> OK, re-creating this is easy for me.  I am running Qt Creator 1.2.93
>> rev 97e7b7bbf9 (Oct 21).
>>
> that's stone age. please try something *current*.
>
> ___
> 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] Breakpoint Problem

[Oswald Buddenhagen]

On Mon, Oct 26, 2009 at 03:46:21PM +, Robert Caldecott wrote:
> OK, re-creating this is easy for me.  I am running Qt Creator 1.2.93
> rev 97e7b7bbf9 (Oct 21).
> 
that's stone age. please try something *current*.

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

Re: [Qt-creator] Breakpoint Problem

[Robert Caldecott]

OK, re-creating this is easy for me.  I am running Qt Creator 1.2.93
rev 97e7b7bbf9 (Oct 21).

1. Start Qt Creator.
2. Create a new Qt4 GUI project (MainWindow based).
3. Open main.cpp and use F9 to add a breakpoint on line 8.
4. Hit F5.  Program builds, gdb starts and the breakpoint is triggered.
5. Hit F5 to continue and then close the application.
6. Toggle the breakpoint on line 8 off (using F9) and add a new one to line 9.
7. Hit F5.  Breakpoint isn't triggered and the application runs,
displaying the main window.

Attached is the gdb log.  I hope this helps.

If I hit F5 again, then the new breakpoint on line 9 is triggered OK.
While gdb is loaded I can toggle breakpoints at will.

2009/10/26 André Pönitz :
> On Monday 26 October 2009 14:33:36 ext Robert Caldecott wrote:
>> Out of interest, have you managed to reproduce my breakpoint issues?
>
> I was not able to reproduce it after the first change I mentioned
> last week.
>
>> (where breakpoints cannot always be set unless gdb is actually
>> running.)  This issue got a little better with the latest nightly
>> Windows build but is still giving me problems.
>
> Could you re-create the log? Maybe the problem more visible
> now that "something" changed...


gdb.log
Description: Binary data
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Breakpoint Problem

[André Pönitz]

On Monday 26 October 2009 14:33:36 ext Robert Caldecott wrote:
> Out of interest, have you managed to reproduce my breakpoint issues?

I was not able to reproduce it after the first change I mentioned 
last week. 

> (where breakpoints cannot always be set unless gdb is actually
> running.)  This issue got a little better with the latest nightly
> Windows build but is still giving me problems.

Could you re-create the log? Maybe the problem more visible
now that "something" changed...

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

Re: [Qt-creator] Breakpoint Problem

[Robert Caldecott]

Out of interest, have you managed to reproduce my breakpoint issues?
(where breakpoints cannot always be set unless gdb is actually
running.)  This issue got a little better with the latest nightly
Windows build but is still giving me problems.

2009/10/26 André Pönitz :
> On Monday 26 October 2009 13:18:20 Poenitz Andre (Nokia-D-Qt/Berlin) wrote:
>> On Monday 26 October 2009 12:29:21 ext GenaCid wrote:
>> > On Monday 26 October 2009 11:34:11 André Pönitz wrote:
>> > > ...
>> > > I just tried to reproduce it but failed. Can you please post a recipe
>> > > to reproduce the problem?
>> > >
>> > > Andre'

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

Re: [Qt-creator] parser bug(s)

[Danny Price]

This isn't down to Creator.

This all depends on the toolchain that Creator has been setup to use - GCC,
MinGW or MSVC's compiler (nmake?).

Check that the toolchain you are using supports C++0x.


On Sat, Oct 24, 2009 at 11:03 AM, Onay Urfalioglu  wrote:

> Hi,
>
> 1) There is a bug (in current snapshots too) with parsing code like the
> following:
>
> c.f()(x)(y)(z);
>
> But, this is legal c++.
>
> 2) C++0x patterns like y = {1,2};  (using initializer lists) are also
> parsed
> as syntax errors.
>
> Is C++0x support planned in the short term? I heard that Qt is also going
> to
> use some C++0x elements for the next versions already.
>
> Greets,
> oni
> ___
> 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] Breakpoint Problem

[GenaCid]

On Monday 26 October 2009 15:18:20 André Pönitz wrote:
> Refering to Message-ID: <200910261429.21544.gena...@inbox.ru>:
> There is something strange in the log: Your project does not seem
> to be linked to libdl, so the dumpers can not be loaded using dlopen.
> Could you please try to disable custom dumper usage (there's an option
> in the debugger settings and in the context menu of the locals view)
> and re-create the log ?
> 
> If that solves the problem we might have a regression in handling
> unexpected dumper failures
> 
> Andre'

Seems, you were write: disabling debugger helper helped me! Breakpoints works 
again.

-|-
Гена.

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

[Qt-creator] parser bug(s)

[Onay Urfalioglu]

Hi,

1) There is a bug (in current snapshots too) with parsing code like the 
following:

c.f()(x)(y)(z);

But, this is legal c++.

2) C++0x patterns like y = {1,2};  (using initializer lists) are also parsed 
as syntax errors.

Is C++0x support planned in the short term? I heard that Qt is also going to 
use some C++0x elements for the next versions already.

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

Re: [Qt-creator] Breakpoint Problem

[André Pönitz]

On Monday 26 October 2009 13:18:20 Poenitz Andre (Nokia-D-Qt/Berlin) wrote:
> On Monday 26 October 2009 12:29:21 ext GenaCid wrote:
> > On Monday 26 October 2009 11:34:11 André Pönitz wrote:
> > > ...
> > > I just tried to reproduce it but failed. Can you please post a recipe
> > > to reproduce the problem?
> > > 
> > > Andre'
> > 
> > Emmm... There were no special actions. Just rebuilt, set breakpoint and 
> > started 
> > the debugger. I've just tried today's snapshot (f1d5b3c70b) and debugger is 
> > still crash =(
> 
> Refering to Message-ID: <200910261429.21544.gena...@inbox.ru>:
> There is something strange in the log: Your project does not seem 
> to be linked to libdl, so the dumpers can not be loaded using dlopen.
> Could you please try to disable custom dumper usage (there's an option
> in the debugger settings and in the context menu of the locals view)
> and re-create the log ?
> 
> If that solves the problem we might have a regression in handling 
> unexpected dumper failures

I just tried myself with a static application, and it "works as expected"
(i.e. breakpoint hit, but no dumpers)

Andre'

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

[Qt-creator] Feature Request: separate keys to (un)comment

[Mar]

Hi,

I can see that it is a smart option to have one shortcut for 
comment/uncomment. But I would prefare the option to set two different 
shortcuts, one for comment and one for uncomment. E.g. when I wand to 
uncomment a block, then I have to mark the exact block, if I mark a line 
too much (e.g. a line in the midle whitch is not comment out) then a 
separate key for uncomment would be much bether.

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

Re: [Qt-creator] Breakpoint Problem

[André Pönitz]

On Monday 26 October 2009 12:29:21 ext GenaCid wrote:
> On Monday 26 October 2009 11:34:11 André Pönitz wrote:
> > ...
> > I just tried to reproduce it but failed. Can you please post a recipe
> > to reproduce the problem?
> > 
> > Andre'
> 
> Emmm... There were no special actions. Just rebuilt, set breakpoint and 
> started 
> the debugger. I've just tried today's snapshot (f1d5b3c70b) and debugger is 
> still crash =(

Refering to Message-ID: <200910261429.21544.gena...@inbox.ru>:
There is something strange in the log: Your project does not seem 
to be linked to libdl, so the dumpers can not be loaded using dlopen.
Could you please try to disable custom dumper usage (there's an option
in the debugger settings and in the context menu of the locals view)
and re-create the log ?

If that solves the problem we might have a regression in handling 
unexpected dumper failures

Andre'

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

Re: [Qt-creator] Breakpoint Problem

[GenaCid]

On Monday 26 October 2009 11:34:11 André Pönitz wrote:
> ...
> I just tried to reproduce it but failed. Can you please post a recipe
> to reproduce the problem?
> 
> Andre'

Emmm... There were no special actions. Just rebuilt, set breakpoint and started 
the debugger. I've just tried today's snapshot (f1d5b3c70b) and debugger is 
still crash =(

-|-
Гена.

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

Re: [Qt-creator] Basic Syntax Highlights

[Thorbjørn Lindeijer]

ext Damien Fagnou wrote:
> Hi ,
> 
> we use a lot of Lua in our company , we have some syntax highlight 
> definitions that include lua keywork and some of our own extension. and 
> the editor we current use for that is using the highlight definition to 
> do the auto complete [just dictionary style ]
> 
> I want to move people coding in Lua to qtCreator along with the C++ 
> developers but what is involve in adding an highlights based on keywords 
> and autocompletion of those to a a language ( ex lua ) ?
> 
> how big of a project is it to add a very basic language support like that ?

Most of the work should be in implementing a QSyntaxHighlighter for Lua.

The other tricky thing is that there is no easy way to add syntax 
highlighting for a new language to Qt Creator at the moment. You will 
have to create a new plugin (say LuaPlugin), which adds a new derivative 
of the BaseTextEditor (say LuaEditor), with appropriate factory, editor 
action registration (TextEditorActionHandler), define and register the 
MIME type, etc.

I guess we could add a Highlight plugin, through which we could make it 
easier to add basic highlighting support for more languages, but at the 
moment this has no priority from our side.

Once you have your LuaPlugin, implementing custom indentation logic, 
code completion and navigation for Lua also becomes possible of course.

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] plugin_qtestlib

[Eike Ziller]

On Oct 20, 2009, at 7:24 PM, ext Bravo.Alex wrote:

> Why is it dead:
> a)  it’s obsolete, we now have a new XYZ plugin supporting  
> QTestLib in Qt Creator
> b)  the author is working on something else and doesn’t have  
> time/interest to work on it
> c)   it didn’t do much, so it’s not worth maintaining
> d)  nobody needs it, we are satisfied with running tests through  
> test.pl

I suppose it's b) and c). Plus that it's not so high in the list of  
things to do.
The only "maybe" still useful parts of the code in the plugin is  
probably the interaction/parsing of the QTestLib output.

++ Eike

>  Alex
>
> On Tuesday 20 October 2009 17:47:42 ext Bravo.Alex wrote:
> > I'm not very successful in finding any info about plugin_qtestlib.
> > There's not many comments in the source code either.
> >
> > plugins.pro says this:
> > plugin_qtestlib \ # this seems to be dead
> >
> > The source tree on gitorious.org is missing  
> QTestLibPlugin.pluginspec for
> >  it.
> >
> > Does anybody know what it was supposed to do?
> It's dead and the code probably is not very useful anymore either.
>
> daniel
>
> 

-- 
Eike Ziller
Software Engineer
Nokia, Qt Development Frameworks
Phone  +49 (0)30 6392 3255
Fax+49 (0)30 6392 3256
E-mail eike.zil...@nokia.com






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

Re: [Qt-creator] Breakpoint Problem

[André Pönitz]

On Friday 23 October 2009 21:03:36 ext Gena wrote:
> On Tuesday 20 October 2009 19:12:34 André Pönitz wrote:
> > There have been some changes in the area today, and by now I
> > can't reproduce the issue anymore. Could you please check
> > (after the 12 hour synchronization delay) whether it works for you?
> 
> Just tried latest snapshot (03e3a92806): smth changed, but still hasn't 
> worked 
> =(

> With my little project debugger works fine, but for big project things are 
> getting worse... Now debugger works only for first setted breakpoint and if I 
> change breakpoint, always get message "The gdb process exited unexpectedly 
> (crashed)." Even after restart qt-creator. Even after rebuild application. 

If gdb crashes there's really not much Creator can do, except perhaps
using a way to ask gdb for information that does not cause gdb to crash.

I just tried to reproduce it but failed. Can you please post a recipe
to reproduce the problem? 

Andre'

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