3 ms·
Why not? Sometimes the stuff in the standard toolkit is crap. I mainly work on the Mac, and the classes provided with AppKit vary greatly in quality. Most part
by jakobegger 11y ago
Why not? Sometimes the stuff in the standard toolkit is crap.
I mainly work on the Mac, and the classes provided with AppKit vary greatly in quality. Most parts work really well, but others are really buggy. For example, after years of struggling with IKImageBrowser, I just wrote my own grid view. It would have saved me a lot of trouble if I'd have done that in the first place.
- st3v3r 11y agoFor a limited few things, maybe. But the vast majority of things don't need that. I'm dealing right now with someone who wrote their own autocomplete text view, which doesn't work properly now that I've fixed their mess with auto layout.
- jakobegger 11y agoI'll have to do that soon as well... I get lots of requests for auto-complete in my app, but it looks like Apple's built-in autocomplete is unfortunately not flexible enough for my needs (eg. it has it's own ideas what a word is that aren't compatible with SQL)