Re: IB does not show Outlet/Action section in inspector

2009-09-23 Thread Gregory Weston

Michael Süssner wrote:


I have the problem with every object even the one from the examples
(Apple).

I have instantiated an NSObject from the IB Library and then I've
tried to add an outlet. Still, no outlet section in the inspector
(identity).


Perhaps I'm misreading, but I suspect that Michael is using old  
documentation and has missed the important point of item #2 in Matt's  
original reply. In recent versions of the dev tools, you create  
outlets and actions in Xcode (in your header, in code) and IB  
automatically sees them.


There is no mechanism in the current version of the tools for defining  
outlets and actions in IB; only for assigning them.



___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: IB does not show Outlet/Action section in inspector

2009-09-23 Thread Bill Cheeseman


On Sep 23, 2009, at 7:11 AM, Gregory Weston wrote:

There is no mechanism in the current version of the tools for  
defining outlets and actions in IB; only for assigning them.


I don't believe this statement is true, if I understand your point  
correctly. Here's how to create an outlet or an action in IB 3.2 and  
write it back to your source files. You can also create wholly new  
classes this way.


1. In any of your project's nib files, go to the Library window (not  
the Inspector window) and select the Classes tab. Using the pop-up  
menu at the top, select one of your project's classes in the very long  
and awkward hierarchical menu. For example, your class MyDocument  
would appear in the menu under NSDocument if it inherits from  
NSDocument.


2. In the bottom pane, select the Outlets or Actions tab.

3. Near the bottom of the window, click the Add (+) button. Type a  
name for the new outlet or action and a return type (which should be  
void for actions).


4. At the bottom of the window, use the Action button and choose Write  
Updated Class Files.


5. In the dialog that comes up, choose to save the file to the  
original name for the implementation file.


6. In the warning alert that comes up to tell you that file already  
exists, choose Replace to incorporate your new outlet or action in the  
existing file, or Merge to bring up FileMerge and give yourself a  
chance to accept or reject individual changes.


7. Lock at your header file. The new outlet or action is right there.  
(The setter and getter methods or properties for outlets are not  
produced by this technique, however.) Look at your implementation  
file. If you created an action, a stub method definition appears.


Is this less than what you used to be able to do in IB? To the best of  
my memory, it gives you more control over what is produced.



--

Bill Cheeseman
b...@cheeseman.name

___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: IB does not show Outlet/Action section in inspector

2009-09-23 Thread Kevin Cathey
1. In any of your project's nib files, go to the Library window (not  
the Inspector window) and select the Classes tab. Using the pop-up  
menu at the top, select one of your project's classes in the very  
long and awkward hierarchical menu. For example, your class  
MyDocument would appear in the menu under NSDocument if it inherits  
from NSDocument.
You don't have to use the pop-up at all (Bill, based upon your  
description here, are you seeing the flat list of classes in the  
middle of the classes tab?). There are three fast ways to use the  
Classes tab:
The fastest way is to use the search field at the bottom of the  
Library window. If you use Command-Option-F, then the library appears  
and the search field takes focus. I typically always have the Classes  
tab up since I can not only instantiate any class with it into my  
document, but I can also see the lineage for the class, see where it  
is defined, and of course add actions and outlets.
If you are working in the design canvas and want to add an action or  
outlet to a class, select the instance of the class you want to add  
the outlet or action to and then use Command-Option-Right-Arrow to  
quickly reveal that class in the classes tab.
In the list of classes in the Classes tab, you can use type selection  
to quickly jump to a class. For example, NSApp jumps to NSApplication.




Now as for the motivation for putting the outlets and actions into the  
Classes tab, here is a response I just put on xcode-users:
 I wonder why the outlet/action UI was moved there … This is all the  
more confusing because you *can* add outlets to First Responder in  
the Identity inspector.


The actions and outlets were moved to the Library for the following  
reason: actions and outlets live on classes, not instances of classes.  
The Classes tab represents all of the classes you can use in your  
Interface Builder document, these come from your Xcode project, from  
frameworks you've linked against, from manually added headers, from  
plugins, and from the document itself (by setting the custom class on  
an object, setting the type of an outlet/action, or using the new  
Subclass menu item in the Classes tab). With this universal list of  
classes, it makes sense to edit the class itself.


