Some of the major topics covered in this section include:
| From the WebKit documentation at: | |
| http://www.opensource.apple.com/source/WebKit/WebKit-7533.16/chromium/src/mac/WebInputEventFactory.mm | |
| // Of Mice and Men | |
| // --------------- | |
| // | |
| // There are three types of scroll data available on a scroll wheel CGEvent. | |
| // Apple's documentation ([1]) is rather vague in their differences, and not | |
| // terribly helpful in deciding which to use. This is what's really going on. | |
| // |
| @implementation UILabel (SwizzlingExamples) | |
| + (void)load | |
| { | |
| SwizzleSelectorWithBlock_Begin(self, @selector(initWithFrame:)) | |
| ^(UILabel *self, CGRect frame) { | |
| if ((self = ((id (*)(id, SEL, CGRect))_imp)(self, _cmd, frame))) { | |
| // ... | |
| } | |
| return self; |
| // TODO: setting window transforms (or mission control) flattens layers... | |
| // TODO: Mask image vs path (layer)? | |
| /// `NSVisualEffectView`: | |
| /// | |
| /// A view that adds translucency and vibrancy effects to the views in your interface. | |
| /// When you want views to be more prominent in your interface, place them in a | |
| /// backdrop view. The backdrop view is partially transparent, allowing some of | |
| /// the underlying content to show through. Typically, you use a backdrop view | |
| /// to blur background content, instead of obscuring it completely. It can also |
tl;dr: Wayland is not "the future", it is merely an incompatible alternative to the established standard with a different set of priorities and goals.
Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating e
| import CoreGraphics | |
| extension CGKeyCode | |
| { | |
| /* | |
| * From Events.h in Carbon.framework | |
| * Summary: | |
| * Virtual keycodes | |
| * | |
| * Discussion: |
I've recently tested on how to move the custom domain catch all email from G Suite to the new iCloud+ Catch All feature and wanted to share my experience.
The end result is having Custom Domain email and Catch All routing, that can be fully used via Gmail, including receiving and sending emails.
- Setup your Custom Domain (or subdomain) with iCloud+
