Re: Strange issue in stroking a bezier path
Re: Strange issue in stroking a bezier path
- Subject: Re: Strange issue in stroking a bezier path
- From: Charlie Dickman <email@hidden>
- Date: Fri, 04 May 2012 22:22:19 -0400
I am having a similar problem but not with an Apple display and at a resolution of 1920 x 1080 and not with stroking a path. My problem occurs with textfield rendering when the fields abut one another. Sometimes the edges do not line up even when they are configured to do so in IB.
(I'm staying in Snow Leopard using Xcode 3; I hate Lion and it's move away from the mouse. I suffer from familial tremors and have a tough enough time with the mouse and find the gesture pad impossible. I will stay on Snow Leopard until I am forced to a new machine. Needless to say I program as a hobby - just for my own enjoyment)
At any rate I believe the problem is with the graphics chip and its ability to consistently activate pixels in close proximity when not drawn with a single stroke. I know of no solution except to adjust the placement of your drawn objects to minimize the effect.
Changing monitors or resolution, I think, will not address the problem. A different, perhaps "better" graphics card might.
On May 4, 2012, at 9:19 PM, Peter Teeson wrote:
> Xcode 4.3.2, Lion 10.7.3,
> Apple 30" Cinema Display, Samsung SyncMaster 950p
>
> Consider the following simple drawRect to demonstrate the issue
>
> - (void)drawRect:(NSRect)dirtyRect
> {
> // Drawing code here.
> NSRect bounds = [self bounds];
> NSBezierPath *path = [NSBezierPath bezierPathWithRect:bounds];
> [path stroke];
> }
>
> In the specific case of the Cinema Display having a resolution setting of 1280 x 800
> the rectangle is not fully drawn every time. The top and right edges are missing.
> But sometimes they do draw. It seems quite arbitrary.
>
> I have tested this with all other resolutions on the Cinema Display under both standard
> and HiDPI and also on the Samsung CRT. They all work just fine. Even the Samsung at 1280 x 800.
>
> (I have tried things such as NSIntegralRect but nothing works except to change the resolution)
>
> Why would this occur and only at that resolution and only on the Cinema Display?
>
> Any ideas for tracking it down, or working around it, gratefully received.
>
> TIA and respect….
>
> Peter
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
Charlie Dickman
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden