On Nov 22, 2010, at 5:14 PM, George Nachman wrote:
I recently added an event tap to my program. Since doing that, there is a
strange behavior: when I kill my job (usually by making a change in Xcode
and pressing cmd-Enter, being prompted to kill the job, and selecting OK),
it will repeat
I am having trouble creating and using a custom table view cell.
I added a new cocoa obj-c file MyCell. The MyCell class derives from NSCell and
does its own drawing (drawInteriorWithFrame:inView:).
I get the following error message at run time.
---
Error invoking selector openAccountWindow on
Rounak Jain wrote:
As Jerry pointed out, you need to learn the basics; please read up on the
basics to include memory management.
I am using Garbage collector.
___
The previous comments still stand.
For starters, there are a few good
On Nov 22, 2010, at 10:58 PM, Laurent Daudelin wrote:
Trying to access this header to check its content and I don't find it in the
Foundation framework anymore for iOS. So, where is it now? All references I
find while googling it refers to pages that were updated in 2002 and 2003,
nothing
We don't know what your code looks like now. You should re-post your
*latest* code to cocoa-dev@lists.apple.com and state what is the problem at
this time.
As Jerry pointed out, you need to learn the basics; please read up on the
basics to include memory management.
The way you've now
On Nov 23, 2010, at 08:36, Nick Zitzmann wrote:
On Nov 22, 2010, at 10:58 PM, Laurent Daudelin wrote:
Trying to access this header to check its content and I don't find it in the
Foundation framework anymore for iOS. So, where is it now? All references I
find while googling it refers to
The thing that jumps out at me is that you're directly accessing the instance
variable myKeys instead of using an accessor. I'm not sure why you want this
to be a mutable array, but assuming that, I would use a method like this:
- (NSMutableArray*)myKeys {
if (!m_myKeys) {
//
I can't believe I missed the rotation gesture recognizer. I honestly searched...
On Nov 22, 2010, at 9:37 PM, Development wrote:
A while back I saw an app that had dials to adjust certain settings.
I could have sworn there was example code related to it. Anyway. I'm
wondering if any of you
Good post!
I hate reading badly formatted code...specielly code that follows standards
from the 90's. Which evern language it is.
On v.47 tis 23 nov 2010, at 18:52:58, Jerry Krinock wrote:
General recommendation: If you want people to read your code, please spend
some time to make it neat
Hello Cocoa developpers,
When using a CFRunLoopRun() event loop in a non-GUI daemon, what kind of
resource and handler do you need to add to the loop for beeing able to
process signals (unix signals) and not beeing stuck in:
(gdb) bt
#0 0x7fff815592da in mach_msg_trap ()
#1
On Nov 23, 2010, at 12:55 PM, Philippe Strauss wrote:
Hello Cocoa developpers,
When using a CFRunLoopRun() event loop in a non-GUI daemon, what kind of
resource and handler do you need to add to the loop for beeing able to
process signals (unix signals) and not beeing stuck in:
(gdb)
Chris,
thanks for your answer.
Don't do this. If you're using bindings or KVO at all in your main thread,
you CANNOT lock your context every place you need to in order to make this
safe. Furthermore, I suspect you may not be locking your context on the
background thread because you're
I just need a Label to send it's action to it's target when I click on it.
The first thing I tried was to use setTarget:, setAction:, sendActionOn:, but
that did not work. I messed around with a couple of other things, but without
success.
What did finally work was to subclass NSTextField and
HI all,
is it possible to have an outline with three elements in parents and only
element in child window ? I need to implement an outline view in which the
parent have 3 elements namely
nstext , nsimage and nsbutton and the child window has only element namely
nstext . my build is
On 23/11/2010, at 19:00, Eric Gorr wrote:
I just need a Label to send it's action to it's target when I click on it.
…
Not fully satisfied with this solution (I like to avoid subclassing unless
absolutely necessary), I was wondering if there was a better way...?
Not sure about your
I wanted to run an iPhone app I wrote 2 years ago. It would not run.
I plugged the iPhone into iTunes to update software and saw a message
that the apps provisioning certificate had expired.
Do I have to pay Jobs an annual fee? How is this broadcast to users
of my app?
WTF is Up? I
On Nov 23, 2010, at 2:25 PM, k...@highrolls.net wrote:
I wanted to run an iPhone app I wrote 2 years ago. It would not run. I
plugged the iPhone into iTunes to update software and saw a message that the
apps provisioning certificate had expired.
Do I have to pay Jobs an annual fee?
On Tue, Nov 23, 2010 at 2:25 PM, k...@highrolls.net wrote:
I wanted to run an iPhone app I wrote 2 years ago. It would not run. I
plugged the iPhone into iTunes to update software and saw a message that the
apps provisioning certificate had expired.
This has nothing to do with Cocoa.
If the app is purchased will it expire as well on a user device?
On Nov 23, 2010, at 3:31 PM, David Rowland wrote:
On Nov 23, 2010, at 2:25 PM, k...@highrolls.net wrote:
I wanted to run an iPhone app I wrote 2 years ago. It would not
run. I plugged the iPhone into iTunes to update
On Nov 23, 2010, at 2:25 PM, k...@highrolls.net wrote:
If the app is purchased will it expire as well on a user device?
Of course not. The expiry date is only for development devices. It will work
indefinitely on a user's device.
___
It will not.
But if you let your membership expire, you are no longer in the store so if the
user deletes the app, they can't re-download it.
On Nov 23, 2010, at 2:34 PM, k...@highrolls.net wrote:
If the app is purchased will it expire as well on a user device?
Thanks. This is not a Cocoa topic. I apologize for the list noise.
Happy Thanksgiving, anyway!
-koko
On Nov 23, 2010, at 3:49 PM, Hunter Hillegas wrote:
It will not.
But if you let your membership expire, you are no longer in the
store so if the user deletes the app, they can't
On 24/11/2010, at 3:42 AM, Rounak Jain wrote:
If you allocate an object using alloc, you need to take responsibility for
releasing it when you’re done.
However, if class methods are used, then there is no need to worry about
releasing objects because they are auto-released.
This is
It's not nonsense, although Jain's description is a little too loose.
Rephrased : If you obtain an object using a method containing the words alloc,
copy, or new, *you* are responsible for releasing the object, otherwise you are
not responsible and the object will be auto-released.
That's a
On 24/11/2010, at 12:41 PM, Rob Ross wrote:
It's not nonsense, although Jain's description is a little too loose.
Rephrased:
First rule of the Cocoa Club: You must not rephrase The Rules.
However, if class methods are used, then there is no need to worry about
releasing objects because
Shameless bump ... any ideas?
On Mon, Nov 22, 2010 at 9:41 AM, Shane
software.research.developm...@gmail.com wrote:
Still trying to get my unit tests to build. I have an app project
which includes unit tests as well, and it depends on another dylib
project. They're all built with
On Nov 23, 2010, at 5:41 PM, Rob Ross wrote:
otherwise you are not responsible and
More or less (there are some exceptions).
the object will be auto-released.
Sometimes.
[NSString stringWithString: @Foobar];
[NSNumber numberWithInt: 7];
Typically returns an object that is not
On Nov 23, 2010, at 12:38 PM, vincent habchi vi...@macports.org wrote:
However, I have now a repeated memory management crash when I release the moc
(apparently, one managed object get released one time too much: it is
destroyed in the main MOC, while the secondary MOC has a copy of it. When
Le 24 nov. 2010 à 05:53, Chris Hanson c...@me.com a écrit :
If your code actually looks like this, it's a bug: You're using entityInMOC1
in another thread. Pass JUST its object ID, not the object itself, from one
thread to the other.
I had not thought about this. Thanks for pointing it out.
Dear all,
I tried to add overlay view on the UIImagePickerController. Now it works,
but it seems I can't use the tap-to-focus feature any more. Can anyone help?
Thanks!
--
Best regards
Leon
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
30 matches
Mail list logo
