Hi Jens,
Thanks for your help. I've been trying to get the option 1 approach to work,
but I don't know what I'm meant to do with my NSValue. I can't find how to
convert it to an NSData type.
Thanks again,
Billy.
On 26 Apr 2010, at 15:46, Jens Alfke wrote:
>
> On Apr 26, 2010, at 5:58 AM, Bi
On 27/04/2010, at 5:05 PM, Billy Flatman wrote:
> Hi Jens,
>
> Thanks for your help. I've been trying to get the option 1 approach to work,
> but I don't know what I'm meant to do with my NSValue. I can't find how to
> convert it to an NSData type.
NSData* data = [NSKeyedArchiver archivedDat
Am 26.04.2010 um 21:17 schrieb John Joyce:
>> For your personal pleasure: The iPhone is a MTP device, so you can use
>> ImageCapture to copy "images" from / to your phone.
>>
>> If you don't want Stanza-like trouble and stay in the AppStore: There is
>> no official way.
>>
>> HTH,
>> T
> Um, actually the menu bar is on the primary display. That's
> the definition of the primary display
> -- it's the one with the menu bar. Did you perhaps mean the
> built-in display?
I was speaking from memory. My recollection is that after I
moved the menu bar the primary display, as repor
> are you saying there is a way to set the min, max and value on
> an
> nsscroller? sorry, not clear on that
Why do you need min and max anyway? The current position is set
as / returned as a float (or a double) between 0 and 1. That
represents the range of the scroller. Interpret it however
> So I guess the compiler treats the *first* declaration of a
> method
> name-and-signature that it encounters as the "real" one.
>
> Now, that's okay ...
Not really. Without the warning flag it means that the type
checking you would hope to get from the compiler is subverted.
In your example
Hi,
I am trying to open a movie using the NewMovieFromDataRef api. But if the
movie URL is not found, I get a crash.
This is happening on OSX10.6.3. QT version 7.6.3. Following is the test app
that I tried. Is there any way/ api to get around this crash ?.
#include
#include
#include
int mai
you are right, that will work, thanks!
On Tue, Apr 27, 2010 at 2:57 AM, Paul Sanders wrote:
> > are you saying there is a way to set the min, max and value on
> > an
> > nsscroller? sorry, not clear on that
>
> Why do you need min and max anyway? The current position is set
> as / returned a
hi all,
i like to create some menus, set them as the main menu bar, then maybe
delete them, and create some more menus, use them, etc.
but i can't find any way to do this with cocoa
here is the problem
when you add a submenu (setSubMenu:forItem) the retain count on the submenu
goes up by one
b
> Don't why it's not working for you. My LSUIElement app similarly has no menu
> bar or dock icon, but it's various ancillory windows (About plain vanilla
> version, Preferences) respond to key board short cuts which are set in the
> main menu nib. I have done no special hacks to achieve this,
On Apr 27, 2010, at 7:46 AM, Bill Appleton wrote:
> i like to create some menus, set them as the main menu bar, then maybe
> delete them, and create some more menus, use them, etc.
>
> but i can't find any way to do this with cocoa
>
> here is the problem
>
> when you add a submenu (setSubMenu:
Bill, you need to learn about the concept of object ownership within Cocoa.
Ownership is the model for memory management, retain count merely an
implementation detail which can tell you nothing useful.
Menus own their submenus, so if you delete a menu with submenus, you don't need
to also delet
On 27/04/2010, at 11:49 PM, Michael Dippery wrote:
Don't why it's not working for you. My LSUIElement app similarly
has no menu bar or dock icon, but it's various ancillory windows
(About plain vanilla version, Preferences) respond to key board
short cuts which are set in the main menu ni
On 27/04/2010, at 11:49 PM, Michael Dippery wrote:
Don't why it's not working for you. My LSUIElement app similarly
has no menu bar or dock icon, but it's various ancillory windows
(About plain vanilla version, Preferences) respond to key board
short cuts which are set in the main menu ni
On 27 Apr 2010, at 7:12 AM, varaha murthy wrote:
> I am trying to open a movie using the NewMovieFromDataRef api. But if the
> movie URL is not found, I get a crash.
> This is happening on OSX10.6.3. QT version 7.6.3. Following is the test app
> that I tried. Is there any way/ api to get around t
On Tue, Apr 27, 2010 at 5:53 AM, Paul Sanders
wrote:
>> Um, actually the menu bar is on the primary display. That's
>> the definition of the primary display
>> -- it's the one with the menu bar. Did you perhaps mean the
>> built-in display?
>
> I was speaking from memory. My recollection is tha
hi all,
i have read the memory rules a few times now, so does this sound right?
1) after i append an item i have created to a menu i have created, and i
don't want to own the menu item any more, i should release the item so that
the menu owns it
2) when i add a submenu i have created to a menu i
On Apr 27, 2010, at 4:48 PM, Michael Ash wrote:
On Tue, Apr 27, 2010 at 5:53 AM, Paul Sanders
wrote:
Um, actually the menu bar is on the primary display. That's
the definition of the primary display
-- it's the one with the menu bar. Did you perhaps mean the
built-in display?
I was speaki
Hello,
I have a model object that represents a single node in a tree (it can be used
in an NSOutlineView for instance). As such, it has a "children" NSMutableArray
iVar which can store other objects of the same class, which in turn may have
their own children.
E.g:
@interface MyNode : NSObjec
Generally, you make MyNode also hold a weak reference to its parent node. (see
NSTreeNode/NSView for example)
Then, when testing a node, can quickly recurse up the tree looking for a
desired ancestor.
On 27 Apr 2010, at 16:33, Keith Blount wrote:
> Hello,
>
> I have a model object that repres
On or about 4/26/10 1:22 PM, thus spake "Greg Parker" :
> The compiler warns more aggressively for mismatches that do affect the call
> site's code. Those are more likely to be actual bugs, rather than correct but
> loosely-typed code. For example, if you change your example's parameter types
> to
On 27 Apr 2010, at 10:28 AM, Bill Appleton wrote:
> 1) after i append an item i have created to a menu i have created, and i
> don't want to own the menu item any more, i should release the item so that
> the menu owns it
>
> 2) when i add a submenu i have created to a menu i have created, and i
Many thanks for the reply, much appreciated. That makes sense - the only (or
rather difficulty) is ensuring the node always has an up-to-date reference to
its parent given the number of scenarios in which it could change (for
instance, if a node is copied etc).
Thanks again,
Keith
___
Hi Matt
> I see now, however, *why* the compiler is silent: it's because it weren't,
> it would be too chatty. I turned on -Wselector and got 114 warnings... :)
You too eh? Wow, was that a surprise - my tutorial project gave me 3679!!!
Joanna
--
Joanna Carter
Carter Consulting
_
On Apr 27, 2010, at 9:28 AM, Bill Appleton wrote:
> after i append an item i have created to a menu i have created, and i
> don't want to own the menu item any more, i should release the item so that
> the menu owns it
Probably not, but it depends on how you created it. If you created it with a
On Apr 27, 2010, at 09:39, Keith Blount wrote:
> Many thanks for the reply, much appreciated. That makes sense - the only (or
> rather difficulty) is ensuring the node always has an up-to-date reference to
> its parent given the number of scenarios in which it could change (for
> instance, if a
Le 26 avr. 2010 à 23:35, Bill Appleton a écrit :
> hi all,
>
> when my windows are first shown there is no drawing inside, they are white
>
> but when i slowly move the mouse over to the close box and the close box
> responds to the mouse hover suddenly they draw their content properly
>
> does
Well that's pretty easy if you're writing proper accessor methods like:
- (NSArray *)children;
- (void)insertObject:(MyNode *)node inChildrenAtIndex:(NSUInteger)index;
- (void)removeObjectFromChildrenAtIndex:(NSUInteger)index;
Just call -setParent: or similar in the implementation.
On 27 Apr 201
Quincey,
> Notwithstanding the discussion in this thread so far, I don't quite
> understand why you wouldn't do this the easy way: create a NSManagedObject in
> your managed context, and delete it when you're done with it.
>
> The documentation explicitly describes the managed context as a "scr
Hi Vincent
> There is a simple reason: the objects in the Managed object context get
> "represented" on a third window, whose contents are drawn from an Entity mode
> NSArrayController that prepares its contents automatically. If I add my
> temporary object to the MOC, it automatically gets fet
Hi,
I have a UIScrollView that can contain a variable number of other UIViews
(UILabels, UIImageViews, etc), but I'm confused as to how to manage the
UIScrollView contentSize given the variability in the number of views it will
contain. I'd like to use IB to create my view, but is this
Indeed, I believe that's my problem - currently when I add objects to my
children array I do things such as [[myNode children] addObject:newNode],
meaning I have nowhere to catch it. I'll update my code to add some accessors
as you suggest, and change my - (NSMutableArray *)children accessor to
On Apr 27, 2010, at 8:28 AM, Bill Appleton wrote:
1) after i append an item i have created to a menu i have created,
and i
don't want to own the menu item any more, i should release the item
so that
the menu owns it
Don't think of who "owns" an object. The memory model doesn't work
that
Hi all,
I have the question whether it is possible to develop iPhone Apps without the
use of the Xcode IDE. For example you could use the classic unix development
tools manually, instead of using them full automatic by pressing the "build and
run" button.
It is just curiosity which brings me to
As far as building from the command line is concerned, you can build your
project without the IDE via the xcodebuild. There's also a similar tool for
running Package Maker.
These are useful for automated builds. If you're looking at using Makefiles,
configure and similar tools, I wouldn't bot
Le 27 avr. 2010 à 20:42, Jens Alfke a écrit :
> What you "own" are references. If you call a method that creates a reference,
> like +alloc, -retain or -copy, then you now own a reference to that object.
> For as long as you own that reference, the object will stay around. When you
> don't need
> Sorry, didn't read your email properly. If you've already created a menu in
> your MainMenu nib and it's not working, perhaps you haven't actually made the
> connection in the nib. If that's the case, then you just need to
> Control-drag from your Close menu item to the First Responder in th
On Apr 27, 2010, at 11:58 AM, vincent habchi wrote:
Yet, at the same time, you may want the dealloc: method to trigger
some events. For example, if you have a CALayer that holds various
sublayers, and that CALayer goes away, you may want all the
sublayers to go away at the same time. Yet,
On Apr 27, 2010, at 12:58 PM, vincent habchi wrote:
> Yet, at the same time, you may want the dealloc: method to trigger some
> events. For example, if you have a CALayer that holds various sublayers, and
> that CALayer goes away, you may want all the sublayers to go away at the same
> time. Y
Le 27 avr. 2010 à 21:21, Scott Ribe a écrit :
>> By the way, how are exactly multiple calls to [object autorelease] handled
>> by the pool? Does this give rise to as many calls to release: as they are
>> autorelease references stored, or does the pool directly adjust the retain
>> count?
>
> W
On 27 Apr 2010, at 21:38, vincent habchi wrote:
Because earlier in this afternoon I decided to trace the retain/
release messages sent to an object by overriding the respective
methods and have them write the retain count before calling super
methods. I registered most curious behaviors, fo
Le 27 avr. 2010 à 21:17, Jens Alfke a écrit :
> Remember that in a ref-counted (or GC'd) system you can't force an object to
> deallocate (even 'self'.) The deallocation is under control of all the other
> objects that have references, and the runtime itself. So you should never put
> any code
On Apr 27, 2010, at 3:38 PM, vincent habchi wrote:
> Le 27 avr. 2010 à 21:21, Scott Ribe a écrit :
>
>>> By the way, how are exactly multiple calls to [object autorelease] handled
>>> by the pool? Does this give rise to as many calls to release: as they are
>>> autorelease references stored, o
On Apr 27, 2010, at 12:38 PM, vincent habchi wrote:
I registered most curious behaviors, for example objects released
while the last time their retain count was printed it was equal to
2. No 1, no 0. That's why I asked, just to know if autorelease does
not short-circuit the traditional rel
Le 27 avr. 2010 à 21:57, Jens Alfke a écrit :
>> I registered most curious behaviors, for example objects released while the
>> last time their retain count was printed it was equal to 2. No 1, no 0.
>> That's why I asked, just to know if autorelease does not short-circuit the
>> traditional re
On Apr 27, 2010, at 1:38 PM, vincent habchi wrote:
> Because earlier in this afternoon I decided to trace the retain/release
> messages sent to an object by overriding the respective methods and have them
> write the retain count before calling super methods. I registered most
> curious behavi
On Apr 27, 2010, at 1:57 PM, Jens Alfke wrote:
> That sounds like an optimization in the runtime to avoid a couple of
> message-sends. You shouldn't override -retain or -release or make assumptions
> about how many times they're called; those are implementation details.
Actually, you can overri
On 27.04.2010, at 00:10, Bill Appleton wrote:
> i added flush window to the drawRect method -- no help
>
> it IS calling draw rect right before the window is shown & then you see it
> --- all white
Are you using multiple threads? I got effects like that when I was screwing up
AppKit state by me
hi vince,
my windows are NSBackingStoreBuffered
is that what you mean by background property? i am just using a subclassed
NSView & a CGContext for drawing
this is a very generic use of cocoa windows, i can't figure out what is
wrong
i noticed that if i show/hide a window it will stop working a
no threads
i have been disabling things to the point that it is mainly just the windows
i noticed that if i show/hide a window it will stop working altogether --
can't resize it, etc.
thanks,
bill
On Tue, Apr 27, 2010 at 1:34 PM, Uli Kusterer
wrote:
> On 27.04.2010, at 00:10, Bill Appleto
On 27.04.2010, at 00:10, Bill Appleton wrote:
> i added flush window to the drawRect method -- no help
>
> it IS calling draw rect right before the window is shown & then you see it
> --- all white
Oh, also: if your code throws exceptions, those can abort important processes
like redraws, you m
>> Over the years, I think that looking at the retain count is the #1 cause
of hairpulling on this list.
it's too bad this is unreliable
an object should be able to return this info
and it isn't simple, it gets convoluted in process
if i add a submenu to an item then it is retained by the menu
On Tue, Apr 27, 2010 at 1:49 PM, Bill Appleton
wrote:
>>> Over the years, I think that looking at the retain count is the #1 cause
> of hairpulling on this list.
>
>
> it's too bad this is unreliable
>
> an object should be able to return this info
Why? It serves you no purpose. Once you hand an
On Apr 27, 2010, at 1:49 PM, Bill Appleton wrote:
> it's too bad this is unreliable
>
> an object should be able to return this info
An object does return this info, the problem is that the # is a meaningless
internal implementation detail of the Cocoa frameworks.
For example, if you create a
On 27 Apr 2010, at 12:58 PM, Bob Barnes wrote:
> I have a UIScrollView that can contain a variable number of other UIViews
> (UILabels, UIImageViews, etc), but I'm confused as to how to manage the
> UIScrollView contentSize given the variability in the number of views it will
> contain. I'd
On Tue, Apr 27, 2010 at 1:49 PM, Bill Appleton
wrote:
>>> Over the years, I think that looking at the retain count is the #1 cause
> of hairpulling on this list.
>
>
> it's too bad this is unreliable
>
> an object should be able to return this info
>
> and it isn't simple, it gets convoluted in pr
On 04/27/2010 1:58 PM, "Bill Bumgarner" wrote:
> Frankly, the -retainCount method should be deprecated and, eventually,
> removed.
I wouldn't go THAT far; after all, when you're tracking a memory leak,
checking your influence on the retain count is important to your
investigation. Hopefully tha
On Apr 27, 2010, at 2:09 PM, Gary L. Wade wrote:
> On 04/27/2010 1:58 PM, "Bill Bumgarner" wrote:
>
>> Frankly, the -retainCount method should be deprecated and, eventually,
>> removed.
>
> I wouldn't go THAT far; after all, when you're tracking a memory leak,
> checking your influence on the
On 04/27/2010 2:12 PM, "Bill Bumgarner" wrote:
>
> On Apr 27, 2010, at 2:09 PM, Gary L. Wade wrote:
>
>> On 04/27/2010 1:58 PM, "Bill Bumgarner" wrote:
>>
>>> Frankly, the -retainCount method should be deprecated and, eventually,
>>> removed.
>>
>> I wouldn't go THAT far; after all, when you
On Tue, Apr 27, 2010 at 11:12 PM, Bill Bumgarner wrote:
>
> The combination of leaks, zombies, heap, and malloc stack logging are much
> *much* more powerful and effective than trying to debug a leak, over-retain
> or under-retain with -retainCount.
>
> b.bum
Hear, hear. I haven't called retai
On 27.04.2010, at 17:28, Bill Appleton wrote:
> 1) after i append an item i have created to a menu i have created, and i
> don't want to own the menu item any more, i should release the item so that
> the menu owns it
Depends on how you create the item. If you create them in a way that you have
On Tue, Apr 27, 2010 at 2:22 PM, Gary L. Wade
wrote:
> Yes, but how would you use those to determine why an Apple framework now
> chooses to retain a delegate (I'm referring to one particular one I
> discovered), thereby causing a retain cycle? It's not a memory leak in the
> sense that Instrume
ObjectAlloc instrument is your friend. Configure it to record retains
and releases. Much more accurate, much easier to understand what's
going on.
On Tuesday, April 27, 2010, Gary L. Wade wrote:
> On 04/27/2010 2:12 PM, "Bill Bumgarner" wrote:
>
>>
>> On Apr 27, 2010, at 2:09 PM, Gary L. Wade wr
On 04/27/2010 2:27 PM, "Shawn Erickson" wrote:
> On Tue, Apr 27, 2010 at 2:22 PM, Gary L. Wade
> wrote:
>
>> Yes, but how would you use those to determine why an Apple framework now
>> chooses to retain a delegate (I'm referring to one particular one I
>> discovered), thereby causing a retain c
On 27.04.2010, at 11:53, Paul Sanders wrote:
> I was speaking from memory. My recollection is that after I
> moved the menu bar the primary display, as reported by NSScreen,
> did not change. But it was a while ago so I could be wrong and
> the docs agree with you. This implies that the prima
On Apr 27, 2010, at 2:49 PM, Bill Appleton wrote:
> and it isn't simple, it gets convoluted in process
It is simple. It is very, very simple. You're over-thinking it.
You are responsible for your references to the submenu. The menu is responsible
for managing its references to its submenus. You
Actually, I think I was just plain wrong but what I meant was
[[NSScreen screens] objectAtIndex: 0].
Paul Sanders.
- Original Message -
From: "Uli Kusterer"
To: "Paul Sanders"
Cc: "Cocoa-Dev (Apple)"
Sent: Tuesday, April 27, 2010 10:34 PM
Subject: Re: NSApplicationMain question
On
On Tue, Apr 27, 2010 at 2:32 PM, Gary L. Wade
wrote:
> On 04/27/2010 2:27 PM, "Shawn Erickson" wrote:
>
>> On Tue, Apr 27, 2010 at 2:22 PM, Gary L. Wade
>> wrote:
>>
>>> Yes, but how would you use those to determine why an Apple framework now
>>> chooses to retain a delegate (I'm referring to on
On Tue, Apr 27, 2010 at 2:40 PM, Paul Sanders
wrote:
> Actually, I think I was just plain wrong but what I meant was
> [[NSScreen screens] objectAtIndex: 0].
At one point in time I recall NSScreen not reliably updating its
information on mode switches of displays. I cannot recall the
specifics bu
On 04/27/2010 2:46 PM, "Shawn Erickson" wrote:
[ removed lots of bad assumptions by Shawn ]
Shawn, it is apparent your understanding of reality is flawed when it comes
to my efforts to track down the bug in Apple's code, so please go away.
This thread is over.
_
On 27.04.2010, at 23:22, Gary L. Wade wrote:
> Calling -retainCount
> immediately before and after the -setDelegate call is pretty much the only
> way.
Nope. It'll only lead to pain and suffering. And false positives. What if
setDelegate was implemented thus:
-(void) setDelegate: (id)dele
{
On Tue, Apr 27, 2010 at 2:56 PM, Gary L. Wade
wrote:
> On 04/27/2010 2:46 PM, "Shawn Erickson" wrote:
>
> [ removed lots of bad assumptions by Shawn ]
>
> Shawn, it is apparent your understanding of reality is flawed when it comes
> to my efforts to track down the bug in Apple's code, so please g
Can you guys maybe agree that you disagree and put it to rest?
-Laurent.
--
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin
http://nemesys.dyndns.org
Logiciels Nemesys Software
laurent.daude...@gmail.com
Photo Gallery
On Apr 27, 2010, at 3:05 PM, Uli Kusterer wrote:
> On 27.04.2010, at 23:22, Gary L. Wade wrote:
>> Calling -retainCount
>> immediately before and after the -setDelegate call is pretty much the only
>> way.
>
> Nope. It'll only lead to pain and suffering. And false positives. What if
> setDelegat
On 27.04.2010, at 22:49, Bill Appleton wrote:
> an object should be able to return this info
>
> and it isn't simple, it gets convoluted in process
Let me exaggerate for a paragraph to hopefully bring across a point:
The main objective of Cocoa's design is not to produce the most efficient cod
On Tue, Apr 27, 2010 at 3:22 PM, Uli Kusterer
wrote:
>For example, bindings were notorious for causing retain circles when you bound
>to File's Owner in a NIB, and that was fixed in 10.5, IIRC.
Fairly sure it is still an issue unless you are using a
NSWindowController subclass as the File's Own
this problem must be because i am using core graphics
i painted a big red rectangle in drawRect and then went on and called my
core graphics code
the big red rectangle comes up every time
but only after resizing do i see the stuff i draw with core graphics
so i am getting the draw rect events b
On 28/04/2010, at 5:06 AM, Michael Dippery wrote:
Sorry, didn't read your email properly. If you've already created
a menu in your MainMenu nib and it's not working, perhaps you
haven't actually made the connection in the nib. If that's the
case, then you just need to Control-drag from y
Sorry, I missed this reply earlier. Unfortunately I can't use NSTreeNode
because I'm tied to providing support for Tiger for the foreseeable future, and
NSTreeNode is Leopard and above only. Thus I'm not able to use bindings for my
outline views (I remember spending weeks trying to bend NSTreeCo
Bill Appleton wrote:
3) when i set the menus i have created for NSApp using setMainMenu
then...
what? who owns them? how do i set more menus for NSApp? how do i
get NSApp
to release the current set?
You are not responsible for NSApplication's retention or release of
menus. It alone is
On Tue, Apr 27, 2010 at 11:29 AM, Thomas Clement wrote:
>
> On Apr 27, 2010, at 4:48 PM, Michael Ash wrote:
>
>> On Tue, Apr 27, 2010 at 5:53 AM, Paul Sanders
>> wrote:
Um, actually the menu bar is on the primary display. That's
the definition of the primary display
-- it's t
On Tue, Apr 27, 2010 at 2:05 PM, Keith Blount wrote:
> Indeed, I believe that's my problem - currently when I add objects to my
> children array I do things such as [[myNode children] addObject:newNode],
> meaning I have nowhere to catch it. I'll update my code to add some accessors
> as you su
On Apr 27, 2010, at 3:49 PM, Bill Appleton wrote:
> if i add a submenu to an item then it is retained by the menu
>
> but then if i then set that submenu to nil is it still retained?
>
> if retained count was accurate you could test it on final release, etc
Well, the direct answer is no, since
Hello,
is there a way to get to the finder label of a file from Cocoa? I'd like to be
able to get & set them.
Thanks,
Rainer___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
C
hi all,
this is helping
one thing you app migrators out there need to remember is that cocoa draws
the window before it is visible
so there is a timing issue
i will check these issues tomorrow
thanks,
bill
On Tue, Apr 27, 2010 at 4:24 PM, Jesper Storm Bache wrote:
> I though I saw that
Rainer Standke (li...@standke.com) on 2010-04-27 20:14 said:
>Hello,
>
>is there a way to get to the finder label of a file from Cocoa? I'd like
>to be able to get & set them.
In 10.6 you can use NSWorkspace's:
- (NSArray *)fileLabels
- (NSArray *)fileLabelColors
On older OSes, you'll need to u
Hi, I been trying to figure out how to get the Bezier path for a character
in different fonts,
but can't quiet figure out why things dont work in some fonts.
Some (many) fonts do not rednder the right path for the glyph,
a 'W' in in "Arial Black" for example is fine (looks like W), but in
"Arial H
Hi all, got a bit of an architectural issue that I'm having a problem solving,
so I thought I'd throw it out there and see if anyone can offer a way forward.
I have a tree of objects of various kinds. Each node in the tree keeps a weak
reference to its parent node. These references are nilled ou
On Apr 27, 2010, at 6:45 PM, danc...@rebelbase.com wrote:
Some (many) fonts do not rednder the right path for the glyph,
a 'W' in in "Arial Black" for example is fine (looks like W), but in
"Arial Hebrew" it looks like a J
in some other fonts it just looks like a square box (as it is
missing)
On Apr 27, 2010, at 6:55 PM, Graham Cox wrote:
Here's the problem: Any tasks on the undo stack that refer to a
particular target must be removed when that target is dealloced.
I don't know your app, but this sounds backwards to me. Don't tasks/
nodes need to be kept around for as long as an
On 28/04/2010, at 12:00 PM, Jens Alfke wrote:
>
> On Apr 27, 2010, at 6:55 PM, Graham Cox wrote:
>
>> Here's the problem: Any tasks on the undo stack that refer to a particular
>> target must be removed when that target is dealloced.
>
> I don't know your app, but this sounds backwards to me.
Newbie question: Consider an array of dictionary objects, all of the same
class. One of the ivars of that class is an NSString which is unique for each
instance. Does there already exist a method that will identify the one
dictionary object that has a given value of that ivar, without me having
On 28/04/2010, at 12:37 PM, Lynn Barton wrote:
> Newbie question: Consider an array of dictionary objects, all of the same
> class. One of the ivars of that class is an NSString which is unique for each
> instance. Does there already exist a method that will identify the one
> dictionary objec
Graham Cox wrote:
On 28/04/2010, at 12:37 PM, Lynn Barton wrote:
Newbie question: Consider an array of dictionary objects, all of the same
class. One of the ivars of that class is an NSString which is unique for each
instance. Does there already exist a method that will identify the one
dic
On Apr 27, 2010, at 8:06 PM, Roland King wrote:
> Graham Cox wrote:
>> On 28/04/2010, at 12:37 PM, Lynn Barton wrote:
>>> Newbie question: Consider an array of dictionary objects, all of the same
>>> class. One of the ivars of that class is an NSString which is unique for
>>> each instance. Doe
FYI: the screen disabling stuff is unlikely to be the issue here (as I
mentioned in a sub-sequent email). One reason is that it only is used for
windows that are already visible.
Both Cocoa and Carbon will send you a draw request before your window is
visible (to avoid a white flash), so that wo
I have an int representing the number of days since 1/1/2001, and wish to get
an NSDate representing that date in the system's local time zone:
NSDateComponents *dc = [[[NSDateComponents alloc] init] autorelease];
[dc setDay: numdays];
NSDate * cd = [[NSCalendar currentCalendar] dateByAddingCompo
Digging under the covers:
CFGregorianUnits gu = { 0, 0, numdays, 0, 0, 0 };
CFAbsoluteTime at = CFAbsoluteTimeAddGregorianUnits( 0, NULL, gu );
cd = [NSDate dateWithTimeIntervalSinceReferenceDate: at];
NSLog( @"date 4: %@", [cd description] );
Produces: "date 4: 2010-05-04 18:00:00 -0600", which
On Tue, Apr 27, 2010 at 8:45 PM, Scott Ribe wrote:
> NSDate * cd = [[NSCalendar currentCalendar] dateByAddingComponents: dc
> toDate: [NSDate dateWithString: @"2001-01-01"] options: 0];
This is a wrong. You don't need to go from a string to a date here.
You are violating the requirement laid out
On Apr 27, 2010, at 9:55 PM, Graham Cox wrote:
> Here's the problem: Any tasks on the undo stack that refer to a particular
> target must be removed when that target is dealloced. Obviously the clear
> place to do this is in the -dealloc method. That's fine if the node is still
> part of the tre
1 - 100 of 108 matches
Mail list logo
