Well, hey, we here use Cocoa and are prepared for 64-bit as of the next couple
of weeks.
But that’s about basic changes in chip architecture and is understandable. I
was more worried about any hints of leaving Obj-C behind, and I’m glad to hear
that the Obj-C interface will continue to be valid
base behind.
Jeff Evans
On Oct 2, 2019, at 10:43 AM, Richard Charles via Cocoa-dev
wrote:
> On Oct 2, 2019, at 11:14 AM, Turtle Creek Software via Cocoa-dev
> wrote:
>
> Sadly, we just decided to abandon the Cocoa update for our app.
Great historical overview
If it’s any help: Microsoft Visual Studio now offers C++/winrt, a pure C++
environment that works great. Doesn’t seem to be well-known yet but it’s
efficient for Windows Store apps. So all our C++ code goes straight into the
Win version.
No need for C# or C++/CX, etc.
On the Mac I use C++ too ex
that in an app that had been doing some
things deep with the drawRect: call that was causing the view to become dirty
again. I fixed it by getting rid of that code. Try looking for something like
that first.
--
Gary L. Wade (Sent from my iPhone)
http://www.garywade.com/
> On Nov 20, 2016, at
p.s. As I was unclear: the image returns YES to flipped and draws on that
assumption, looking good. When I say the image in the print dialog is "flipped"
I mean that it is backwards - mirrored - the reverse of what it should be - as
if it were an unflipped view - until it is drawn a second time.
I'm printing from a view-based OSX app (compiled for 10.11), and have found it
easy to print by creating a print operation from the view in question. The view
is flipped (that is, returns YES to IsFlipped) and looks good on screen. The
view creates a print operation this way:
NSPrintOpe
(even nonmutable)
inited with objects.
Jeff
On Sep 21, 2016, at 9:33 PM, Jens Alfke wrote:
> On Sep 21, 2016, at 9:19 PM, Jeff Evans wrote:
>
> Is it really true what Jens says, that [[NSArray alloc]init] always
> returns the same pointer?
> If that is the case, how
Whoa - maybe I've had too much wine with dinner, but:
Is it really true what Jens says, that [[NSArray alloc]init] always
returns the same pointer?
If that is the case, how can one declare two separate arrays?
Jeff
On Sep 21, 2016, at 8:50 PM, Jens Alfke wrote:
> On Sep 21, 2
have had to deal with these
AV sync issues and can give more feedback.
Doug
> On Feb 4, 2016, at 4:39 PM, Jeff Evans wrote:
>
> Doug, I had found that if the drawing mechanism was still cleaning up a few
> visual details - adjusting a beam or stem length after getting the context
n, or appears
to be.
Jeff
On Feb 4, 2016, at 4:19 PM, Noah Desch wrote:
The `needsDisplay` property will tell you if there are any pending draw
requests since the last time the view was drawn, is that what you are looking
for?
-Noah
> On Feb 4, 2016, at 6:07 PM, Jeff Evans wrote:
>
&g
b 4, 2016, at 15:52, Jeff Evans wrote:
>
> Clark, it's a music app; a piece is composed and placed on the screen;
> there's a lot of massaging going on as the music adjusts visually.
Instead of looking to the view system to know when your code is done laying
things out, why n
ust a single view - perhaps
it would be enough to check needsDisplay! Worth trying.
Jeff
On Feb 4, 2016, at 4:06 PM, Clark S. Cox III wrote:
> On Feb 4, 2016, at 15:52, Jeff Evans wrote:
>
> Clark, it's a music app; a piece is composed and placed on the screen;
> there's
difference in the
appearance.
So I figure: the system presumably knows if it is about to send more redraw
requests to that view. Is there any way I could know what it knows?
Jeff
On Feb 4, 2016, at 3:31 PM, Clark S. Cox III wrote:
> On Feb 4, 2016, at 15:07, Jeff Evans wrote:
>
Suppose one wants to do a task in an NSView only once it has no drawRect calls
pending. Is there any way to tell, for a particular NSView, if there are any
drawing events coming up? Whether, that is, the view is up to date?
I've tried counting my explicit uses of setNeedsDisplay and decrementing
to do anything yet... now we return to our regular programming.
With deepest apologies, Jeff
On Feb 3, 2016, at 4:28 PM, Jeff Evans wrote:
Colleagues, I have been trying to create a draggable NSView for OSX and am
stumped by the stubborn refusal of the view frame to change.
Here's the es
Colleagues, I have been trying to create a draggable NSView for OSX and am
stumped by the stubborn refusal of the view frame to change.
Here's the essence: in responding to a mouse drag there is a place where I do
this;
NSPoint newLocation = event.locationInWindow;
NSRect frame = self.frame;
fr
thing
basic here. The chapter does contain the anchor page 3>
Yours, Jeff
On Jan 21, 2016, at 5:32 PM, Quincey Morris wrote:
On Jan 21, 2016, at 17:17 , Jeff Evans wrote:
>
> In OSX I'm using an NSURLRequest to load a file url in WKWebView. Works
> fine un
Colleagues,
In OSX I'm using an NSURLRequest to load a file url in WKWebView. Works
fine unless I try to add an anchor to the path, for example,
[path]/filename.html#anchorname
The problem appears to be that the # gets escaped to %23.
I tried [NSURL URLWithString: anchorname relativeT
18 matches
Mail list logo