Now First Responder is an interesting item. First Responder is itself  
not a class, so it does not make sense to put it in the Classes tab.  
In Cocoa, First Responder really acts like an instance. The actions  
for First Responder are attributes for it, and that is why they live  
in the Attributes inspector for First Responder.




I hope that clears some of that up…

Kevin

On 23 Sep 2009, at 08:26, Bill Cheeseman wrote:



On Sep 23, 2009, at 7:11 AM, Gregory Weston wrote:

There is no mechanism in the current version of the tools for  
defining outlets and actions in IB; only for assigning them.


I don't believe this statement is true, if I understand your point  
correctly. Here's how to create an outlet or an action in IB 3.2 and  
write it back to your source files. You can also create wholly new  
classes this way.


1. In any of your project's nib files, go to the Library window (not  
the Inspector window) and select the Classes tab. Using the pop-up  
menu at the top, select one of your project's classes in the very  
long and awkward hierarchical menu. For example, your class  
MyDocument would appear in the menu under NSDocument if it inherits  
from NSDocument.


2. In the bottom pane, select the Outlets or Actions tab.

3. Near the bottom of the window, click the Add (+) button. Type a  
name for the new outlet or action and a return type (which should be  
void for actions).


4. At the bottom of the window, use the Action button and choose  
Write Updated Class Files.


5. In the dialog that comes up, choose to save the file to the  
original name for the implementation file.


6. In the warning alert that comes up to tell you that file already  
exists, choose Replace to incorporate your new outlet or action in  
the existing file, or Merge to bring up FileMerge and give yourself  
a chance to accept or reject individual changes.


7. Lock at your header file. The new outlet or action is right  
there. (The setter and getter methods or properties for outlets are  
not produced by this technique, however.) Look at your  
implementation file. If you created an action, a stub method  
definition appears.


Is this less than what you used to be able to do in IB? To the best  
of my memory, it gives you more control over what is produced.



--

Bill Cheeseman
b...@cheeseman.name


___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to 

Re: IB does not show Outlet/Action section in inspector

2009-09-23 Thread Bill Cheeseman


On Sep 23, 2009, at 12:12 PM, Kevin Cathey wrote:

You don't have to use the pop-up at all (Bill, based upon your  
description here, are you seeing the flat list of classes in the  
middle of the classes tab?). There are three fast ways to use the  
Classes tab:


I'm a mouse person, so I tend to overlook keyboard solutions.

It would be nice if the Classes pop-up had an alphabetical option, or  
defaulted to alphabetical. The way it is now, I have to remember that  
the base class (after NSObject) for NSWindowController is NSResponder,  
for example. That's easy, but others are decidedly not easy to remember.


By the way, I notice that the pop-up becomes an outline view if you  
drag the divider below it downward. Very cute.


--

Bill Cheeseman
b...@cheeseman.name

___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: IB does not show Outlet/Action section in inspector

2009-09-23 Thread Gregory Weston

Bill Cheeseman corrected/educated me:


On Sep 23, 2009, at 7:11 AM, Gregory Weston wrote:


There is no mechanism in the current version of the tools for
defining outlets and actions in IB; only for assigning them.


I don't believe this statement is true, if I understand your point
correctly. Here's how to create an outlet or an action in IB 3.2 and
write it back to your source files. You can also create wholly new
classes this way.

1. In any of your project's nib files, go to the Library window (not
the Inspector window) and select the Classes tab. Using the pop-up
menu at the top, select one of your project's classes in the very long
and awkward hierarchical menu. For example, your class MyDocument
would appear in the menu under NSDocument if it inherits from
NSDocument.


You know what? I had never noticed that. I still think the OP is  
confused, though, about where he was supposed to be looking for things.



Is this less than what you used to be able to do in IB? To the best of
my memory, it gives you more control over what is produced.


Offhand, I don't think it's more or less functionality or control than  
I remember. But at least for me it was less obvious. I switched over  
to defining things by hand when 3.0 came out because I found it  
easier. Or perhaps I should say more easily.

___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


IB does not show Outlet/Action section in inspector

2009-09-22 Thread Michael Süssner
When I select an object in IB, the inspector does not display the  
outlet/action section.


Is this a bug?
I have installed Xcode on another computer and experienced the same  
behaviour.


