Billings badly needs to remember how columns have been sized in the project view, as well as other visual settings like sort order.

Right now, every time I launch Billings, the column widths are set to some arbitrary uniform value which is far too big for things like the Quantity, Rate and Total columns (I would have to be charging something like the US national debt to need so much space) and yet are stupidly small for columns that actually needs some space like Project/Slip Name, which invariably gets truncated.

Furthermore, the sort order that I place on a list of projects always gets forgotten.

What's the point of letting us change the column widths if it's going to be forgotten every time I quit.

Is this really how you intended Billings to behave?

Column order and sort orders are definitely being remembered.

What you may not realize is that the "All Projects" view is different that a single client's project view.

The all projects view has an additional column and stores it's preference separately than the regular projects view.

I didn't mention column order. You're right; re-ordering of columns does get preserved when quitting and re-launching the app.

I am aware of the difference between "All Projects" and a single client view.

Sort order is definitely NOT being saved. If I click on a column heading to sort by that column, it is highlighted blue. When I quit and re-launch, no columns are ever highlighted, and the sort order is arbitrary (creation order?).

You neglected to mention column width, but this is definitely not being stored either.

Example:

• Click on a client in the side bar
  
• Re-size the Quantity, Rate and Total columns to their minimum width.
  
• Re-size the Name column to the maximum size the viewable without pushing any of the columns off the right edge of the window.
  
• Quit
  
• Re-launch
  
• Column widths are not preserved. They just get re-drawn at widths that *look* like they have been equally distributed, but actually haven't quite.
  

*BUMP*

Any useful response on this?

I guess not... clearly an interface that pleases itself (rather than, you know, the user) is preferable for Marketcircle...