Posts

Post not yet marked as solved
3 Replies
279 Views
I have a custom NSView embedded in a NSScrollView. [NSView drawRect:] is called once, when the window is created and displayed, and the rendering is exactly how it should be. Then I resize (shrink) the window, which does not make [NSView drawRect:] being called again, as no new part of my view needs to be drawn; however, the window's content is flushed again on screen, and the rendering is now different. How could this be possible? I am logging a message in my [NSView drawRect:] implementation, so I am absolutely certain that it is called only once in this scenario. Is it possible that a single drawing instruction ([NSBezierPath stroke], in this case) called only once actually produces two different rendered images, in two different drawing buffers, and that the buffer flushed to the screen can change depending on the size of the window?? Now, what is different in the rendering? Two things: antialiasing is performed differently (the line width is 0.25 pixel), correctly in the first case, and not very smoothly in the second case. I also changed [NSBezierPath setFlatness:], and this flatness is taken in account in the first case, and unchanged (default flatness) in the second case. When I continue to resize the window, enlarging then shrinking it, drawRect: is called when I enlarge it, and depending on the window size, sometimes I get the "correct" rendering, and sometimes the "wrong" one (for the whole view; it is not limited to the newly revealed area). I have a built-in display set to "more space", and an external non-retina monitor; with "desktop & dock" settings set to "displays have different Spaces", in case this has any impact on the situation.
Posted Last updated
.
Post not yet marked as solved
1 Replies
1.8k Views
Hi all,I have an Xcode 10.2 workspace with 3 projects: DeepLib, DirectLib, and App. libDeepLib.a is linked with DirectLib, and libDirectLib.a is linked with App. Using the new build system, I can't make Xcode to rebuild both DirectLib and App when I modify a source file in DeepLib (this was OK with the legacy build system).I have tried this:- enabling "Find Implicit Dependencies" in the scheme- adding DeepLib and DirectLib before App, in the Build pane of the scheme, checking all checkboxes- adding explicit dependencies by adding DeepLib.xcodeproj to DirectLib, then add DeepLib in DirectLib's target dependencies build phase; and the same with DirectLib and AppWhat should I do? I'd rather avoid linking DeepLib to App directly, as DirectLib is designed to hide DeepLib to the client application. And of course, I'd like to avoid cleaning the build folder for each build.Thanks!
Posted Last updated
.
Post marked as solved
1 Replies
7.3k Views
Hi,I am codesigning my macOS app from terminal (after adding some resources I don't want to copy using Xcode build phases). When I verify the signature using "codesign --verify", this is OK, but when I run "spctl --assess", I get "a sealed resource is missing or invalid".How can I know which resource is missing or invalid? What does spctl checks that codesign don't?Thanks
Posted Last updated
.