ThinkingRock Forum

As a former Kinkless user, I very much enjoy the way TR handles things. But using OmniOutliner/Kinkless has spoiled me in terms of certain UI niceties. For example...

1. When adding an action to a project using CTRL-a (Projects screen) I expect to be able to begin typing the description immediately. Instead I have to either use the mouse to select the Description field or hit Tab 4 times. It seems that dropping the cursor and into the Description field immediately would be useful, since I'd wager that's the right move 90% of the time.

2. Dragging items in the project tree. I'd prefer it if the drop target was somehow highlighted when dragging projects/actions. Currently, there's no visual cue where a dragged item is going to "land"

3. The expansion triangle sometimes needs a second click. The first click "darkens" it but doesn't toggle. The second click toggles.

4. And of course maintaining state of the tree would be great.

Oh, and I'm obviously using TR on OS X (Tiger). Thanks for a great tool.

Jack

I agree with items 2, 3 & 4 (#1 is not an issue for me personally). I also would like to add a couple more project-related issues:

5. Project cut/copy/paste works for me using the shortcuts, but the picks from the pulldown menu are greyed out.

6. The convert project to action button is also greyed out - can't get it to work.

Thanks! TR 1.2.3 is working great for me - these are just minor issues! I am still marveling at how much simpler and intuitive TR is over kGTD!

>> 6. The convert project to action button is also greyed out - can't get it to work.

I have the same problem.

Bill

Item 6:
The convert action to project was not included into v1.2.3 because I suggested some specs on
http://www.thinkingrock.com.au/forum/viewtopic.php?t=125
and nobody replied so we thought it was not that urgent.

Sorry about the confusion. Please let us know if these specs are correct and we will implement them in the next version.

Item 1: you can also use CTRL+TAB after CTRL+A and that will get you to the action (or project) description.

I will investigate the other points.

_________________
Claire
ThinkingRock Analyst and Tester

I don't think it's that urgent. I was just commenting because the button was present but greyed out.

My response to your specs is first, that the button should be active only if there are NO actions. Let the user decide what to do with any actions that might be there before allowing the project to be converted to an action.

However, if you decide to allow the button to be active with one action, then I would support keeping the action description rather than the project description because that should be more specific.

Thanks! I can't say enough how much TR has improved by effectiveness of GTD!

Oops! I meant to say MY effectiveness of using GTD! Should have used the Preview button!