(Canadian

All goes back to customer support.Even with Q17 for Windows I had the option of using a 2 line register. The same with every other version w/Windows but with Windows 17 for Mac. Why?
Not customer support, really, but development resources -- or lack thereof. There is a long list of features that we in the customer base have asked Quicken to add to the Mac product. Some were in the legacy Mac program (Quicken 2007); some are in Quicken for Windows. There aren't enough developers to tackle all these requests quickly; new/improved features do come, just not as fast as anyone would like.Even with Q17 for Windows I had the option of using a 2 line register. The same with every other version w/Windows but with Windows 17 for Mac. Why?
Please, be sure to add your own vote as well.
@smayer97 It is not, in fact, highly presumptuous. It's exactly what the longtime product manager for Quicken Mac has stated about why they don't have a 2-line display, and why they were unlikely to devote the resources to create one.smayer97 said:@jacobs that is highly presumptuous as to the amount of effort required to implement and impact on performance.
Agreed, but I will tell you something that I have observed over my years as a developer.smayer97 said:A 2-line register design is NOT what prevents "more flexibility" to move or resize columns. In fact, in QM2007, they started to deliver that very capability (in Brokerage registers, you can actually resize the Transfer and Memo fields on the second line, independent of the first). So it is quite possible to have both a 2-line design and still maintain flexibility.
Sometimes the best thing you can do for your customer is not to "listen" to them.Unknown said:All goes back to customer support.Even with Q17 for Windows I had the option of using a 2 line register. The same with every other version w/Windows but with Windows 17 for Mac. Why?
But that's the rub. Once introduced it is highly unlikely that the customers would allow the Quicken developers to remove it whether it creates bugs or not (major out cry). Not to mention that as a practice companies really hate to throw out code that they spent a large amount of time developing. And add to that most likely at first the bugs would be considered "startup bugs that need to be fixed", and not "long term bugs inherent the way it is done", and as such it would be much more imbedded and harder to remove by the time they figured this out.RMWms said:I can work with whatever is settled upon, and if 2-line comes back, I really hope we don't see bugs and other code issues come with it. If that's the case, I'm fine with returning to single line.
There's no rub.... it would be an option that users can turn on or off... So, if it turns out to be too buggy to a user's liking they can switch back to 1-line display.Chris_QPW said:But that's the rub. ...RMWms said:I can work with whatever is settled upon, and if 2-line comes back, I really hope we don't see bugs and other code issues come with it. If that's the case, I'm fine with returning to single line.