Re: Adding and removing menu items causes memory usage to grow

That's it all right. Thank you for helping with your DELICIOUS BRAINS. On Thu, Oct 28, 2010 at 9:39 PM, Synthetiq Solutions wrote: > George Nachman wrote: >> In trying to figure this out, I downloaded the binary distribution of >> my program that someone else built (before I took it over). That >

Re: Get wrong tag value from NSPopupButtonCell

That's how I started... NSInteger testTag; [ [ olPopups cellAtRow:0 column:0 ] setTag: counter]; testTag = [ [ olPopups cellAtRow:0 column:0 ] tag]; Thanks -- Reinhard Am 30.10.2010 um 00:18 schrieb Jonathon Kuo: What's the point of doing this: NSPopUpButtonCell *testCell = [ [ [ NSPopUpBut

Re: Get wrong tag value from NSPopupButtonCell

That's how I started... NSInteger testTag; [ [ olPopups cellAtRow:0 column:0 ] setTag: counter]; NSInteger testTag = [ [ olPopups cellAtRow:0 column:0 ] tag]; Thanks -- Reinhard Am 30.10.2010 um 00:18 schrieb Jonathon Kuo: What's the point of doing this: NSPopUpButtonCell *testCell = [ [ [

Re: Get wrong tag value from NSPopupButtonCell

What's the point of doing this: > NSPopUpButtonCell *testCell = [ [ [ NSPopUpButtonCell alloc] init] > autorelease]; if you're doing this 2 lines later: > testCell = [ olPopups selectedCell]; At this point, I would check for testCell being nil. -Jon On Oct 29, 2010, at 2:02 PM, Rei

Re: Adding and removing menu items causes memory usage to grow

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Glad to be of assistance and let me say: hats off to you good sir - great pun, especially with Halloween in sight. (And apologies for the sender line on my last email; I have too many mail clients, and sometimes I can forget to, you know, fill in my o

Re: Get wrong tag value from NSPopupButtonCell

On Oct 29, 2010, at 14:02, Reinhard Segeler wrote: > Can't get the correct tag value in this way. What's wrong? > > NSPopUpButtonCell *testCell = [ [ [ NSPopUpButtonCell alloc] init] > autorelease]; > > // olPopups is an Outlet to an NSMatrix > [ olPopups selectCellAtRow

Get wrong tag value from NSPopupButtonCell

Hi, Can't get the correct tag value in this way. What's wrong? NSPopUpButtonCell *testCell = [ [ [ NSPopUpButtonCell alloc] init] autorelease]; // olPopups is an Outlet to an NSMatrix [ olPopups selectCellAtRow:0 column:0 ]; testCell = [ olPopups selectedCell

Re: Dictionary keyed by a few sparse integers?

Another way to do it is to use CFDictionaryRef and use the integers directly. NSInteger type; dateFormatterStorage = CFDictionaryCreateMutable( kCFAllocatorDefault, 0, 0, &kCFTypeDictionaryValueCallBacks ); formatter = (NSDateFormatter*)CFDictionaryGetValue( dateFormatterStorage, (void*)type);

Re: Localizing standard alternate menu items in unsupported languages

I thought I'd try one more time with this question. Does anyone have any ideas about localizing default alternate menu titles? Thanks, -Nick On Aug 4, 2010, at 5:49 PM, Nick Kocharhook wrote: > Hello, > > My application is localized in several languages which OS X does not support. > When the

Re: Dictionary keyed by a few sparse integers?

On 29/10/2010, at 11:12 PM, Andy Lee wrote: >> Having put it back to not using the static array, it's now working fine! >> Gremlins > > Happens all the time. Someone should really do a study on why putting code > back the way it was fixes bugs, especially after one has posted to cocoa-dev

Re: Dictionary keyed by a few sparse integers?

On Oct 29, 2010, at 7:52 AM, Graham Cox wrote: > > On 29/10/2010, at 10:44 PM, Roland King wrote: > >> It should work the way you've done it in a NSDictionary. >> >> Yes the numbers created by +numberWithUnsignedInteger: are distinct objects >> (normally, if I use low numbers they actually are

Re: Dictionary keyed by a few sparse integers?

On 29/10/2010, at 10:44 PM, Roland King wrote: > It should work the way you've done it in a NSDictionary. > > Yes the numbers created by +numberWithUnsignedInteger: are distinct objects > (normally, if I use low numbers they actually aren't, one of Cocoa's little > optimizations I guess), how

Re: Dictionary keyed by a few sparse integers?

It should work the way you've done it in a NSDictionary. Yes the numbers created by +numberWithUnsignedInteger: are distinct objects (normally, if I use low numbers they actually aren't, one of Cocoa's little optimizations I guess), however they compare as equal with isEqual: or isEqualToNumbe

Dictionary keyed by a few sparse integers?

I have a need to associate objects with an arbitrary unsigned integer, which can be pretty much anything. I figured a dictionary with NSNumbers as keys would be perfect, where the NSNumber is created using +numberWithUnsignedInteger: Trouble is, each time I create the number, it's a new object

SOAP results doesn't preserve whitespace

What can I do to preserve whitespace in SOAP calls? I invoke the SOAP call with WSMethodInvocationSetCallBack(soapCall, &callback, &context); WSMethodInvocationScheduleWithRunLoop(soapCall, [[NSRunLoop currentRunLoop] getCFRunLoop], (CFStringRef)NSDefaultRunLoopMode); and in the callback I do N