Enable friendly naming quick filters (I will PR)

[cbordeman]

Would like to have a Name column on the edit filters windows. If present, the Name would display on the menu.

I'll PR this.

[rmcrackan]

Hey, what's the matter? My hack ain't good enough for you?

😄 Thanks for the new feature.

A word of warning: I keep classic (winforms) and chardonnay (avalonia/xaml) as close to feature parity as possible. Any UI changes will need to be made to both. (Obviously unless it's framework-specific like the PR you did for the xaml scroll bars.)

[cbordeman]

I actually didn't notice you could do the hack, but I think making it formal has some value for the same reason.

I'm going to go ahead and have a go at a separate field, though my WinForms experience is very limited. IMO the chardonnay (Avalonia) is so much better, is there a reason it is still around? Pardon my ignorance.

[cbordeman]

Also, I realize that while loading the filters, I'll need to handle the missing name field gracefully so as to not nuke existing data.

[rmcrackan]

is there a reason it is still around?

Fair question and one I've considered. Despite the legion reasons not use winforms:

• Years before Libation was Libation, this was just an app I made for myself in winforms. (Winforms was the only version until another dev'er did the full Avalonia port a few years ago.) It's simply what I knew better so I went with it.
• Every time I try to do more than trivial things in xaml I end up tearing out my hair. Of which I have little to spare.
• It's absolutely rock solid and supported officially by MS. Every so often bugs come up in Avalonia. I don't know if I've ever found a proper bug in winforms since I started using it over 20 years ago.
• It's time-tested and filled with mature things. It's had out of the box screen reader support since forever. I don't have accessibility needs but I have close family who do so I'm especially sensitive to such things.

[CharlieRussel]

As a devoted user of Libation in its Classic (winform) implementation, I'd be really unhappy if it went away. It has the one thing going for it that beats everything, it JFW.

[rmcrackan]

JFW

lol. No worries friend -- classic isn't going anywhere. Classic and Chardonnay are here to stay. One day I'll remember to write up an explanation in the faq. One day...

[cbordeman]

@CharlieRussel What doesn't just work in the chardonnay?

[cbordeman]

@rmcrackan That's a very good explanation, thanks. WPF is actually rock solid, too, since it's not been receiving feature updates for several years now. But Avalonia so new, it certainly still has holes, and there's few third party libs. I'm brand new to it, and the reimagined styling system is weird!

[CharlieRussel]

@cbordeman -- Not being the developer here, I'm not sure what does/doesn't work. But I know from following the bugs/remediations here that @rmcrackan and others have sometimes had to jump through some hoops to get things working. As of now, so far as I know, the functionality is equivalent. But I'm old school and quite happy with the L&F of classic.

[cbordeman]

Gotcha. I'm here to try to made this app useful to the blind and nearly blind, since I have blind relatives. I am not seeing any big bugs, really, just hoping to fix any big showstoppers. Thanks for your answer.

[cbordeman]

PR #997 created.

[rmcrackan]

Thanks. I’m heading out of town for a few days and will look at this early next week