On May 3, 2012, at 19:38 , Graham Cox wrote:
> You probably should do this as your last line:
>
> [self performSelector: withObject:nil afterDelay:[NSEvent
> keyRepeatInterval] + 0.1];
>
> because the key repeat rate is set by the user in the "Keyboard" system
> preferences and can change.
I
On 3 May 2012, at 7:19 PM, Jerry Krinock wrote:
> I've seen the nilling of attributes happen before, upon re-inserting a
> deleted object [1]. This behavior is obviously related, but different. If
> anyone can think of a good reason for this behavior, it would be interesting
> to read.
By th
El may 4, 2012, a las 3:19 a.m., Quincey Morris escribió:
> On May 3, 2012, at 19:38 , Graham Cox wrote:
>
>> You probably should do this as your last line:
>>
>> [self performSelector: withObject:nil afterDelay:[NSEvent
>> keyRepeatInterval] + 0.1];
>>
>> because the key repeat rate is set b
On May 4, 2012, at 08:25 , Marc Respass wrote:
> When I set the delay to zero, there is no delay. My selector is called
> immediately as if I didn't change anything.
Not exactly. Consider what happens when you mash the arrow key. Thus, there
might be multiple (normal) key events queued. The se
> On May 3, 2012, at 6:11 PM, Ben Kennedy wrote:
>
>> Separate from the above, I also have a new performance problem. The loop in
>> which I do my cascading updates executes inordinately slowly; simply
>> assigning new values for two properties takes about 0.45 seconds when
>> iterating a data
El may 4, 2012, a las 1:02 p.m., Quincey Morris escribió:
> On May 4, 2012, at 08:25 , Marc Respass wrote:
>
>> When I set the delay to zero, there is no delay. My selector is called
>> immediately as if I didn't change anything.
>
>
> Not exactly. Consider what happens when you mash the arro
On May 4, 2012, at 12:39 , Marc Respass wrote:
> This is working great. What do you think?
"Working great" sounds great!
If you want to go the extra mile for your users, you could try something like
this:
CMTableView *tableview = [notification object];
NSTimeInterval delayInterval
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
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
On 2012-05-04, at 10:22 PM, Charlie Dickman wrote:
> (I'm staying in Snow Leopard using Xcode 3; I hate Lion and it's move away
> from the mouse.
I don't understand. I only use a mouse on my Mac Pro. No Tablet. (I don't do
iDevice apps)
So I don't see any of the bouncy castle scroll things that s
On May 4, 2012, at 8:19 PM, Peter Teeson wrote:
> - (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 havin
> My custom NSView in a NSPanel shows some information depends on panel's
> position to the main window. I want to update it during dragging the panel.
> I try [self setNeedsDisplay:YES] in mouseDragged: delegate, drawRect: called
> many times during dragging, but it will not appear on screen u
12 matches
Mail list logo
