Thanks for your comments.
> My first instinct when someone says "not reproducible for me with a scroll
> view" on Mac is: Maybe it only occurs with overlay scrollers, or only with
> separate scrollers? Have you tried toggling that setting?
If you mean the "show scroll bars" setting in System Pr
My first instinct when someone says "not reproducible for me with a scroll
view" on Mac is: Maybe it only occurs with overlay scrollers, or only with
separate scrollers? Have you tried toggling that setting?
Also, are you calling setNeedsDisplay: or setNeedsDisplayInRect: anywhere?
That's usual
On 1 Jan 2020, at 2:46, Rob Petrovec via Cocoa-dev wrote:
drawRect is not deprecated. Correct. However, it is technically old
fashioned. It is much more efficient to use layers. Layers can take
better advantage of the video card especially during animations, and
don’t require unnecessary redr
>> I, for one, wasn't able to reproduce it on the 5 machines I was able to put
>> my hands on.
>
> Although I have not seen a *reproducible* case either, I have seen that it is
> much more likely to occur in text views with hundreds of lines or rows, so
> you should try such in your tests.
M
> turning it on did not cause the issue to show up on Mohave
>> ...
>> I, for one, wasn't able to reproduce it on the 5 machines I was able to put
>> my hands on.
> Curious, how were you able to verify that turning on copyOnScroll in
> your app and running it on Mojave did not reproduce the
On 2019 Dec 31, at 00:34, Eyal Redler wrote:
> I, for one, wasn't able to reproduce it on the 5 machines I was able to put
> my hands on.
Although I have not seen a *reproducible* case either, I have seen that it is
much more likely to occur in text views with hundreds of lines or rows, so you
> On Dec 31, 2019, at 1:34 AM, Eyal Redler wrote:
> Nothing old fashioned or unorthodox in what I'm doing.
drawRect is not deprecated. Correct. However, it is technically old
fashioned. It is much more efficient to use layers. Layers can take better
advantage of the video card especi
I honestly think this is fall out from copiesOnScroll being deprecated and the
clip view always behaving as if it was set to true. My guess is you will see
the same problems in your apps if you ran them on Mojave with copiesOnScroll
set to true. In which case you need to update your app to wor
Since installing macOS 10.15, I see blocks of empty text view lines or table
view rows often when scrolling through many apps, including file browser
windows in Path Finder (cocoatech.com) and, for heaven’s sake, even in BBEdit.
Conclusion: This is not “our” faults. Thank you, Eyal for submitti
On 27 Dec 2019, at 13:03, Allan Odgaard via Cocoa-dev wrote:
> I do change copiesOnScroll.
Sorry, I meant that I do *not* change copiesOnScroll.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comm
On 16 Dec 2019, at 16:35, Eyal Redler wrote:
It does look very similar (except for the fact that in your example
the text is also cut on the right. Do you have copiesOnScroll turned
off as well?
I do change copiesOnScroll.
Apart from opting out of responsive scrolling, it’s should be a very
I submitted the issue via feedback reporter. Case number: FB7509033
Eyal
> On 19 Dec 2019, at 17:10, Gary L. Wade wrote:
>
> Interesting. This could be a layering issue then, and it could be due to a
> configuration unique to your customer’s setup. Since you’re doing things on
> a lower le
I read most of the discussion but maybe missed some parts so it might repeat
something or miss the point altogether.
How big is your view. I had a lot problems with a big view and layer backing.
It will use tiled layers as a layer can only be a few thousand pixels tall.
And when you do any che
Interesting. This could be a layering issue then, and it could be due to a
configuration unique to your customer’s setup. Since you’re doing things on a
lower level than expected, there may be some nuance you need to add or
something Apple needs to fix that may work fine using higher level fra
>>
>> OK, I'll try to get the sysdiagnose from my users before submitting. I must
>> say I'm really skeptic regarding the relation with my use of CG. It is not
>> that CG is not used by CT and everything else is also using CG.
>
> CG may not be the issue… and I cannot offer a better suggestion,
Eyal,
> On Dec 19, 2019, at 02:55, Redler Eyal via Cocoa-dev
> wrote:
>
>
>>
>> Since you’re using CoreGraphics, it’s very likely there’s an edge case with
>> your customers’ systems that you aren’t encountering. CG is pretty much the
>> lowest practical level in the graphics stack. Since
> Since you’re using CoreGraphics, it’s very likely there’s an edge case with
> your customers’ systems that you aren’t encountering. CG is pretty much the
> lowest practical level in the graphics stack. Since your app does reproduce
> the issue but in other configurations than yours, you could
Since you’re using CoreGraphics, it’s very likely there’s an edge case with
your customers’ systems that you aren’t encountering. CG is pretty much the
lowest practical level in the graphics stack. Since your app does reproduce the
issue but in other configurations than yours, you could still a
I am drawing using core graphics. I tried turning copiesOnScroll and this
didn't seem to help.
I'll gladly write a feedback report but I'm not able to reproduce this so I
can't give an xcode project that will reproduce this... Isn't that a
requirement?
BTW, perhaps you know: Are there no relea
If you’re not involving a higher level class like NSTextView or a medium level
one like CoreText, it sounds like you might be going all the way down to
CoreGraphics? If so, you might find your disparity between your system and your
users in things like retina choice for a particular display and
Thanks Rob, Makes sense although the issue is not consistent on Catalina (I
think this is something only a minority of my app users on Catalina are
experiencing - and I wasn't able to reproduce it). I saw this deprecation but
could not be sure if it means that it is always on or always off. I gu
Thanks!
I don't use CoreText or NSTextView. I pretty much ruled out RTL vs LTR issues
since this is showing up in documents containing either and both. I'm also
unable to imagine how some text drawing code could produce such artifacts as
splitting a subview in the middle.
(http://eyalredler.com/
On 14 Dec 2019, at 21:16, Redler Eyal via Cocoa-dev wrote:
I'm getting reports from users complaining about a strange display
issue on Catalina with my app.
[…]
The problem is that when with some documents, sometimes, when the user
scrolls down the document, some pages are not drawn or even pa
From
https://developer.apple.com/documentation/appkit/nsclipview/1532142-copiesonscroll?language=objc
copiesOnScroll
A Boolean value that indicates if the clip view copies rendered images while
scrolling.
Discussion
When the value of this property is YES, the clip view copies its existing
render
I see from your personal web site you know Hebrew. Is it possible the
affected/non-drawing pages contain some RTL text while those that don’t only
contain LTR? I have seen some bugs with RTL text within NSTextView where the
text was/wasn’t drawing in a similar manner. Do you operate at a CoreTex
Hi All,
I'm getting reports from users complaining about a strange display issue on
Catalina with my app.
My app is a word-processor (not based on the cocoa text system) whose main
display shows the pages of the document. Every page is a separate view and all
the pages are subviews of one big v
26 matches
Mail list logo
