I'm beginning to think this code is
2025-01-20 23:25:02.970152+01 by Dan Lyke 2 comments
I'm beginning to think this code is just messing with me:
hiddenPasswordField.isHidden = true;
2025-01-20 23:25:02.970152+01 by Dan Lyke 2 comments
I'm beginning to think this code is just messing with me:
hiddenPasswordField.isHidden = true;
comments in ascending chronological order (reverse):
#Comment Re: I'm beginning to think this code is made: 2025-01-21 00:04:34.820459+01 by: markd
One of those historical accidents they probably could have handled a LOT better.
in the olden days, there was no visibility flag on NSView - to hide one, you moved it offscreen or took it out of the view hierarchy.
Eventually someone convinced apple that having a visibility flag would be a really convenient thing. "We need a default value of zero because that's what new objective-C objects get initialized to" - rather than figuring out how to get all the view subclasses to be visibility by default, a new flag that's useful as a zero was added - hidden. So now you have to do to the double-negative mind screw every time you want to reason about it. (amusingly enough, during my weekly MusicJot pairing last week, we complained about that very construct)
#Comment Re: I'm beginning to think this code is made: 2025-01-21 00:04:34.820459+01 by: Dan Lyke [edit history]
Yeah, I've mostly gotten used to it, but the fact that this code has a hiddenPasswordField : NSSecureTextField! and a visiblePasswordField : NSTextField! makes reading some if it bizarre.