Definitely follow that train. Doing things with the wrong context is
definitely one possibility. By the way, the setNeedsDisplay doesn’t need to
happen on that view; it could be a subview, and there could be some other
operation that implicitly causes such a dirtying—remember, there’s also
se
They seem pretty terrible. No explanation of any of the things.
The GCD guide from Apple is very old, with out-of-date info, and lacking info
on the newer things (AFAICT).
Is there a way to look at the C header files for GCD? I tried opening
Dispatch.h, and Xcode is stuck "Generating Interface…
Hmm. If you scroll down in the generated Swift interface file, you get a bunch
of block comments from the C version. Sigh.
> On Nov 21, 2016, at 13:48 , Rick Mann wrote:
>
> They seem pretty terrible. No explanation of any of the things.
>
> The GCD guide from Apple is very old, with out-of-da
On Nov 21, 2016, at 1:48 PM, Rick Mann wrote:
> Is there a way to look at the C header files for GCD? I tried opening
> Dispatch.h, and Xcode is stuck "Generating Interface…", presumably a Swift
> interface I don't want to see.
I've found that if I tell Xcode to open Foo.h, and Xcode gets stuc
On 11/20/2016 8:15 PM, Robert Monaghan wrote:
I have been working on a custom UI for my Cocoa application. By looking around
the internet, I have managed to learn how to subclass a large number of UI
objects on MacOSX. In many cases I could make the appearance work the way I
want.
The last UI
macOS 12.1, Xcode Version 8.1 (8T61a).
App with two windows: FestEvent and Preferences, which have Autosave names of
FestEvent, resp. Preferences.
Start App → FestEvent window will show.
Make it to show Preferences window as well.
Move both windows around and observe Preferences.plist to have a
