On Tue, Nov 1, 2011 at 10:47 PM, Matt Neuburg wrote:
> On my machine, what happens is that we SIGABRT with the editor falling into
> main.c and no logging of any kind in the console.
Did you drag the slider at the bottom of the Breakpoint Navigator all
the way to the right to reveal framework st
On 2 November 2011 00:06, Matt Neuburg wrote:
> On Sun, 30 Oct 2011 15:55:39 +, Igor Mozolevsky
> said:
>>On 30 October 2011 15:15, Matt Neuburg wrote:
>>> In ARC, this is legal:
>>>
>>> self.view.layer.contents = (id)[[UIImage imageNamed:@"boat.gif"] CGImage];
>>>
>>> And this is legal:
>>
I want to set a dispatch queue via a property. How should I set the property's
attributes when the queue is retained/released via functions dispatch_retain()
and dispatch_release()?
Currently, since using "retain" is only possible for objects, I just declare it
like follows:
@property (nonatom
Hi Andreas.
I assuming that you aren't using ARC, right?
Be aware that the property declaration that you send doesn't retain anything.
The declaration should by:
@property (nonatomic, retain) dispatch_queue_t *dispatchQueue;
On Nov 2, 2011, at 9:52 AM, Andreas Grosam wrote:
> I want to set a d
Automatic property generation doesn't support the semantics you need.
You are correct that you have to use the dispatch_retain() and
dispatch_release() functions; you just have write your setter and getter
manually, using those functions.
-Jamie
Sent from my iPhone
On Nov 2, 2011, at 7:52 A
Bruno,
> @property (nonatomic, retain) dispatch_queue_t *dispatchQueue;
Let's assume for a second that this worked. Since dispatch_queue_t is already
typedef'd as a pointer "typedef struct dispatch_queue_s *dispatch_queue_t;".
You've declared the property as a pointer to a pointer, which mea
On Nov 2, 2011, at 1:33 PM, Jamie Pinkham wrote:
> Automatic property generation doesn't support the semantics you need.
>
> You are correct that you have to use the dispatch_retain() and
> dispatch_release() functions; you just have write your setter and getter
> manually, using those functi
Andreas,
It most certainly indicates a semantic. That is, the generated property
accessors and getters will retain the object versus, copying or assigning the
object. In this case, the semantic you are trying to enforce isn't possible
for the type you are trying to enforce it on. The error y
Andreas,
Also, in the modern runtime, you'll need to add the @synthesize to the
implementation file as well, if you don't declare the backing ivar in the
header.
Thanks,
Jamie
On Nov 2, 2011, at 10:51 AM, Jamie Pinkham wrote:
> Andreas,
>
> It most certainly indicates a semantic. That is,
On Nov 2, 2011, at 1:48 AM, Andreas Grosam wrote:
> I cannot reproduce what you are experiencing
Well, that caused me to do some more testing, and I now suspect that in order
to reproduce it you might have to be running Xcode 4.2 on Snow Leopard. Snow
Leopard's Xcode seems to have a number of
On Nov 2, 2011, at 4:31 AM, Igor Mozolevsky wrote:
> the compiler has
> no clue what you intend to do with `ref' of type `CGImageRef'. What
> bridging does is it tells the compiler to stop worrying because _you_
> have taken over the management of the type
You're focussing on the wrong part of
From the compiler point of view, the 'retain' semantic does not mean anything
for an arbitrary type like dispatch queue.
So indicating the semantic to the compiler is pointless.
Now, if you want to expose the semantic to the developers that use this class,
a simple comment is probably enough.
On Nov 1, 2011, at 7:47 PM, Matt Neuburg wrote:
> But that is a *lot* of ifs. A lot more ifs than we can expect of, say, a
> beginner. (For one thing, the templates don't use the LLDB debugger. For
> another, what beginner has heard of $eax?) And yet this console message is
> helpful particular
On 2 November 2011 15:43, Matt Neuburg wrote:
> What I wasn't understanding is why I *didn't* have to cast to __bridge id in
> the first two cases I listed.
That's easy: the compiler should have no problem tracking the use of
ids throughout as they are easily managed (eg, an id can live inside
On 02 Nov 2011, at 8:22 am, Matt Neuburg wrote:
On Nov 2, 2011, at 3:39 AM, Kyle Sluder wrote:
I have to ask why you're printing $eax
You tell me. I'm doing it because Ben Kennedy and a bunch of Web
sites (after a Google search) told me to. m.
And I'll tell you why I did: after being baf
On Nov 2, 2011, at 9:55 AM, Ben Kennedy wrote:
> On 02 Nov 2011, at 8:22 am, Matt Neuburg wrote:
>
>> On Nov 2, 2011, at 3:39 AM, Kyle Sluder wrote:
>>
>>> I have to ask why you're printing $eax
>>
>> You tell me. I'm doing it because Ben Kennedy and a bunch of Web sites
>> (after a Google se
On Nov 2, 2011, at 1:18 PM, Matt Neuburg wrote:
>
> On Nov 2, 2011, at 9:55 AM, Ben Kennedy wrote:
>
>> On 02 Nov 2011, at 8:22 am, Matt Neuburg wrote:
>>
>>> On Nov 2, 2011, at 3:39 AM, Kyle Sluder wrote:
>>>
I have to ask why you're printing $eax
>>>
>>> You tell me. I'm doing it beca
On 02 Nov 2011, at 10:37 am, Kyle Sluder wrote:
> I just wouldn't trust LLDB for anything at this point, after watching my
> coworkers fight it.
Well, I forgot to mention that (unsurprisingly) I have also been using LLDB, to
which I switched precisely because I discovered that it solved this pr
Hi,
I'm having a window with just a single custom view in it. The window is
resizable and when resized I need the view to be redrawed. But when
dragging the corner and resizing the window, OS first fills the window with
white, then paints the previous image left bottom and finally asks the view
to
On Nov 2, 2011, at 12:13 PM, Vojtěch Meluzín wrote:
> Is there a way to prevent
> OS from filling the window with white and painting the original image, and
> rather ask the view immediately?
What you’re seeing is definitely not normal behavior. Either it’s an artifact
of the unusual way your a
On Tue, 1 Nov 2011 11:00:33 -0700, James Merkel said:
>Why would someone want to base their application on the tenuous
>availability of a temporary exception ?
Because there's no choice. They are the only way to achieve a large number of
extremely common operations.
I'm looking forward to seei
On Tue, 1 Nov 2011 09:58:12 -0700, Howard Moon said:
>I experienced the exact same symptoms as the OP when trying to open more
>than just a handful of .png files at once (NONE of which were downloaded
>from the internet, but created in Photoshop). Perhaps after some number
>of files is exceeded,
> What you’re seeing is definitely not normal behavior. Either it’s an
> artifact of the unusual way your app is structured (is this happening
> within that modal panel?), or you’re doing something unusual when drawing
> your view. How are you doing the drawing? You should just need to override
> -
On Nov 2, 2011, at 8:43 AM, Matt Neuburg wrote:
> And, since Apple's own example, with no casting, does not compile, I was left
> with *no* official documentation as to what I should do in those cases.
Did you file a bug report?
--
Greg Parker gpar...@apple.com Runtime Wrangler
On Nov 2, 2011, at 1:39 PM, Vojtěch Meluzín wrote:
> It is then used to get CGContextRef for drawing.
What does that mean, exactly? Does anything draw into the view except during
the -drawRect: method?
—Jens___
Cocoa-dev mailing list (Cocoa-dev@lis
No no, just during the drawRect. I was just explaining how the drawing is
done, just in case it matters. The reason is that CGContextRef was used
with carbon as well, so the code is more or less the same.
Vojtech
Dne 2. listopadu 2011 23:18 Jens Alfke napsal(a):
>
> On Nov 2, 2011, at 1:39 PM,
Hi,
I'm using modal windows using runModalForWindow and I'd like to implement
probably a slightly untypical thing - when a user clicks outside of the
window, it gets closed, like he clicked cancel button or something. The
idea is that this would simulate a popup menu. I know it's not exactly
typic
On Nov 2, 2011, at 5:29 PM, Vojtěch Meluzín wrote:
> I'm using modal windows using runModalForWindow and I'd like to implement
> probably a slightly untypical thing - when a user clicks outside of the
> window, it gets closed, like he clicked cancel button or something. The
> idea is that this wou
> > I'm using modal windows using runModalForWindow and I'd like to implement
> > probably a slightly untypical thing - when a user clicks outside of the
> > window, it gets closed, like he clicked cancel button or something. The
> > idea is that this would simulate a popup menu. I know it's not ex
On Nov 2, 2011, at 16:55, Vojtěch Meluzín wrote:
>>> I'm using modal windows using runModalForWindow and I'd like to implement
>>> probably a slightly untypical thing - when a user clicks outside of the
>>> window, it gets closed, like he clicked cancel button or something. The
>>> idea is that th
> > This is just a special case. In basically all platforms so far it was
> quite
> > easy to find a simple way to detect, when user clicks outside of the
> > window, so in case particular window should be a "menu", then I could
> just
> > close it on user click outside (or OS did that automaticall
Damn, Jens you were right! It's my fault. Sorry for the problems.
Vojtech
Dne 2. listopadu 2011 23:36 Vojtěch Meluzín
napsal(a):
> No no, just during the drawRect. I was just explaining how the drawing is
> done, just in case it matters. The reason is that CGContextRef was used
> with carbon as
On Nov 2, 2011, at 6:25 PM, Vojtěch Meluzín wrote:
> ...all I found was a classical popup menu with set of items, but in my case
> the menus may be much more complicated...
What version of OS X? Almost sounds like you're describing a popover, as in
Lion. But still, the comments pointing you back
Ok, folks please forget about the intentions, if they are bad, they will be
badly rewarded :).
Anyway I need it from Leopard. Is that really so hard to do such a trivial
thing in Cocoa???
Vojtech
Dne 3. listopadu 2011 1:42 Scott Ribe napsal(a):
> On Nov 2, 2011, at 6:25 PM, Vojtěch Meluzín wrote
Cocoa discourages behaviors that in normal UI practice are not wise. So when
you want to do something very unique/custom, then yes it can be hard, but never
impossible.
On Nov 2, 2011, at 7:46 PM, Vojtěch Meluzín wrote:
> Ok, folks please forget about the intentions, if they are bad, they will
On Nov 2, 2011, at 6:46 PM, Vojtěch Meluzín wrote:
> Anyway I need it from Leopard. Is that really so hard to do such a trivial
> thing in Cocoa???
No it's not, but you need to listen to what people are telling you...
--
Scott Ribe
scott_r...@elevated-dev.com
http://www.elevated-dev.com/
(303)
On 11/2/11 5:46 PM, Vojtěch Meluzín wrote:
> Ok, folks please forget about the intentions, if they are bad, they will be
> badly rewarded :).
> Anyway I need it from Leopard. Is that really so hard to do such a trivial
> thing in Cocoa???
NSWindow's delegate protocol declares a -windowDidResignKey
I've created a modal dialog that uses an NSTreeController as part of a
master-detail style interface to a hierarchical storage model. Using bindings
(not delegate methods) to supply the data. Using 10.4 as the base SDK. XIB
attached.
Works fine on Lion and Snow Leopard. It's a little odd on
On 02/11/2011, at 6:19 AM, James Merkel wrote:
> Your're assuming the temporary exception will always be granted.
A point seemingly made clear in today's email on the topic: "These entitlements
are granted on a short-term basis and will be phased out over time."
--
Shane Stanley
'AppleScript
On Nov 2, 2011, at 18:42 , Eric Slosser wrote:
> I've created a modal dialog that uses an NSTreeController as part of a
> master-detail style interface to a hierarchical storage model. Using
> bindings (not delegate methods) to supply the data. Using 10.4 as the base
> SDK. XIB attached.
>
40 matches
Mail list logo
