On Jul 24, 2011, at 11:41 AM, Tom Jeffries wrote:
> Jens, I'm sorry if my naming conventions confuse you. I've been programming
> for 27 years on a wide variety of operating systems, and I'm afraid following
> Cocoa naming conventions is not high on my list.
OK. It’s 33 years in my case, 15 of
On Jul 24, 2011, at 4:01 PM, Tom Jeffries wrote:
> On Sun, Jul 24, 2011 at 12:12 PM, Andy Lee wrote:
> You should know that it is most certainly possible to use that syntax with a
> variable. For example:
>
>NSString *myString = @"abc"; // <== a variable
>NSString *newString = [myStrin
NSString is the class. myString is an instance of that class and in this case
is a variable. myString is information. Its not an operation. It is a class
instance which contains information on what the data is and what can be done
with it.
mystring is not a function. copy is a method call to t
On Sun, Jul 24, 2011 at 12:12 PM, Andy Lee wrote:
> You should know that it is most certainly possible to use that syntax with
> a variable. For example:
>
>NSString *myString = @"abc"; // <== a variable
>NSString *newString = [myString copy]; // <== a message send
>
> You can send mess
You mentioned that things are working perfectly except for the drawing. I did
notice that, I am not dismissing that, I just want to confirm some simple
things in an effort to help...
On Jul 24, 2011, at 1:11 PM, Tom Jeffries wrote:
> I appreciate the answers, so far everything that's been sugge
On Jul 24, 2011, at 2:41 PM, Tom Jeffries wrote:
> Jens, I'm sorry if my naming conventions confuse you. I've been programming
> for 27 years on a wide variety of operating systems, and I'm afraid
> following Cocoa naming conventions is not high on my list.
One does not follow from the other. If y
Looks like today is my day for grouchy responses. "I wish I hadn't chosen this
week to give up sniffing glue." ;)
On Jul 24, 2011, at 11:41, Tom Jeffries wrote:
> Jens, I'm sorry if my naming conventions confuse you. I've been programming
> for 27 years on a wide variety of operating systems, an
I should make sure that I'm not making an assumption here, but is
SequeraStepWindow a subclass of NSWindow?
It's been a while since I've worked with NSWindow, but the reason that it works
once is because the awakeFromNib likely sends setNeedsDisplay to all it's
associated views once it's loaded
Patrick,
Everything works except that I can't get drawRect to be called a second
time. I assume that means the IBOutlet is working. However, I think you're
right that there's something about the interaction between the modules that
is causing the problem.
Thanks, Tom
On Sun, Jul 24, 2011 at 11
Jens, I'm sorry if my naming conventions confuse you. I've been programming
for 27 years on a wide variety of operating systems, and I'm afraid
following Cocoa naming conventions is not high on my list.
I thought [SequeraStepWindow awakeFromNib] makes it obvious that
SequeraStepWindow is a class.
On Jul 24, 2011, at 10:11 AM, Tom Jeffries wrote:
> + (BOOL) Play
It’s hard to tell what’s going on in the code when you’re not following Cocoa
naming conventions. Methods should start with a lowercase letter (unless they
begin with a common acronym like “URL”).
I’m very strongly in favor of
I appreciate the answers, so far everything that's been suggested is
something I've tried. Maybe if I put the code out somebody will see what
I'm doing wrong:
This is the function that is called by the mouse click, it's in another
module:
+ (BOOL) Play
{
// init code
[SequeraStepWindow DrawCu
12 matches
Mail list logo
