»
TP 51 feature incomplete / feature requests and bugs
Posted June 19, 2008 by Nick Brawne
Over the last few weeks I have come up with all sort of small features that I would like to request, but have not, as I know that TP 51 is feature incomplete. The problem is that witjout a list it is impossible to know what is incomplete, and what should be a feature request, or listed as a bug.
I understand that Jesse does not want to give a long list of all the features that TP 2.0 will have, but would it be possible to at least let us know what features you intend to add to themes ?
Below is a partial list of my bugs / feature requests:
- inconsistant application of rules with dark themes > some task '-' are theme color, some black
- inconsistant application of rules with dark themes > project names sometimes not theme color. Clicking save and apply theme in preferences sometimes toggles colors.
- toggling the done status of a tasks will force a non applied theme rule to be applied.
- project list (left side widow) not effected by rules text is always black
- project click arrow not themable always black (invisable with dark themes)
- default theme names are consistant with names used in rules
- TP does not recognize third party color pickers (PaintersPicker http://www.old-jewel.com/ppicker/index.html)
- applying a tag to a note turns it into a task (without the '-')
- search is case sensative. inBox and InBox are not the same. perhaps this could be a preference or option in search.
- persistant searches > open a new document and an old search term is already on a new and empty tab

reply |
edit
jesse - June 23, 2008 1:19 PM
Sorry for not responding sooner. This sort of summation+refresher list is always very appreciated.
I think both of these issues should be fixed in the next release.
I'm not sure what you mean here.
This is fixed for the next version.
This should be fixed, but isn't yet.
Not sure what you mean?
Not sure why. If PaintersPicker is a third party haxie/input manager it may be that it doesn't work under garbage collection, and so fails to get loaded.
Is this a request or a bug? :)
Are you sure? By default why you type in the search field it should be case insensitive.
Persistent searches are already implemented...So you can quickly access searches that you've predefined in your new document. But I don't know how I would allow you to specify that new documents should have a particular search open in a separate tab when you create it.
reply | edit
Nick Brawne - June 23, 2008 3:04 PM
see below
reply | edit
Nick Brawne - June 23, 2008 3:05 PM
In the Rules tab, one of the listed rules is: Group Header. There is also a checkbox for 'Entry is group header', but the drop down below it refers to project name. Everywhere else, groups are also referred to as projects.
Color Pickers are neither haxies or input manager plugins (they don't require SIMBL) They are placed in Library / ColorPickers. Another picker I use that is not recognized is Shades (http://www.chromaticbytes.com/shadesTour.php)
I don't know.
Its the current behavior and could be seen as a bug !
Appears to be fixed in v52
Personally I find it really annoying to create a new doc and find it pre-populated with empty tabs that relate to search terms from other docs.
Persistent between starts for the same doc = good
Persistent to new docs = bad
reply | edit
jesse - June 23, 2008 3:26 PM
I think things are actually labeled correctly, though maybe there is a way to make it clearer. Group headers and projects are not the same things. Group headers can be either top level projects or they can be tag names (when grouping search results by tag).
Odd, I'm not sure then. But I'm still pretty sure that it's not something that's in my control, I'm not doing anything special with color pickers. In fact I don't manage them at all, it's all handled by Cocoa's built in color view class.
Can you explain a bit more what's happening though? For me, it seems that I can add tags to notes, and they don't change from notes to tasks. Maybe you mean the the @done tag also applies strikethrough formatting to notes? That's true, but it's not changing the notes "type". If you don't want notes with @done to get strikethrough formatting you can adjust the "Tagged Done" rule to require that the match is also of type task.
I misunderstood you. I though you meant that you wanted that as a feature. I didn't realize that it was already happing when you created a new document. That sounds like a bug... Can you:
reply | edit
Nick Brawne - June 23, 2008 4:22 PM
Persistant searches with new docs appears to have been fixed in v52. (looks ready for prime time)
Apart from color pickers the remaining issues are subjective. Bug ? or Feature ?
reply | edit
Matthew Crider - June 23, 2008 4:24 PM
Where is version 52?
reply | edit
Nick Brawne - June 23, 2008 4:27 PM
Pre-pre-release, testing to see if it squashes a quit on launch bug.
reply | edit
Topic's comments