I am still waiting for hours and minutes entry and storage of flight times. I've been waiting 3+ years and have had comments "dangled" in front of me by NC-software that this change is just around the corner for most of that time. Clearly it is not a priority and I will keep my money tucked safely into my pocket for now. NC-software appears to be doing well now so why mess with success?
I work for an airline and we track all flight time in hours:minutes. I also am familiar with computer programming and know this would be a very significant change to the data underlying the program and it's interfaces. I would also note that it is not sufficient enough for the entry of times to be in hours:minutes but that the data must be stored as such (well, actually in minutes).
I respect the work effort required to change. However, I also posit that hours:minutes it is a much more universal method of tracking flight time because hours.tenths can be converted to hours:minutes without loss of data resolution, but not vice versa. Hence, NC-software could expand their market significantly by storing flight time in minutes and offering Pilots the choice of entering data in hours.tenths or hours:minutes.
There are several threads with hours:minutes entry in common. I trust this response will add to the noise of those clamoring for change.