i’m getting an EXC_BAD_ACCESS crash in my app when it runs under lion 10.7.4.
the app runs fine on 10.6.8. the app is built with xCode 3.2.6 on lion, using
the 10.6 sdk and targeting 10.6.
this is 100% repeatable. when the user executes a menu item, i execute a bunch
of code that includes seve
using a timer works just fine. and i don’t believe any “debouncing” is
necessary as the timer can’t fire if i am already in the process of resizing.
thanx ken and quincey,
ken
On Jun 23, 2011, at 3:57 PM, Ken Victor wrote:
> empirically, it appears that the event tracking loop for win
believe it would
be “messier” than quincey’s "low tech" solution, which can be encapsulated in
my subclass. i will now give this a try and report back.
thanx quincey,
ken
On Jun 23, 2011, at 3:21 PM, Quincey Morris wrote:
> On Jun 23, 2011, at 14:55, Ken Victor wrote:
>
>
On Jun 23, 2011, at 2:40 PM, Ken Thomases wrote:
> Hi Ken,
>
> On Jun 23, 2011, at 4:12 PM, Ken Victor wrote:
>
>> so… anyone have any other ideas as to how to get called for a modifier key
>> change will in the midst of a live resize?
>
> I'm a bit confu
e is a flag you can set
> (explained here: http://tinyurl.com/6jky52c) to receive notifications for
> this sort of thing
>
>
> On Jun 22, 2011, at 5:21 PM, Ken Victor wrote:
>
>> i‚ve got a subclass of NSWindow (MagneticWindow) that provides:
>> - (NSSize) windowWillResiz
i’ve got a subclass of NSWindow (MagneticWindow) that provides:
- (NSSize) windowWillResize: (NSWindow*) sender toSize: (NSSize)
frameSize;
i use this to provide constrained live resizing of the window, i.e., if the
shift key is down, the window will only resize in the horizontal or verti
scott,
thanx. altho some of those specific APIs are deprecated, their “modern”
equivalents seem to do the job.
thanx,
ken
On May 24, 2011, at 5:36 AM, Scott Ribe wrote:
> On May 23, 2011, at 4:23 PM, Ken Victor wrote:
>
>> ...can anyone tell me what additional information i need
in my app, i save and restore (via archiving and unarchiving) the NSPrintInfo
for each report my app can print. this has worked fine for me until i just got
a new epson printer that can print double-sided. the saved/restored NSPrintInfo
is apparently not saving/restoring sufficient information t
of that, find out why they are throwing NSErrors as exceptions.
>
> Chris Kane
> Cocoa Framework, Apple
>
>
> On May 21, 2011, at 12:34 PM, Ken Victor wrote:
>
>> nick,
>> thanx for the reply.
>>
>> here is a copy of the top portion of the stack trace
, at 10:40 PM, Nick Zitzmann wrote:
>
> On May 20, 2011, at 4:41 PM, Ken Victor wrote:
>
>> the following problem only occurs when i run my app in 64-bit mode; i.e., it
>> does not happen when i run in 32-bit mode. my environment is snow leopard
>> 10.6.7 running on a
the following problem only occurs when i run my app in 64-bit mode; i.e., it
does not happen when i run in 32-bit mode. my environment is snow leopard
10.6.7 running on a mac pro.
when i call:
-[NSPrintPanel
beginSheetWithPrintInfo:modalForWindow:delegate:didEndSelector:contextInfo:]
i
At Wed, 09 Apr 2008 10:43:34 -0700, Corbin Dunn <[EMAIL PROTECTED]>:
The question was "what advantage is there for using NSInteger/
NSUInteger". The answer is 64-bit transition of your Cocoa apps.
-corbin
this "raises" a question i've been meaning to ask for a while:
can anyone speculate as t
At 1:08 PM -0700 3/31/08, [EMAIL PROTECTED] wrote:
Date: Mon, 31 Mar 2008 12:20:41 -0700
From: Mike <[EMAIL PROTECTED]>
Subject: Re: Main Thread UI and Detached Thread
To: Apple Cocoa List
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I have two met
13 matches
Mail list logo
