[Qt-creator] my cheers, and two cents

Nathan Carter nathancarter5 at gmail.com
Tue Nov 4 15:57:36 CET 2008


>>
>> 1. What's a task list?  I can get to it with the button next to
>> QuickOpen, but I can't add a task, and can't find documentation on
>> this.  Is it searching my source files for some secret incantation
>> like "TO DO"?
>
> I guess this is a concept that came from Visual Studio (not sure  
> though). You're not the only one confused by the terminology here.  
> I'm not sure if we should extend its functionality, or just rename  
> it. I do think automatically searching for all TODO entries in  
> source code would be a nice feature, though it's easy enough to just  
> press Ctrl+Shift+F and do it yourself. :-)

Two responses:

1. I still don't know what the task list does, nor how to use it.   
Someone else said compiler warnings showed up here.  Is that it's  
purpose?  Compilation warnings (and errors) are "tasks"?

2. No, the search is quite different from having the search results  
already there (as clickable links).  Do you really want to jump  
through all the files with tasks to see the elements of your to-do  
list one at a time!?

But actually, a task list that is comprised of two types of tasks  
would be great:  Type 1 == those found through a TO-DO search and type  
2 == those manually added.  But perhaps I'm going beyond the spirit of  
Qt Creator here by suggesting adding inessentials.  Maybe this is  
where a plugin comes in.

>> 4. Can we get continued video tutorials as features are added?  I
>> found the intro tutorials a perfect high-level intro, from which I
>> began experimenting on my own and reading help on an as-needed basis.
>> It would be great if as new chunks of features are added (code
>> refactoring tools, etc.) that we see an overview of them in new video
>> tutorials.  This really gives the learning curve a smackdown, IMO.
>
> For sure we'll have some more videos later. :-)

Excellent!

>> 6. Bug: I checked the preference box for showing a word wrap marker  
>> at
>> column 80, but it doesn't seem to show up, instead just slightly
>> graying everything from column 0 to the right.
>
> Hmm, can't reproduce. Maybe a problem with your font? Can you try  
> selecting another one? Sounds like it might be having problems  
> determining how wide 80 characters are.

I've tried it with Courier New and Monaco, both fixed width fonts, the  
latter of which is the default, I believe.  It doesn't seem to  
matter.  Here's a screenshot:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Picture 1.png
Type: image/png
Size: 96706 bytes
Desc: not available
Url : http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20081104/f2fa51ec/attachment.png 
-------------- next part --------------



While I'm on it, two related suggestions:

1. The preferences dialog should stay on the page you were on when you  
last clicked OK.  Otherwise, you end up doing a lot of clicking the  
expanders to get back to where you were as you try to get a preference  
just right.

2. The preferences dialog has some painting issues when the combo box  
drop-down is large, as in the following screenshot for font  
selection.  This comes about by navigating the drop-down box with the  
down arrow key.  (It makes it look as if you're multi-selecting when  
you're not.)  (Leopard on a MacBook Pro)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Picture 2.png
Type: image/png
Size: 173618 bytes
Desc: not available
Url : http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20081104/f2fa51ec/attachment-0001.png 
-------------- next part --------------



>> 9. Support for Doxygen comments would be excellent, or at the very
>> least the trivial feature of preserving the initial * on a line  
>> when I
>> press enter.  That is, if I'm at the point
>>       /** foo bar baz bash
>>        *  hubbly bubbly [and I press enter here]
>> then give me a line like
>>         *  [cursor here]
>> as the next line.  Eventually, it would be great if Doxygen-generated
>> documentation took on the same status in QtCreator's help as the  
>> built-
>> in Qt help does.  I.e., I can push a button to call Doxygen on my
>> Doxyfile, and rebuild the help which then gets re-indexed, and F1-ing
>> a class I've defined opens that generated page in the help window.
>
> I'm very much with you here. The Doxygen integration might make for  
> a nice plugin. :-)

Hehe.  Whoever writes the plugin, let me ask that word wrapping be  
implemented so that it treats the initial [witespace]*[whitespace] as  
immovable, and thus enables me to type, cut, copy, paste, etc., while  
it handles keeping everything nicely word-wrapped after a left column  
of stuff like this.
	/**
	 *
	 *
	 *
	 */

Nathan


More information about the Qt-creator-old mailing list