;>>>>>>>>//We send a message to our debugger to let us know our button was
>>>>>>>>>> pressed
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>> @end
>>>&
ing:(NSNotification
>>>>>>>>>>> *)aNotification
>>>>>>>>>>> {
>>>>>>>>>>>// Insert code here to initialize your application
>>>>>>>>>>>NSButton *myButton = [[NSButto
gt;>>>>>>>> @end
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The point of this snippet is to show the ease of skipping the
>>>>>>>>>> interface builder. This is accessible
Send me your Xcode project and let me take a look at what's going on, I won't
have steady internet access for just a bit but I'll take a look ASAP
Sent from my iPhone
> On Aug 28, 2013, at 13:36, Alex Hall wrote:
>
> I know it has been some time since this thread ended, but I saved the below
Actually, it's not gcc anymore but lvm something. I read it in one of the
objective c primers, starting x-code 4.5
As for testing the code, there is one called code runner which i found on the
appstore, which i quite like as it's small footprint, compatible with 10
languages, including objectiv
Hello Yuma. You will need some kind of compiler or IDE to practice with. How do
you plan to proceed?
On Jul 7, 2013, at 7:21 PM, Yuma Antoine Decaux wrote:
> Sorry, i didn't mention not using x-code, but more in the attempt of
> harnessing the syntax used in objective c rather than concentrat
Gcc that was. It certainly has a objective c compiler.
Sent from my iPhone
On Jul 7, 2013, at 8:50 PM, "Jonathan C. Cohn" wrote:
> I believe Xccode still uses gccunder the hood.
>
> Sent from my iPhone
>
> On Jul 7, 2013, at 8:21 PM, Yuma Antoine Decaux wrote:
>
>> Sorry, i didn't ment
I believe Xccode still uses gccunder the hood.
Sent from my iPhone
On Jul 7, 2013, at 8:21 PM, Yuma Antoine Decaux wrote:
> Sorry, i didn't mention not using x-code, but more in the attempt of
> harnessing the syntax used in objective c rather than concentrating on the
> interface or IB in x
Sorry, i didn't mention not using x-code, but more in the attempt of harnessing
the syntax used in objective c rather than concentrating on the interface or IB
in x-code for now.
"Light has no value without darkness"
On 7/07/2013, at 8:11 PM, Paul Hunt wrote:
> Hello Yuma. If you aren't u
Hello Yuma. If you aren't using XCode to learn Objective-C, what compiler are
you using?
On Jul 6, 2013, at 8:30 PM, Yuma Antoine Decaux wrote:
> Yuma
>
--
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To unsubscribe from this group and s
grammatically, then we are more competent programmers than
>> our sighted counterparts because we understand what’s really going on. In
>> addition, when we use a textbook, we literally have to translate Interface
>> Builder speak into lines of code. The question then is this, where
extbook, we literally have to translate Interface
> Builder speak into lines of code. The question then is this, where is the
> Objective C documentation? Where can we find a description of all of the
> APIS? Can you point us in the right direction?
>
> Thanks so much.
>
>
>
&
ies@googlegroups.com]
On Behalf OfTyler Thompson
Sent: Friday, July 5, 2013 2:13 AM
To: macvisionaries@googlegroups.com
Subject: Re: xcode creating actions and outlets
believe me i understand the frustrations of working with objective C,
especially if it’s new. As it happens I find that programmati
> [mailto:macvisionaries@googlegroups.com] On Behalf Of Tyler Thompson
> Sent: Friday, July 5, 2013 2:13 AM
> To: macvisionaries@googlegroups.com
> Subject: Re: xcode creating actions and outlets
>
> believe me i understand the frustrations of working with objective C,
> e
ries@googlegroups.com
[mailto:macvisionaries@googlegroups.com] On Behalf Of Tyler Thompson
Sent: Friday, July 5, 2013 2:13 AM
To: macvisionaries@googlegroups.com
Subject: Re: xcode creating actions and outlets
believe me i understand the frustrations of working with objective C,
especially if it's
Let me start out by saying you don’t actually ever #include/#import the xib,
(that’s the user interface file and even when you’ve chosen to use the
interface builder you don’t ever include it anywhere) I can tell you that stack
overflow is a wonderful resource for any objective c/cocoa help. (pe
Do you have a link where i can see where i'm supposed to programmatically link
controls?
I know there are statements to include in controller.h controller.m and
application.xib, but im not sure what i'm supposed to write in application.xib
Any help greatly appreciated. I've given up on emulati
believe me i understand the frustrations of working with objective C,
especially if it’s new. As it happens I find that programmatically linking your
UI elements tends to actually work a little better (as it gives you much more
control), but for each person it’s different :)
On Jul 5, 2013, at
Hi,
There is a method which i found on the maccessibility news page. Convoluted,
and not able to do it yet, it's driving me crazy.
I might try it programmatically but i'm going through a textbook method and
they're entirely gui based so i'm left wanting, once more. Starting to get
tired of the
To tack on to my previous comment here’s how you can programatically link
objects with objective c
NSButton *theButton;
[theButton addTarget:self action:@selector(buttonMethod:)
forControlEvents:someControlEvent];
On Jul 4, 2013, at 10:23 PM, Yuma Antoine Decaux wrote:
> Hi All,
>
> I am go
I can’t speak to the voiceOver side of things but i know most blind developers
i’ve spoken to just simply don’t use the interface builder at all, no reason
you can’t initialize your object and hook it up to your method with
NSNotifications or it’s delegate method, a little more specifics on what
Hi All,
I am going through an IOS book right now, and am stuck at a point where i need
to create an action in my controller for a button. I'm supposed to control drag
a button to my assistant editor so that x code can automatically place the
appropriate action method and properties to my projec
22 matches
Mail list logo
