Sonar's native preset manager fix requests

[Starship Krupa]

Use of a DAW's preset management system is integral to my workflow. Why it is is not important.

CbB's had some issues, but Sonar's has moved even further from ideal. Here are the issues I'm seeing with Sonar's preset manager.

In CbB, when the user double clicks in the preset name field to enter a name for a new preset, text turns black and the background turns white. This is fine.

Where Sonar has slid downward from CbB is that the typeface also changes, to something that looks like the "Console" or "Courier" font:

That doesn't hurt the functionality, but it looks weird.

More of a problem is that once the user enters the name and hits <enter>, there's no visual indication that the new preset hasn't yet been saved. Whereas in CbB, using the Tungsten theme, after a new preset name has been entered, the background of the name field changed color to signify that it hadn't yet been saved, and would be lost otherwise. This wasn't the case with Mercury, it seems to be an error that was corrected for Tungsten:

The graphic resource for this in CbB is Plug-in property page/Preset Name drop-down menu. Tungsten uses a light orange cell but Mercury uses the same grey for both cells.

Ideally, the indicator for not having saved your new preset would be the Save button changing state. Or even just saving the new preset when the user hits <enter>.

Please restore/improve this functionality. If I'm correct and the new UI also supports 2 button states for the preset name drop-down menu, if should be possible to fix it.