I am using Xcode3.2 and snow leopard.

Any help?
Michael
___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: IB does not show Outlet/Action section in inspector

2009-09-22 Thread Kyle Sluder
On Mon, Sep 21, 2009 at 11:57 PM, Michael Süssner
michael.suess...@utanet.at wrote:
 When I select an object in IB, the inspector does not display the
 outlet/action section.

Did you remember to click the Outlet inspector?  g

If so, I would definitely consider that to be a bug.  Makes IB kinda
useless.  See if right-clicking on things produces the popup outlet
inspector HUD thingy, to use the technical term.

--Kyle Sluder
___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: IB does not show Outlet/Action section in inspector

2009-09-22 Thread Matt Neuburg
On Tue, 22 Sep 2009 08:57:14 +0200, Michael S?ssner
michael.suess...@utanet.at said:
When I select an object in IB, the inspector does not display the
outlet/action section.

Is this a bug?
I have installed Xcode on another computer and experienced the same
behaviour.

I am using Xcode3.2 and snow leopard.

(1) This is an Xcode question, not a Cocoa question, and belongs on the
Xcode list.

(2) Select *how*? Single-clicking an object in IB does not change what the
inspector shows; it is up to you to navigate the inspector. Double-clicking
an object in IB does not bring up a dialog where you can create outlets and
actions, as it did in earlier versions; instead, you create outlets and
actions in Xcode (in your header, in code) and IB automatically sees them.

m.

-- 
matt neuburg, phd = m...@tidbits.com, http://www.tidbits.com/matt/
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings



___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: IB does not show Outlet/Action section in inspector

2009-09-22 Thread Michael Süssner
Yeah, I also thought that the Xcode mailing list is the right one. But  
the list seams to be a little bit inactive.


I wanted to know if anyone else has detected the same behaviour.

