At version 4.1 I thought listpro was great and it did exactly what I wanted. If you don’t really need the new features of 5.0, you might want to try it before you upgrade.

A couple things I’d like to clear up are the release schedule and “how long does it take to make this thing?”

ListPro 4.1 came out under 2 years ago. I’m not arguing that it wasn’t a long wait (we are acutely aware of how long it has been between releases!), but we didn’t hit the 3 year mark (thank goodness!)

Also, we didn’t spend that whole time working on ListPro. As you may have seen in the “team pictures” we post every now and then, we aren’t a big software house. Bigger than some, sure, but we don’t have 70 people on staff. We also don’t contract out any of our work or send it overseas. Every program we release is a product of hard working, full-time staff based right here in Ann Arbor, Michigan. That means that everyone here wears more than one hat. Our developers not only work on multiple titles, they also handle a lot of our infrastructure work, from online stores to sales databases.

Either way, the good news is that we are working towards more frequent release cycles in the future. I can’t offer dates but a lot of what changed in both eWallet 5.0 and ListPro 5.0 were things that will let us work more efficiently (and thus more quickly) in the future.

Thanks again for all your comments and support!

For example when using a single large master task list as I leave work, I could select the ‘Leaving’ filter which would show my home to-dos, errands and ‘flagged – must do before leaving ‘ items.
Coming in to work the next day I could slect my ‘Arrive at desk’ filter whch would filter all of todays to dos, quick desk calls etc.

If a checkbox is the first item in a list then I could click to see the details, but a double click would check (strikeout) the item (by opening the details with the checkbox highlighted – as it does now – and the second click would check the box and return to list view; but all to quick to see)

I think that this does not make the interface any more complex, in fact for me it would add a better safetynet for the times that I accidentally strike out items that I did not mean to.

I think that this could easily be incorporated as an option without increasing the complexity of the interface. It could be a property of the list itself – just an extra checkbox on the list property settings. For example make the default to be ‘click for details’ – but have a checkbox on the list properties – ‘settings’ tab labelled ‘single click strikeout for those that don’t want to go to the datils view on a single click.

This would be a really big improvement for me.

I’m waiting for the 5.1…
Yvan