undefined | Better HN

0 pointsjcelerier8y ago0 comments

native_view is just a NSView which is where you have to render your stuff on macOS, whatever the toolkit used. But the actual widget implementation is custom: take for instance QComboBox.

It is painted here:

https://github.com/qt/qt/blob/0a2f2382541424726168804be2c90b...

This calls at some point QStyle::drawControl which ends up here on mac : https://github.com/qt/qt/blob/0a2f2382541424726168804be2c90b...

this ends up here in this big switch : https://github.com/qt/qt/blob/0a2f2382541424726168804be2c90b...

which leads us here, in the drawComboBox function where mostly everything is done by hand: https://github.com/qt/qt/blob/0a2f2382541424726168804be2c90b...

and also here: tadam, actually it just uses the "windows" (actually fairly generic and themeable) style for drawing : https://github.com/qt/qt/blob/0a2f2382541424726168804be2c90b...

See also this qt blog: http://blog.qt.io/blog/2017/02/06/native-look-feel/

0 comments

2 comments · 1 top-level

LeoNatan258y ago· 1 in thread

I see a lot of HIToolbox calls, which is what AppKit uses internally to draw. So from that third to last link, it seems like a hybrid solution. Not optimal but still better than Electron or Flutter.

jcelerierOP8y ago

> I see a lot of HIToolbox calls, which is what AppKit uses internally to draw.

sure, but that's not the same as using a NSComboBox directly, and that's not using Apple's layout engine (based on cassowary, wasn't it) either. Not that I think that this is a bad solution : it allows software with a strong identity to have fairly custom UIs that are consistent across platforms.

j / k navigate · click thread line to collapse