To clarify, I have opened the identity view in the inspector panel and  
it does not display the add outlet/action section after I have  
selected an object. :-(


g
Michael

Am 22.09.2009 um 19:25 schrieb Matt Neuburg:


On Tue, 22 Sep 2009 08:57:14 +0200, Michael S?ssner
michael.suess...@utanet.at said:

When I select an object in IB, the inspector does not display the
outlet/action section.

Is this a bug?
I have installed Xcode on another computer and experienced the same
behaviour.

I am using Xcode3.2 and snow leopard.


(1) This is an Xcode question, not a Cocoa question, and belongs on  
the

Xcode list.

(2) Select *how*? Single-clicking an object in IB does not change  
what the
inspector shows; it is up to you to navigate the inspector. Double- 
clicking
an object in IB does not bring up a dialog where you can create  
outlets and
actions, as it did in earlier versions; instead, you create outlets  
and
actions in Xcode (in your header, in code) and IB automatically sees  
them.


m.

--
matt neuburg, phd = m...@tidbits.com, http://www.tidbits.com/matt/
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings






Mit freundlichem Gruß

Michael Süssner Dipl.-Ing.
Wimbergergasse 10-44
1070 Wien
Tel: +43 (1) 5268251
Mobil: +43 (676) 7955229



___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: IB does not show Outlet/Action section in inspector

2009-09-22 Thread Andy Lee
Are you having this problem with all objects or only instances of your  
own class? Did you use IBOutlet when you declared the outlets?  Maybe  
you could show us your header file.


Does it help if you force IB to re-read your header with File - Read  
Class Files...?


--Andy

On Sep 22, 2009, at 5:06 PM, Michael Süssner  
michael.suess...@utanet.at wrote:


Yeah, I also thought that the Xcode mailing list is the right one.  
But the list seams to be a little bit inactive.


I wanted to know if anyone else has detected the same behaviour.

To clarify, I have opened the identity view in the inspector panel  
and it does not display the add outlet/action section after I have  
selected an object. :-(


g
Michael

Am 22.09.2009 um 19:25 schrieb Matt Neuburg:


On Tue, 22 Sep 2009 08:57:14 +0200, Michael S?ssner
michael.suess...@utanet.at said:

When I select an object in IB, the inspector does not display the
outlet/action section.

Is this a bug?
I have installed Xcode on another computer and experienced the same
behaviour.

I am using Xcode3.2 and snow leopard.


(1) This is an Xcode question, not a Cocoa question, and belongs on  
the

Xcode list.

(2) Select *how*? Single-clicking an object in IB does not change  
what the
inspector shows; it is up to you to navigate the inspector. Double- 
clicking
an object in IB does not bring up a dialog where you can create  
outlets and
actions, as it did in earlier versions; instead, you create outlets  
and
actions in Xcode (in your header, in code) and IB automatically  
sees them.


m.

--
matt neuburg, phd = m...@tidbits.com, http://www.tidbits.com/matt/
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings






Mit freundlichem Gruß

Michael Süssner Dipl.-Ing.
Wimbergergasse 10-44
1070 Wien
Tel: +43 (1) 5268251
Mobil: +43 (676) 7955229



___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/aglee%40mac.com

This email sent to ag...@mac.com

___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: IB does not show Outlet/Action section in inspector

2009-09-22 Thread Bill Cheeseman


On Sep 22, 2009, at 5:06 PM, Michael Süssner wrote:

I have opened the identity view in the inspector panel and it does  
not display the add outlet/action section after I have selected an  
object.


In IB 3.2, this functionality was moved to the Library window. In the  
Library window, select the Classes tab, then in the bottom pane select  
the Outlets or Actions tab.



--

Bill Cheeseman
b...@cheeseman.name

___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: IB does not show Outlet/Action section in inspector

2009-09-22 Thread Shawn Erickson
On Tue, Sep 22, 2009 at 2:06 PM, Michael Süssner michael.suess...@utanet.at
 wrote:

Yeah, I also thought that the Xcode mailing list is the right one. But the
 list seams to be a little bit inactive.


Which xcode list you looking at? I see tens of emails a day on the Xcode
list.

This is the list you want...
http://www.lists.apple.com/mailman/listinfo/xcode-users

-Shawn
___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: IB does not show Outlet/Action section in inspector

2009-09-22 Thread Michael Süssner
I have the problem with every object even the one from the examples  
(Apple).


I have instantiated an NSObject from the IB Library and then I've  
tried to add an outlet. Still, no outlet section in the inspector  
(identity).

g
Michael

Am 22.09.2009 um 23:23 schrieb Andy Lee:

Are you having this problem with all objects or only instances of  
your own class? Did you use IBOutlet when you declared the outlets?   
Maybe you could show us your header file.


Does it help if you force IB to re-read your header with File -  
Read Class Files...?


--Andy

On Sep 22, 2009, at 5:06 PM, Michael Süssner michael.suess...@utanet.at 
 wrote:


Yeah, I also thought that the Xcode mailing list is the right one.  
But the list seams to be a little bit inactive.


I wanted to know if anyone else has detected the same behaviour.

To clarify, I have opened the identity view in the inspector panel  
and it does not display the add outlet/action section after I have  
selected an object. :-(


g
Michael

Am 22.09.2009 um 19:25 schrieb Matt Neuburg:


On Tue, 22 Sep 2009 08:57:14 +0200, Michael S?ssner
michael.suess...@utanet.at said:

When I select an object in IB, the inspector does not display the
outlet/action section.

Is this a bug?
I have installed Xcode on another computer and experienced the same
behaviour.

I am using Xcode3.2 and snow leopard.


(1) This is an Xcode question, not a Cocoa question, and belongs  
on the

Xcode list.

(2) Select *how*? Single-clicking an object in IB does not change  
what the
inspector shows; it is up to you to navigate the inspector. Double- 
clicking
an object in IB does not bring up a dialog where you can create  
outlets and
actions, as it did in earlier versions; instead, you create  
outlets and
actions in Xcode (in your header, in code) and IB automatically  
sees them.


m.

--
matt neuburg, phd = m...@tidbits.com, http://www.tidbits.com/matt/
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings






Mit freundlichem Gruß

Michael Süssner Dipl.-Ing.
Wimbergergasse 10-44
1070 Wien
Tel: +43 (1) 5268251
Mobil: +43 (676) 7955229



___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/aglee%40mac.com

This email sent to ag...@mac.com




Mit freundlichem Gruß

Michael Süssner Dipl.-Ing.
Wimbergergasse 10-44
1070 Wien
Tel: +43 (1) 5268251
Mobil: +43 (676) 7955229



___

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.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com