Dear All,
There may be several approaches to solve the issue I am about to describe,
either on the userland side or on the kernel side... or in-between, using a
daemon.
Current situation
A bsd kernel extension communicates with a regular userland application (called
theApp). The kext gathers s
On Mar 11, 2013, at 2:02 PM, Dave wrote:
>
> On 11 Mar 2013, at 20:53, John McCall wrote:
>
>> On Mar 11, 2013, at 1:33 PM, Dave wrote:
>>> On 11 Mar 2013, at 20:26, Mike Abdullah wrote:
>
> I had assumed (and I thought I'd done something like this before) that
> the:
>
>>>
On Mar 11, 2013, at 1:55 PM, Dave wrote:
> Not sure I understand:
>
> if from an Instance - Method, I do:
>
> [super someMehod];
>
> It calls -someMehod in the superclass.
>
> if from an instance + Method I do:
>
> [super someMethod], then surely it's an error because this isn't an instance?
On Mar 11, 2013, at 2:55 PM, Dave wrote:
> On 11 Mar 2013, at 20:50, Jens Alfke wrote:
>
>>
>> On Mar 11, 2013, at 1:33 PM, Dave wrote:
>>
>>> There isn't a
>>> -newDict
>>> method defined, so how come I didn't get a complier error?
>>
>> Because the receiver is a Class, so the method is +new
On Mon, Mar 11, 2013, at 01:55 PM, Dave wrote:
> Not sure I understand:
>
> if from an Instance - Method, I do:
>
> [super someMehod];
>
> It calls -someMehod in the superclass.
>
> if from an instance + Method I do:
>
> [super someMethod], then surely it's an error because this isn't an
>
On 11 Mar 2013, at 20:55, Dave wrote:
>
> On 11 Mar 2013, at 20:50, Jens Alfke wrote:
>
>>
>> On Mar 11, 2013, at 1:33 PM, Dave wrote:
>>
>>> There isn't a
>>> -newDict
>>> method defined, so how come I didn't get a complier error?
>>
>> Because the receiver is a Class, so the method is +n
On Mar 11, 2013, at 1:45 PM, Dave wrote:
>>> myDict = [[super class] newDict];
>>
>> This should be [super newDict].
>
>> -- Seth
>
>
> Surely that would call the Instance Method (and there isn't one), I think the
> correct code is:
>
> [[self superclass] newDict];
>
> as someone else all
On 11 Mar 2013, at 20:49, Dave wrote:
> On 11 Mar 2013, at 20:45, Mike Abdullah wrote:
>
> Confused now, I thought you meant +.
>
> There is no instance of the class to call [super newDict] on?
>
> There is no:
>
> -NewDict method, just +newDict.
>
> So, surely [super newDict] should error?
On Mar 11, 2013, at 1:45 PM, Dave wrote:
> On 11 Mar 2013, at 20:30, Seth Willits wrote:
>> On Mar 11, 2013, at 1:21 PM, Dave wrote:
>>
>>> +(NSMutableDictionary*) newDict
>>> {
>>> return [[NSMutableDictionary alloc] init];
>>> }
>>
>> (I hope you're using ARC otherwise this is a memory leak.)
On 11 Mar 2013, at 20:53, John McCall wrote:
On Mar 11, 2013, at 1:33 PM, Dave wrote:
On 11 Mar 2013, at 20:26, Mike Abdullah wrote:
I had assumed (and I thought I'd done something like this
before) that the:
myDict = [[super class] newDict];
statement would call newDict in BaseClass??
On 11 Mar 2013, at 20:50, Jens Alfke wrote:
On Mar 11, 2013, at 1:33 PM, Dave wrote:
There isn't a
-newDict
method defined, so how come I didn't get a complier error?
Because the receiver is a Class, so the method is +newDict, which
exists.
Not sure I understand:
if from an Instan
On Mar 11, 2013, at 1:33 PM, Dave wrote:
> On 11 Mar 2013, at 20:26, Mike Abdullah wrote:
>>>
>>> I had assumed (and I thought I'd done something like this before) that the:
>>>
>>> myDict = [[super class] newDict];
>>>
>>> statement would call newDict in BaseClass Instead it calls the vers
On 11 Mar 2013, at 20:45, Mike Abdullah wrote:
On 11 Mar 2013, at 20:33, Dave wrote:
On 11 Mar 2013, at 20:26, Mike Abdullah wrote:
I had assumed (and I thought I'd done something like this
before) that the:
myDict = [[super class] newDict];
statement would call newDict in BaseClass
On Mar 11, 2013, at 1:33 PM, Dave wrote:
> There isn't a
> -newDict
> method defined, so how come I didn't get a complier error?
Because the receiver is a Class, so the method is +newDict, which exists.
—Jens
___
Cocoa-dev mailing list (Cocoa-dev@li
On Mar 11, 2013, at 1:26 PM, Dave wrote:
> I had assumed (and I thought I'd done something like this before) that the:
> myDict = [[super class] newDict];
> statement would call newDict in BaseClass Instead it calls the version in
> NewClass and goes into an infinite loop!!
No, what you wa
On 11 Mar 2013, at 20:30, Seth Willits wrote:
On Mar 11, 2013, at 1:21 PM, Dave wrote:
+(NSMutableDictionary*) newDict
{
return [[NSMutableDictionary alloc] init];
}
(I hope you're using ARC otherwise this is a memory leak.)
Yes, but it's only an example so don't worry about that, and, a
On 11 Mar 2013, at 20:33, Dave wrote:
>
> On 11 Mar 2013, at 20:26, Mike Abdullah wrote:
>>>
>>> I had assumed (and I thought I'd done something like this before) that the:
>>>
>>> myDict = [[super class] newDict];
>>>
>>> statement would call newDict in BaseClass Instead it calls the ve
On Mar 11, 2013, at 1:30 PM, Seth Willits wrote:
> On Mar 11, 2013, at 1:21 PM, Dave wrote:
>
>> +(NSMutableDictionary*) newDict
>> {
>> return [[NSMutableDictionary alloc] init];
>> }
>
> (I hope you're using ARC otherwise this is a memory leak.)
A 'new' prefix is defined as returning an ow
On Mar 11, 2013, at 4:30 PM, Seth Willits wrote:
> On Mar 11, 2013, at 1:21 PM, Dave wrote:
>
>> +(NSMutableDictionary*) newDict
>> {
>> return [[NSMutableDictionary alloc] init];
>> }
>
> (I hope you're using ARC otherwise this is a memory leak.)
Not if the caller knows to observe the rule ab
On 11 Mar 2013, at 20:26, Mike Abdullah wrote:
I had assumed (and I thought I'd done something like this before)
that the:
myDict = [[super class] newDict];
statement would call newDict in BaseClass Instead it calls the
version in NewClass and goes into an infinite loop!!
Yes. [sup
On Mar 11, 2013, at 1:21 PM, Dave wrote:
> +(NSMutableDictionary*) newDict
> {
> return [[NSMutableDictionary alloc] init];
> }
(I hope you're using ARC otherwise this is a memory leak.)
> myDict = [[super class] newDict];
This should be [super newDict].
-- Seth
_
On 11. Mar 2013, at 20:21, Dave wrote:
try
myDict = [super newDict];
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.app
Typeo:
return [[NSMutableDictionary alloc] init];
should be:
return myDict;
---
Hi,
Take the following example:
@interface BaseClass
+(NSMutableDictionary*) newDict;
@end
@implementation BaseClass
+(NSMutableDictionary*) newDict
On 11 Mar 2013, at 20:21, Dave wrote:
> Hi,
>
> Take the following example:
>
> @interface BaseClass
>
> +(NSMutableDictionary*) newDict;
>
> @end
>
> @implementation BaseClass
>
> +(NSMutableDictionary*) newDict
> {
>
>
> return [[NSMutableDictionary alloc] init];
> }
>
>
> @class New
Hi,
Take the following example:
@interface BaseClass
+(NSMutableDictionary*) newDict;
@end
@implementation BaseClass
+(NSMutableDictionary*) newDict
{
return [[NSMutableDictionary alloc] init];
}
@class NewClass;
@interface NewClass : BaseClass
+(NSMutableDictionary*) newDict;
@end
#
On 25 Feb 2013, at 22:45, Steve Sisak wrote:
At 3:18 PM + 2/25/13, Dave wrote:
On 25 Feb 2013, at 13:57, Steve Sisak wrote:
Created A, B, C, make C dependent on A, B, submit all of them to
an NSOperationQueue and wait for C to complete (or put your
completion code on a block dependent
On 25 Feb 2013, at 15:45, Kyle Sluder wrote:
On Mon, Feb 25, 2013, at 07:18 AM, Dave wrote:
Agreed. but that is true of anything, I am comfortable with Multi-
Threading so it's not really an issue for me.
Someone who's truly comfortable with multithreading would be relishing
the opportunity
I'm subclassing NSATSTypesetter to add custom line wrapping behavior which
indents wrapped lines relative to the starting line's indentation (like Xcode).
To do this, I'm overriding -
getLineFragmentRect:usedRect:remainingRect:forStartingGlyphAtIndex:... and for
wrapped lines am modifying the
On Mar 11, 2013, at 3:15 AM, anni saini wrote:
> My app is just having NSStatusBar menu such as Adium. On right click context
> menu, I'm calling some window to open.
>
> //Calling method
> myWindow = [[MyWindowViewController alloc]init];
> myWindow.data = @"abc";
> [myWindow show:self];
>
> //
My steps are:
1) Launch XCode
2) Create a new project
3) Select Single View Application
4) Give a Project Name
5) Select Device iPhone
6) Click on MainStoryboard.storyboard
7) Delete what's there so that it's blank
8) Add New file Objective-C class subclass UIViewController
9) Uncheck iPad and unc
If you want the behavior of a series of buttons, I'd have a series of buttons.
Table view cells simply don't behave like buttons. If it makes it easier for
you, it might make sense to put buttons inside table view cells.
Luke
On Mar 11, 2013, at 4:38 AM, "Ben" wrote:
> Hi,
>
> I have a UIT
I must not be doing what you are. I don't see a problem.
On 10 Mar 2013, at 5:48 PM, gary.gard...@brokensoftware.com wrote:
> I am using XCode 4.6 and created a project.
>
> I am using a Single View Application type of project
I selected iPhone only. I checked the Use Storyboards box in the new
Hi,
I have a UITableView which I have disabled scrolling on.
When a user touches a cell it is selected as required, however when a user
touches, drags then releases (on that same cell) no selection of the cell
happens.
I understand that in normal use this would be the correct behaviour(as a
Hi,
My app is just having NSStatusBar menu such as Adium. On right click context
menu, I'm calling some window to open.
//Calling method
myWindow = [[MyWindowViewController alloc]init];
myWindow.data = @"abc";
[myWindow show:self];
//Called method
- (void)show:(NSWindow*)parentWindow
{
[myPa
34 matches
Mail list logo
