Hog Bay Software's comments http://hogbaysoftware.com/forums en-us 60 You are quite right, and it... http://hogbaysoftware.com/forums/taskpaper/topics/855_Print_Out_2/comments/3480 <p>You are quite right, and it does make good sense as now presented. But why 2007?</p> Sat, 05 Jul 2008 00:35:08 -0500 Glen McKeown The problem is not consiste... http://hogbaysoftware.com/forums/taskpaper/topics/856_Changing_the_tag_controls_in_V53/comments/3479 <p>The problem is not consistent in that it does not occur automatically when certain actions are done. When it does occur the only way to get around it is to delete all tags and start again. Even then it can help to use the search facility to only have that entry on view. Initially the problem occurred when I backspaced on an @tag in order to change it. So I then changed to deleting the @tag completely and running the new one. But even that can create the problem. I believe another factor is that it occurs when there are two or more @tags on the same note. It is also more prone to occur when there is more than one tab, and when the arrange by tag is operating. Hope this helps.</p> Sat, 05 Jul 2008 00:24:20 -0500 Glen McKeown Jesse, Any more thoughts... http://hogbaysoftware.com/forums/taskpaper/topics/834_A_Perfectly_Legitimate_Reason_Collapsing_is_Needed_in_Task_Management/comments/3478 <p>Jesse,</p> <p>Any more thoughts on this.</p> <p>Matt</p> Fri, 04 Jul 2008 10:26:49 -0500 Matthew Crider Well, what I don't like abo... http://hogbaysoftware.com/forums/taskpaper/topics/856_Changing_the_tag_controls_in_V53/comments/3477 <p>Well, what I don't like about the new tags is that they are hard to change. In v51 I could double-click the word, the @ would remain unhighlighted, I could then begin typing and TaskPaper would autocomplete. </p> <p>Here's a couple of examples of how I would use that feature:</p> <ol> <li>A ToDo tagged @soon. Then, through progress of doing other items, I now want it to be tagged @now.</li> <li>A ToDo tagged @contingent. Then, the item upon which this ToDo is contingent is done, so I want to mark this @now.</li> </ol> <p>In v51, I would double-click "soon" or "contingent" and type "n" and it would autocomplete to "@now." This was very efficient.</p> <p>Now, a single-click opens a search on that tag. So, now I have to carefully place the cursor between the @ and the word and then highlight the tag. Several times I have accidentally opened the search because I didn't get it inbetween.</p> <p>Now, don't get me wrong. I like the ability to pop open a search based on the tag, but don't I already have that capability down at the bottom of the page?</p> <p>Perhaps, change to a command-click on the tag to open up a search and leave all other clicking as normal.</p> <p>Matt</p> Fri, 04 Jul 2008 10:25:08 -0500 Matthew Crider Thanks. http://hogbaysoftware.com/forums/taskpaper/topics/851_Clicking_is_inconsistent_in_v53/comments/3476 <p>Thanks.</p> Fri, 04 Jul 2008 10:12:43 -0500 Matthew Crider Jesse, If it is an issue... http://hogbaysoftware.com/forums/taskpaper/topics/849_Strike_through_in_v53_for_done/comments/3475 <p>Jesse,</p> <p>If it is an issue that causes problems, then I understand. But, if not, then I prefer it not to strike out the tags. This is just my opinion and preference. Tags now have two lines in that case: the underline and the strikethrough. I find it distracting.</p> <p>So, put me down with a vote for returning the strikethrough to the way it was, if at all possible.</p> <p>Thanks.</p> <p>Matt</p> Fri, 04 Jul 2008 10:08:24 -0500 Matthew Crider No it didn't. I cleaned up ... http://hogbaysoftware.com/forums/taskpaper/topics/849_Strike_through_in_v53_for_done/comments/3474 <p>No it didn't. I cleaned up a lot of the styling code for version 53, and that was one special case that I removed. Generally it seems like styles should apply to the whole line, it was creating some odd cases when I only applied styles to the first name part ofthe line, but not to tags.</p> Fri, 04 Jul 2008 08:34:19 -0500 jesse I'm not sure exactly what y... http://hogbaysoftware.com/forums/taskpaper/topics/853_Refinements/comments/3473 <p>I'm not sure exactly what you mean. TaskPaper is based on a plain text file format, so you'll never be able to select some text and mark it as bold, italic, change the font, etc, since there is no place in the file format to store that information. And I wouldn't want to change to another file format, TaskPaper's plain text format is one of it's biggest selling points.</p> <p>But when Taskpaper displays one of these files it can add temporary styling that makes the document easier to read. For example, I'm sure you've noticed that projects in taskpaper render in a bigger bolder font. In the next version of TaskPaper (2.0, you can download dvelopment version of it from these forums now) you'll have much more flexibility on defining styles that get applied to you document when it is opened in TaskPaper.</p> <p>I hope that helps.</p> Fri, 04 Jul 2008 08:29:24 -0500 jesse Voodoopad style auto recogn... http://hogbaysoftware.com/forums/taskpaper/topics/848_Dev_53_file_links_not_working/comments/3472 <p>Voodoopad style auto recognition of names is probably a way off. But right now TaskPaper will actually recognize the address book link that you posted. I'm not sure how to get that link from address book yet at the moment... but if you could figure that out then you could have a workable, if a little ugly system.</p> Fri, 04 Jul 2008 08:25:18 -0500 jesse The nice thing about changi... http://hogbaysoftware.com/forums/taskpaper/topics/847_TaskPaper_2_Development_53/comments/3471 <p>The nice thing about changing to a query language is it will be fairly easy to implement these sorts of options. Nothing done yet though.</p> Fri, 04 Jul 2008 08:19:16 -0500 jesse