> On Feb 10, 2015, at 15:34, Clark S. Cox III wrote:
>
>>
>> On Feb 10, 2015, at 12:20, Quincey Morris
>> wrote:
>>
>> On Feb 10, 2015, at 11:23 , Jerry Krinock wrote:
>>>
>>> I’ve always wondered why, when you’re dragging a window around a non-Retina
>>> screen, the anti-aliasing doesn’t
> On Feb 10, 2015, at 12:20, Quincey Morris
> wrote:
>
> On Feb 10, 2015, at 11:23 , Jerry Krinock wrote:
>>
>> I’ve always wondered why, when you’re dragging a window around a non-Retina
>> screen, the anti-aliasing doesn’t show a “comb filter” kind of effect, with
>> different lines getti
On Feb 10, 2015, at 11:23 , Jerry Krinock wrote:
>
> I’ve always wondered why, when you’re dragging a window around a non-Retina
> screen, the anti-aliasing doesn’t show a “comb filter” kind of effect, with
> different lines getting fuzzy and sharp as they are dragged on and off their
> pixels
> On 2015 Feb 10, at 05:36, Charles Jenkins wrote:
>
> This may explain why my purchase of a program that outputs code for vector
> images resulted in disappointment.
Counterintuitive at first, but, yes :))
I’ve always wondered why, when you’re dragging a window around a non-Retina
screen, t
This may explain why my purchase of a program that outputs code for vector
images resulted in disappointment. I don't have a retina display, so I bought a
program to make graphics code that would look good at any size/resolution in my
Mac app, even for displays I have no experience with. What I
> On 2015 Feb 09, at 13:28, Uli Kusterer wrote:
>
> The image didn’t make it to the list,
Oh, well. I recall being able to send pictures in the past, as long as the
message size was < 25K. Maybe this is a new feature :(
> Here’s an article (with pictures!) about this issue I wrote ages ago:
> On 10 Feb 2015, at 9:16 am, Quincey Morris
> wrote:
>
> FWIW (and while we wait for Jerry to tell us what was in the missing screen
> shot), I’ve abandoned the “offset it by 0.5 points” approach, in the last
> year or two. I don’t necessarily have an unarguable justification, but my
> reas
FWIW (and while we wait for Jerry to tell us what was in the missing screen
shot), I’ve abandoned the “offset it by 0.5 points” approach, in the last year
or two. I don’t necessarily have an unarguable justification, but my reasoning
runs along these lines:
1. For general drawing, when the thin
> On Feb 9, 2015, at 1:18 PM, Jerry Krinock wrote:
>
> Is there a way to draw thin lines in code, and get good results on non-Retina
> displays? What should I read to learn how?
(The listserv strips image attachments, so we can’t see the pictures.)
The typical problem drawing thin horizontal
On 09 Feb 2015, at 22:18, Jerry Krinock wrote:
> I may need to break down and learn something about graphics and drawing.
>
> I use NSBezierPath in a -[NSView drawRect:] to do an engineering-style
> drawing. Here is a tiny arrowhead pointing to a vertical “dimension line”:
>
> Not very nice.
I may need to break down and learn something about graphics and drawing.
I use NSBezierPath in a -[NSView drawRect:] to do an engineering-style drawing.
Here is a tiny arrowhead pointing to a vertical “dimension line”:
Not very nice. If instead I draw this in a graphics program, with antiali
11 matches
Mail list logo
