I' doing the implementation of AQGridView, and everything was going well.
But, now I'm getting the error below.
- (AQGridViewCell *) gridView: (AQGridView *)inGridView cellForItemAtIndex:
(NSUInteger) index;
{
MagazineCell *cell = (MagazineCell *)[inGridView
dequeueReusableCellWithIdentifier:@"
This sort of thing is more commonly handled by a button in a toolbar either
above or below the table.
Another approach is the drag/release to reload (as seen in some Twitter apps
for example).
A button partially occluding the table sounds awkward to me, and IB is likely
trying to block you fo
Hi All,
I have a table view and would like to float a button on top of the
table view. The button is a will function as a refresh, and have a PNG
image.
When I try and place a button on the table in Interface Builder, the
drag/drop is rejected. Can someone point me in the right direction?
Thanks
On Jun 27, 2011, at 6:17 PM, Quincey Morris wrote:
> On Jun 27, 2011, at 15:58, Philip Dow wrote:
>
>> I am exploring using a custom window controller for a core data document
>> based application and wanted to ask those more knowledgeable than myself if
>> there are any caveats I must conside
On Jun 27, 2011, at 15:58, Philip Dow wrote:
> I am exploring using a custom window controller for a core data document
> based application and wanted to ask those more knowledgeable than myself if
> there are any caveats I must consider.
>
> Following the documentation, I am overriding NSDocum
I am exploring using a custom window controller for a core data document based
application and wanted to ask those more knowledgeable than myself if there are
any caveats I must consider.
Following the documentation, I am overriding NSDocument's makeWindowControllers
method in my NSPersistentDo
I overlooked -windowShouldClose returning the wrong value.
Excuse the noise ... -koko
On Jun 27, 2011, at 4:11 PM, koko wrote:
>
> On Jun 27, 2011, at 3:18 PM, Jerry Krinock wrote:
>
>>
>> On 2011 Jun 27, at 12:48, koko wrote:
>>
>>> Where should I look for ?corruption of the deleagate ..
On Jun 27, 2011, at 3:18 PM, Jerry Krinock wrote:
>
> On 2011 Jun 27, at 12:48, koko wrote:
>
>> Where should I look for ?corruption of the deleagate ... or just what.
>
> You could set a breakpoint on -[NSApplication setDelegate:]
In the Breakpoint Window I entered [NSApplication setDelegate
On Jun 27, 2011, at 3:10 PM, Jens Alfke wrote:
>
> On Jun 27, 2011, at 12:48 PM, koko wrote:
>
>> Now when I click the red close button the app delegate method
>> applicationShouldTerminate is not called.
>
> So, by default closing the window wouldn’t quit the app. If it is, that
> implies t
On 2011 Jun 27, at 12:48, koko wrote:
> Where should I look for ?corruption of the deleagate ... or just what.
You could set a breakpoint on -[NSApplication setDelegate:]
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post adm
On Jun 27, 2011, at 12:48 PM, koko wrote:
> Now when I click the red close button the app delegate method
> applicationShouldTerminate is not called.
So, by default closing the window wouldn’t quit the app. If it is, that implies
that your delegate also has a -applicationShouldTerminateAfterLa
In a simple app of mine, I use the standard Help menu and MyApp Help
menu item, which is bound to -showHelp:.
I would like to have my AppDelegate being informed when the Help Viewer
has been launched and opened from this menu item.
It seems as if the method -showHelp: cannot be overridden. Wh
I can elaborate why this delay exists. If you have two or more rows selected,
there is a slight delay so one can double click on all the selected rows and
perform an action on all of them (ie: open all). After the delay passes with no
second click (we wait for the double click interval), the ori
Under what conditions or causes would preclude an app delegate meth from being
called?
At start up in appDidFinishLaunching I log the delegate for reference.
Then I execute a method and at the end of the method I log the delegate again
for comparison and it checks out.
Now when I click the red
On Jun 27, 2011, at 1:13 PM, Jens Alfke wrote:
> It makes sense to me. Integer coordinates denote the grid lines between
> pixels, not the pixel centers. Likewise, the hot-spot of the cursor is in
> between pixels, not in the center of a pixel. In the case of the default
> arrow cursor, the hot
On Jun 27, 2011, at 6:22 AM, William Squires wrote:
> What if I have an init method, and - in the above '// Do something here'
> section - my initializations fail (maybe a resource can't be located/loaded)
> - should I raise an NSException, or set self=nil so that any subclasses will
> get a n
On Jun 27, 2011, at 11:39 AM, Richard Somers wrote:
> The documentation matches the behavior. Cocoa event objects do indeed return
> y coordinate values that are 1-based. A mouse click on the bottom left corner
> of a window or view yields the point (0, 1) in Cocoa and not (0, 0).
> ...
> The d
The documentation matches the behavior. Cocoa event objects do indeed return y
coordinate values that are 1-based. A mouse click on the bottom left corner of
a window or view yields the point (0, 1) in Cocoa and not (0, 0).
I recently submitted bug 9639143 on another issue but it has a sample
a
On Jun 27, 2011, at 1:26 PM, Raleigh Ledet wrote:
> Cocoa coordinates are all 0,0 based. If you have a reproducible test case
> that says otherwise, please file a radar and attach it.
>
> -raleigh
>
>
> On Jun 25, 2011, at 7:59 AM, Richard Somers wrote:
>
>> The Cocoa Drawing Guide states "C
Cocoa coordinates are all 0,0 based. If you have a reproducible test case that
says otherwise, please file a radar and attach it.
-raleigh
On Jun 25, 2011, at 7:59 AM, Richard Somers wrote:
> The Cocoa Drawing Guide states "Cocoa event objects return y coordinate
> values that are 1-based ins
Your instantiating your NSBrowser from a nib file. Try over riding
- (id)initWithCoder:(NSCoder *)coder
-raleigh
On Jun 26, 2011, at 4:18 AM, Ari Black wrote:
> On 11-06-26 7:04 AM, Fritz Anderson wrote:
>>
>> On 25 Jun 2011, at 7:05 PM, Ari Black wrote:
>>
>>> @implementation SpecialMatrix
>
OK here is a more detailed explanation of what I am doing
I start downloading the video file with a NSURLConnection
I then implement the received data delegate method like the following.
- (void)connection:(NSURLConnection *)aConnection didReceiveData:(NSData *)aData
{
bytesFetched += aD
On Jun 26, 2011, at 12:51 PM, Tales Pinheiro de Andrade wrote:
> Well, I used the macro UIDeviceOrientationIsLandscape, I'm assuming that this
> is for both sides:
> #define UIDeviceOrientationIsPortrait(orientation) ((orientation) ==
> UIDeviceOrientationPortrait || (orientation) ==
> UIDevic
yes I know it's equivalent, didn't say it wasn't, I said it was the favored
form, which I remembered from Scott's message a year ago in this thread
http://www.cocoabuilder.com/archive/cocoa/286849-self-super-init-nil.html#286952
where he said
This has been, or is being update
On Mon, Jun 27, 2011 at 6:38 AM, Roland King wrote:
>> The favored form for writing an init method seems to be
>>
>> -(id)init
>> {
>> if (self = [super init])
>> {
>> // Do something here
>> }
>> return self;
>> }
>
> actually I think the current favoured method is
>
> -(id)init
> {
> s
On 27-Jun-2011, at 9:22 PM, William Squires wrote:
> 2) Isn't the prevailing paradigm to raise an NSException if something goes
> wrong?
No. In Cocoa, exceptions are used to indicate programmer error, not runtime
failure. In general, Cocoa isn't exception safe, so if an exception occurs,
yo
On 27-Jun-2011, at 9:22 PM, William Squires wrote:
> The favored form for writing an init method seems to be
>
> -(id)init
> {
> if (self = [super init])
> {
> // Do something here
> }
> return self;
> }
actually I think the current favoured method is
-(id)init
{
self = [ super init
The favored form for writing an init method seems to be
-(id)init
{
if (self = [super init])
{
// Do something here
}
return self;
}
Several questions arise:
1) Isn't the 'if' superfluous? if self was nil (after the assignment from
[super init]), any messages sent (in the commented section
Great, thanks Heath.
> Date: Sun, 26 Jun 2011 21:23:02 -0500
> From: heath.bord...@gmail.com
> To: cocoa-dev@lists.apple.com
> Subject: Re: MFMailComposeViewController: referencing attached data in HTML
> body
>
> You could base64 your image data and use a data url to refer to it
> within you
29 matches
Mail list logo
