Conversation
c5e2b01 to
9f6fb94
Compare
neilcsmith-net
left a comment
There was a problem hiding this comment.
Thanks! Looks good on reading. Not tested yet. Probably needs squashing before merge.
Handles my concerns about customization / disabling the display. I still think the node prefixing approach is flawed against filtering the hierarchy, but if everyone else is on the board with the current approach then this is good to go.
Please don't merge this until @mbien has followed up here or on the sorting review though, just in case that gets complicated in master.
I'm tempted to say, yes too much, except that pipeline example does look quite nice! I'm curious where the |
likely. Something seems to equate "" with null during parsing. Plain old properties don't do that usually.
yeah I like that one too. The reason I experimented with this is because it looked like the symbol+space pattern appears to be fairly limiting in what symbols you can use. Sometimes you want to repeat a symbol and postfix a space, other times you want to repeat the space and add a symbol at the end - or use different symbols like in that pipeline. |
Yes, I know. I was surprised reading that as I thought that was how we'd tell people to switch it off. Still, as long as we know, we can explain. At a guess it's due to the code at https://github.com/JFormDesigner/FlatLaf/blob/e735c4898e6772c734229c688976faceab1bdfc8/flatlaf-core/src/main/java/com/formdev/flatlaf/UIDefaultsLoader.java#L461 Makes sense given the values are typed I suppose, or maybe intended to allow override removal. |
|
Yeah, the pipeline symbol looks pretty nice:
I don't mind changing the algorithm to use |







UIManager(one new and one shared with other modules) to allow L&F customization or ...