Behavior of Esc-key in some windows [DONE]
Behavior of Esc-key in some windows [DONE]
In the "File already exists" dialog and similar windows where there is a "Hide" and "Abort" option, the Esc-key currently hides the window. I would expect that it aborts the operation. What do you think?
Re: Behavior of Esc-key in some windows
Yup. That confused me as well. Esc means "get me out of here" (ESCAPE!) and I was surprised to find out an hour later that a window is still hidden there, with operation pending, waiting for me to click a button.
Re: Behavior of Esc-key in some windows
I agree that this pattern is causing some confusion and will get into it later.
Currently I'm all in new file panels UI, and it's a quite complex pile of code.
Currently I'm all in new file panels UI, and it's a quite complex pile of code.
Re: Behavior of Esc-key in some windows
"new file panels UI" -- oh yeah! "brief mode" confirmed!
Re: Behavior of Esc-key in some windows
In fact:
In this case any Apple's recommended approaches immediately transforms all this beauty into a pile of crap.
The trickiest part is to make all these fancy Cocoa APIs run smooth under any serious workloads (at least thousands of items).In this case any Apple's recommended approaches immediately transforms all this beauty into a pile of crap.
Re: Behavior of Esc-key in some windows
Sweet! But as for general UI sluggishness -- I've noticed this about macOS as well. Some things are wonderful (like scrolling webpages, especially with touchpad) some things (like scrolling through large data sets, i.e. database rows, or anything with Xcode) feel like playing a game at 5 frames per second Overall, when using keyboard, Windows always felt much more snappier than macOS. So what you're saying would confirm my suspicion that there's something nasty going on under the hood.
Re: Behavior of Esc-key in some windows
Yep. Cell-based NSTableView was kinda faster, but it's deprecated now. View-based NSTableView, on the other side, is just terrible in terms of performance.mike wrote:The trickiest part is to make all these fancy Cocoa APIs run smooth under any serious workloads (at least thousands of items).