Changing the @ tag controls in V53

Posted July 4, 2008 by Glen McKeown

There appears to be a real problem with changing the @tags. It is not possible to actually amend the @tags when they are place. Not only is this impossible, but the effect, which is slightly erratic, is to amend the actual Note itself. I then started to totally delete the @tag if I wanted to change the tag, but now I am finding that even this is causing the note to be changed - here is an example below

- Ray Wagner: Housing Associa@May08May08.

When the new @tag was inserted there was a gap between the word Association (which was complete) and the @sign, yet the tag has managed to travel backwards.

jesse - July 4, 2008 8:02 AM

Is anyone else noticing problems with this? I'm playing around with editing tags in 53 now and can't seem to reproduce any of the problems reported. It may be that I'm just not dong the right steps... if you could give a key by key explanation of what is happening, and what you expect to be happening that might help me. Thanks.

Matthew Crider - July 4, 2008 10:25 AM

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.

Here's a couple of examples of how I would use that feature:

  1. A ToDo tagged @soon. Then, through progress of doing other items, I now want it to be tagged @now.
  2. A ToDo tagged @contingent. Then, the item upon which this ToDo is contingent is done, so I want to mark this @now.

In v51, I would double-click "soon" or "contingent" and type "n" and it would autocomplete to "@now." This was very efficient.

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.

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?

Perhaps, change to a command-click on the tag to open up a search and leave all other clicking as normal.

Matt

Glen McKeown - July 5, 2008 12:24 AM

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.

Topic's comments