Why doesn't dBpa have the same standard GUI functionality that's available in virtually every other software program that uses "columns" to display data?
That is:
1) The 'ORDER' of the columns in dBpa cannot be changed. I realize specific columns can be 'enabled' or 'disabled', but NOT reordered. This is ridiculous. One should be able to move the columns into the order that they feel works best for them. I like... [Track] [Artist] [Title] [Length] [Rip Status], but must live with [Track] [Title] [Length] [Rip Status] [Artist].
2) While individual columns CAN be resized, THE CHANGED SIZES DO NOT HOLD! Not only does this occur from one start of the program to the next, but most annoying is that the columns resize back to their defaults from DISC to DISC! This is not only extremely frustrating and downright annoying as it makes one do "double-work" by having to resize the columns each and every time a new disc is loaded, but it's one of the simplest standards built into every GUI of every program written since Windows 98! So why not in dBpa in 2015?
Am I the only one experiencing these problems?
If I am, could someone please tell me how to resolve them? But, if I'm not, PLEASE FIX these two simple issues by the next release of dBpa.
Thank You.
C64
dBpoweramp R15.3 for Windows
Windows 7 (x64)
That is:
1) The 'ORDER' of the columns in dBpa cannot be changed. I realize specific columns can be 'enabled' or 'disabled', but NOT reordered. This is ridiculous. One should be able to move the columns into the order that they feel works best for them. I like... [Track] [Artist] [Title] [Length] [Rip Status], but must live with [Track] [Title] [Length] [Rip Status] [Artist].
2) While individual columns CAN be resized, THE CHANGED SIZES DO NOT HOLD! Not only does this occur from one start of the program to the next, but most annoying is that the columns resize back to their defaults from DISC to DISC! This is not only extremely frustrating and downright annoying as it makes one do "double-work" by having to resize the columns each and every time a new disc is loaded, but it's one of the simplest standards built into every GUI of every program written since Windows 98! So why not in dBpa in 2015?
Am I the only one experiencing these problems?
If I am, could someone please tell me how to resolve them? But, if I'm not, PLEASE FIX these two simple issues by the next release of dBpa.
Thank You.
C64
dBpoweramp R15.3 for Windows
Windows 7 (x64)
Comment