Height parameter is 'grayed out' in interface builder?

hello, i would like to alter the height of my newly created view in my .xib file, and although the view is selected the height parameter is 'grayed out' in interface builder?, any one know why ?

Anything here?
Xcode 4 User Guide

Similar Messages

Interface Builder - Locking Properties

Good morning all,
I have some question about the feature to lock properties in Interface builder. I am using Interface Builder 3.0 (629) and I am not sure if the behavior I am seeing is a bug or if it is just some small details I am unaware of. Here is my little annoying problem:
Whenever I open some of my nib files ( they are now all saved as NIB 3.0) some of them instantly are flagged as something changed, and some don't.
1: I can't figure out why Interface Builder thinks that. The only thing I can think of, is that I might have created the Nib file on a primary monitor ( I am developing a Macbook pro) and sometimes I might have created the Nib file on a second monitor. Is it because Interface Builder is relocating the Nib file on the 2nd monitor ( which has the Dock) that he thinks something has changed??
2: Also, when I am trying to lock the nib files using Non-Localizable properties, on some NSTextField it still does not let me edit the text.
3: Whenever some locking is applied, I have the same issue as in (1), Whenever I open up a locked Nib file, I see the big LOCK image flashing. ( I think interface builder is trying to do something) And on some NIB file it is fine.
I also noticed that when my Nib files were saved as Nib 2.0 I could not save the deployment Target OS.
Thanks for confirming my doubt or explaining these undocumented behavior if they are not!
Simon

Nothing beyond what Apple's already released or said in the press releases is known, or can be discussed, by anyone here. Sorry, but we'll all have to wait and see.
As to individuals writing their own apps, again, we'll have to wait and see, but there's no indication that Apple will support this anytime in the foreseeable future. Their emphasis is on providing apps that won't totally screw up an iPhone, so therefore I'd I doubt strongly that Apple's going to want to support iPhone on which any of us can install anything we happen to cook up.
Regards.

Dear God... PLEASE HELP... Selection Hieght value is grayed out.

I dont know whats up with this... but all of a sudden today, in my flash cs4 (mac and PC versions) When i go to open a fla in flash to work on it, i select a text box... in the properties window under position and size --- HIEGHT-(selection hieght) value is grayed out... I opened fla's that i had don before but this also now affects them as well. I tried opening on my PC .. now it does the same thing. Every file i open now.. when i got to the properties of a text box ... the height values are grayed out. I am using Palatino roman font... in a simple text box.
Position and size:
x:20 y:15
w:264 H:335.2 <-------- grayed out!!!
I have opened these files in cs3... and that now is also experiencing this......
PLEASE HELP... Im in the middle of a project --- with extreme deadlines...
PLEASE PLEASE PLEASE

Sorry.. left out some important info
I am running MAC os Snow Leopard
Runing XP pro as well.. looks like once file is from Mac Snow Leopard to the XP the problem is also now in CS4/CS3 in the windows system too...
Noticed this post :
??? related problem
Hi, i am experiencing a strange and unpleasant situation.
I am using CS3 and upgraded to Snow Leopard 10.6.2 last night, along downloading the latest Flash Player for browsers.
Problem is that now all of my text block arent displaying the same line height that before i updated?????
I compared the same exact SWF made under Tiger and those made under Snow Leopard and the two arent identical, lines are misaligned regarding line height!
What gives? Flash or OSX interpreting fonts differently?
Thanks!

How to make selection parameter gray out, not changeble mode

Hi Experts,
Selection screen having parameters, I am putting default values in that parametrs.
How to make this parameter gray out, not changeable mode.
Thanks in advance
mahahe.
See comments below
Edited by: Rob Burbank on Jul 1, 2009 12:43 PM

Hi,
For the parameters required, while declaring them use the MODIF ID, lets say you have choosen the modif id as SC1.
i.e. parametes: p_mat type matnr DEFAULT '100' MODIF ID SC1.
Then in the initialization event, code as below.
    LOOP AT SCREEN.
      IF screen-group1 = 'SC1'.
        screen-input = '0'.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
It will work.
Regards,
Nangunoori.

Outline Build-Move Members in Dimension Properties is grayed out

Hi, I'm very new with EIS and created a sample meta outline. Everytime I add a member name below a Dimension in the meta outline, EIS does not allow me to check "Move Members" in the "Duplicate Member Name" area from the Outline Build tab. When I delete the member names just added to the Dimension, the "Move Members" would be available to be checked (not grayed out).
Any help would be great, thank you!

Hi there
I believe the Fit to Stage button only becomes available if the image is larger than the stage itself. If you insert an image that is smaller than the stage, it will not enable and maximize the image to fill the stage area if that's what you were hoping to do.
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

I'm getting a very low signal from my Blackbird interface. The fire wire connection is selected properly and track recording sliders set. However the recording level slider in the lower right corner is grayed out. How can I get better signal?

I'm getting a very low signal from my Blackbird interface. The fire wire connection is selected properly and track recording sliders set. However the recording level slider in the lower right corner is grayed out. How can I get better signal?

If it's slow on startup it would be extensions loading or LaunchDaemons starting up.
You should have a look in:
/Library/LaunchDaemons
/Library/Extensions
You can count out anything in your home folder and it shouldn't put anything in /System as that's reserved for Apple.

Volume slider in track info grays out with audio interface

I'm using a Presonus Inspire interface for mic and guitar. But in new tracks, the volume slider in track info grays out when I plug it in. Prefs recognizes the interface and I set audio in and out on Inspire. Signal comes through the headphones, but no signal in GB because the volume slider in track info is all the way to the left and grayed out.
Ideas?
Thanks!
Jim

http://www.bulletsandbones.com/GB/GBFAQ.html#volumesliderdimmed
http://www.bulletsandbones.com/GB/GBFAQ.html#selectinterface

Rotate Format Field 180. Height Grays out and changes from 2 to 1????

Is there a reason why when I create a Format Field with a height of 2, and then when I rotate the field 180, then the height changes to 1 and can not be changed. (Grayed out).
Is there anyway to make the height back to 2? Strange why this would happen.
I'm using v5.5.1.280.
Thanks

Well, I was about to send the email but before doing so I decided to see what the software says about rotating. Here a quote from the help system:
>Output Designer does not support the rotation of multiple-line fields. If the rotate property for a multiple-line field is changed to something other then 0 (the default), Output Designer will automatically convert the multiple-line field to a single-line field. At the same time, Output Designer will gray out the height property for the field.
There doesn't seem to be a text rotation property but the help system states:
>Rotated text labels are restricted to a single line, using a single font. Output Designer converts a multi-line text label to a single line when rotated.
My guess is that the programming team was able to rotate the field but ran into a problem keeping the height so they documented the restriction.
It looks like to get multiple lines there will just have to be multiple fields and some way to split up the data into those fields.

Multi page tiling grayed out?

So I'm trying to save a lot of work recombining individual pages by doing a project as 1 sheet in illustrator (CS3) and then printing it to a PDF. But, I cannot click the Create Multi-page PDF from Page Tiles option in the General section like the instructions say to, because it is grayed out. Is there some overarching setting that I need to reinstall, or am I missing something?
I've also tried just printing to the PDF and that just causes Illustrator to crash.
Thanks,
Eric

There's your problem. You only have one tile. The document is not set up for tile printing.
Page Tiling is a print setting. It tells the printer to print the document in tiles that are the size of your supposed media (the size of the sheets you ostensibly have loaded in the printer).
Just for clarity do this:
1. Assume you want to build a document that will export as a PDF with 16 vertical letter-size pages. File>New.
2. In Document setup, set the height to 11" and width to 8.5". But then key in "*2" after the 11 and key in "*8" after the 8.5. Click outside the field and you'll see the Artboard size change to 22" x 68". Click OK.
3. View>Show Page Tiling. You'll only see one page tile.
4. File>Print>General pane. Select Adobe PDF as the "printer". Set Media size to Custom, portrait, width 8.5", height 11".
5. Click Setup to switch to the Setup pane. Select Tile Full Pages from the Tiling popup. Click Done.
You'll now see a 22" x 68" Artboard with 16 numbered Page Tiles. If you Save A Copy as PDF, you'll have the option to Save Tiles as Separate Pages.
JET

/SAPAPO/OM_LC_DOWNLOAD_UPLOAD section C grayed out

I have recently completed an unicode conversion of our SCM 7.0 system. On the source I ran sections A and B, then did the unicode conversion. On the target I did a fresh install of liveCache and made it the same build. I followed the info in note 632357
I have then tried this process two ways, but the first way which I thought was what I needed to do caused many issues.
The first process.
I used the commands below to get the parameters set in the target install the same as they were in the source.
$ dbmcli -u control,##### -d APT
$ db_drop
$ dbmcli db_create APT control,######
$ dbmcli -u control,###### -d APT
dbmcli on APT> medium_put APT_BACKUP /tmp/APTinst/APT.backup FILE DATA 0 8 YES
dbmcli on APT> service_connect
dbmcli on APT> recover_config APT_BACKUP
dbmcli on APT> service_release
The parameters seemed to work, but the problem I had was trying to get the datafiles created. The source had 16 datafiles so I was trying to create the targets 16 datafiles. I ran the below command for that and it said ok, but never actually created them.
dbmcli on APT> param_addvolume 1 DATA /sapdb/APT/sapdata1/DISKD0001 F 262144
dbmcli on APT> param_addvolume 2 DATA /sapdb/APT/sapdata1/DISKD0002 F 262144
dbmcli on APT> param_addvolume 3 DATA /sapdb/APT/sapdata1/DISKD0003 F 262144
dbmcli on APT> param_addvolume 4 DATA /sapdb/APT/sapdata1/DISKD0004 F 262144
dbmcli on APT> param_addvolume 5 DATA /sapdb/APT/sapdata1/DISKD0005 F 262144
dbmcli on APT> param_addvolume 6 DATA /sapdb/APT/sapdata1/DISKD0006 F 262144
dbmcli on APT> param_addvolume 7 DATA /sapdb/APT/sapdata1/DISKD0007 F 262144
dbmcli on APT> param_addvolume 8 DATA /sapdb/APT/sapdata1/DISKD0008 F 262144
dbmcli on APT> param_addvolume 9 DATA /sapdb/APT/sapdata1/DISKD0009 F 262144
dbmcli on APT> param_addvolume 10 DATA /sapdb/APT/sapdata1/DISKD0010 F 262144
dbmcli on APT> param_addvolume 11 DATA /sapdb/APT/sapdata1/DISKD0011 F 262144
dbmcli on APT> param_addvolume 12 DATA /sapdb/APT/sapdata1/DISKD0012 F 262144
dbmcli on APT> param_addvolume 13 DATA /sapdb/APT/sapdata1/DISKD0013 F 262144
dbmcli on APT> param_addvolume 14 DATA /sapdb/APT/sapdata1/DISKD0014 F 262144
dbmcli on APT> param_addvolume 15 DATA /sapdb/APT/sapdata1/DISKD0015 F 262144
dbmcli on APT> param_addvolume 16 DATA /sapdb/APT/sapdata1/DISKD0016 F 262144
I then went back into se38 and ran /SAPAPO/OM_LC_DOWNLOAD_UPLOAD, but the buttons for section C are all grayed out.
The second process was to use what the fresh target install created with no parameter changes, but I then went back into se38 and ran /SAPAPO/OM_LC_DOWNLOAD_UPLOAD, but the buttons for section C were still all grayed out.
Thanks

Hello Natalia,
I have an issue with step C4-loading LiveCache transactional data in section C.
We are in the process of upgrading our SCM5.0 system to release SCM7.0. Our source livecache version is 7.6.03.12 and target livecache version we are upgrading to is 7.7.04.29. We are in the downtime phase of the upgrade, executing the post LiveCache upgrade C1-C11 steps in Section C.
During step C4 when uploading LiveCache transaction data, we are running into an error CONNE_IMPORT_WRONG_COMP_TYPE. The dump says that "when importing the object 'OT_ORDERS", the component no. 5 in the dataset has a different type from the corresponding component of the target object in the program "/SAPAPO/SAPLOM_UPGR_PARALLEL". The data type is "P" in the dataset, but "C in the program"
We are running AIX5.3 and Oracle 10.2.0.2.0.
I would appreciate if you can provide some help or pointers on how this issue can be addressed. Thank you!
Please see below for some information from the ST22 dump
Error analysis |
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in
procedure "GET_DB" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
When importing the object "OT_ORDERS", the component no. 5 in the
dataset has a different type from the corresponding component
of the target object in the program "/SAPAPO/SAPLOM_UPGR_PARALLEL".
The data type is "P" in the dataset, but "C" in the program.
Information on where terminated
Termination occurred in the ABAP program "/SAPAPO/SAPLOM_UPGR_PARALLEL" - in
"GET_DB".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 3222
of the (Include) program "/SAPAPO/OM_UPG_CLASS_IMPCLUT".
The termination is caused because exception "CX_SY_IMPORT_MISMATCH_ERROR"
occurred in
procedure "GET_DB" "(METHOD)", but it was neither handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "/SAPAPO/SAPLOM_UPGR_PARALLEL "; its source code
begins in line
| 3221 of the (Include program "/SAPAPO/OM_UPG_CLASS_IMPCLUT ".

Interface Builder Assertion Failure at initialization/startup

Interface Builder appears to be unusable...
I get four (4) alert messages at the start of running Interface Builder:
====
Interface Builder encountered an internal logic error. Choose "Continue" to continue running Interface Builder in an inconsistent state. Choose "Crash" to halt Interface Builder and file a bug with Crash Reporter. Choosing "Crash" will result in the loss of all unsaved data.
====
Selecting (Show Details) I get:
====
Assertion Message: Interface Builder encountered an error communicating with the iPhone Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
IBUIViewImageRequester failed to rasterize a UILabel, UIButton, UITextField, and UISegmentedControl.
Exception name: NSInternalInconsistencyException
Exception reason: [NOTE: this exception originated in the server.]
Invalid parameter not satisfying: font != nil
Exception backtrace:
0. CoreFoundation 0x30279dfb [NSException initWithName:reason:userInfo:]
1. libobjc.A.dylib 0x92750e3b objcexceptionthrow
2. CoreFoundation 0x3028e5fb CFReadStreamGetBuffer
3. Foundation 0x305b0594 [NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:]
4. UIKit 0x309fe074 [UILabel setFont:]
5. UIKit 0x309fec08 [UILabel _commonInit]
6. UIKit 0x309fd13c [UILabel initWithFrame:]
7. Interface Builder Cocoa Touch Tool 0x00008655 [UIView initWithMarshalledValues:orderedKeys:marshallerClassNames:andMarshallerInstanti ationContexts:globalMarshallingContext:]
8. Interface Builder Cocoa Touch Tool 0x0000b307 [IBCocoaTouchToolObjectPackage dealloc]
9. Interface Builder Cocoa Touch Tool 0x0000b80f [IBCocoaTouchToolObjectPackage initWithData:]
10. Interface Builder Cocoa Touch Tool 0x0000a5a1 [IBCocoaTouchToolObjectPackage dealloc]
11. Interface Builder Cocoa Touch Tool 0x00002c74 [IBCocoaTouchTool produceImageForRequest:]
12. Interface Builder Cocoa Touch Tool 0x00002445 [IBCocoaTouchTool produceImagesForRequests:]
13. CoreFoundation 0x3024a10d CF_forwarding_prep0
14. CoreFoundation 0x30249ff8 [NSInvocation invoke]
15. CoreFoundation 0x3026eaf8 [NSInvocation invokeWithTarget:]
16. CoreFoundation 0x3026e094 [NSDate initWithTimeIntervalSinceNow:]
17. CoreFoundation 0x3024a0a2 CF_forwarding_prep0
18. CoreFoundation 0x3024a10d CF_forwarding_prep0
19. CoreFoundation 0x30249ff8 [NSInvocation invoke]
20. Foundation 0x3053e15d [NSConnection dispatchInvocation:]
21. Foundation 0x3053c307 [NSConnection handleRequest:sequence:]
22. Foundation 0x3053ba13 [NSConnection handlePortCoder:]
23. Foundation 0x3053b5be [NSConcretePortCoder dispatch]
24. Foundation 0x3053ae33 [NSDOStreamData bytes]
25. CoreFoundation 0x30246e79 CFRunLoopRemoveObserver
26. CoreFoundation 0x30245560 CFRunLoopRunSpecific
27. CoreFoundation 0x30244628 CFRunLoopRunInMode
28. Foundation 0x30535525 [NSRunLoop runMode:beforeDate:]
29. Interface Builder Cocoa Touch Tool 0x000020af [IBCocoaTouchTool startServingForPortName:]
30. Interface Builder Cocoa Touch Tool 0x00002e77 [IBCocoaTouchTool produceImageForRequest:]
Exception info:{
Backtrace:
0. Interface Builder 0x00004d29 [IBApplication handleAssertion:inFile:onLine:]
1. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
2. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
3. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
4. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
5. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
6. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
7. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
8. AppKit 0x906e4d0d _DPSNextEvent
9. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
10. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
11. AppKit 0x9092192b [NSApplication _realDoModalLoop:peek:]
12. AppKit 0x9091c069 [NSApplication runModalForWindow:]
13. InterfaceBuilderKit 0x00382511 [IBDetailedAlert runModal]
14. Interface Builder 0x00004dd6 [IBApplication handleAssertion:inFile:onLine:]
15. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
16. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
17. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
18. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
19. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
20. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
21. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
22. AppKit 0x906e4d0d _DPSNextEvent
23. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
24. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
25. AppKit 0x9092192b [NSApplication _realDoModalLoop:peek:]
26. AppKit 0x9091c069 [NSApplication runModalForWindow:]
27. InterfaceBuilderKit 0x00382511 [IBDetailedAlert runModal]
28. Interface Builder 0x00004dd6 [IBApplication handleAssertion:inFile:onLine:]
29. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
30. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
31. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
32. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
33. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
34. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
35. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
36. AppKit 0x906e4d0d _DPSNextEvent
37. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
38. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
39. AppKit 0x9092192b [NSApplication _realDoModalLoop:peek:]
40. AppKit 0x9091c069 [NSApplication runModalForWindow:]
41. InterfaceBuilderKit 0x00382511 [IBDetailedAlert runModal]
42. Interface Builder 0x00004dd6 [IBApplication handleAssertion:inFile:onLine:]
43. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
44. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
45. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
46. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
47. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
48. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
49. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
50. AppKit 0x906e4d0d _DPSNextEvent
51. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
52. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
53. AppKit 0x906dd5fb [NSApplication run]
54. AppKit 0x906aa834 NSApplicationMain
55. Interface Builder 0x00004eca [IBApplication changeInspectorMode:]
====
If I press (Continue) and then try to create any fields which need text, such as a label or button, I get the exact same alert window, and nothing "appears to work" as far as getting past this.
Some background...
I have no problems like this on my PPC development platform, just on my Intel-based system.
Configuration:
Intel hardware, 1.6 Ghz, 2GB, Mac OS/X 10.5.7
Originally I installed the the devtools from: xcode3122621developerdvd.dmg
and the 2.0 or 2.1 iPhone SDK, but never used Interface Builder (long story)
When the final SDK for 3.0 came out, I installed that from:
iphonesdk_3.0_leopard_9m2736final.dmg
A few days ago, I said, OK, enough reading, I'm ready to start on my application, and fired up Xcode, created a new project and double-clicked on the .xib file to build my interface.
That's when I first saw this problem... and now I'm stuck.
What I've done since...
#1) Deleted prefs for Interface Builder (ibtool), and XCode
retried... same error
#2) wiped /developer clean and resinsatlled from iphonesdk_3.0_leopard_9m2736final.dmg
retried... same error
retried #1, retried, same error
#3) ran /Volumes/Olórin/Developer/Library/uninstall-devtools --mode=all
rebooted
checked international to make sure US/English was selected
repaired disk permissions
rebooted
verified, no prefs files in ~/Library/Preferences or /Library/Preferences
retried... same error
HELP!!!

! ! ! - O M G - ! ! !
{quote:title=reststop wrote:}
#3) ran /Volumes/Olórin/Developer/Library/uninstall-devtools --mode=all
{quote}
I was about to post a reply which included the entire crash log for details... and saw this line:
7/21/09 12:44:16 AM [0x0-0x28028].com.apple.InterfaceBuilder3[269] Couldn't read font cache (file://localhost/Volumes/Olo%C3%83%C3%85rin/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0. sdk/System/Library/.lilid/.lili).
The file is there, so why can't it read it... uh oh, not exactly
... I typed /Olórin/ not /Olo%C3%83%C3%83rin/
Apparently somewhere internal to Interface Builder, when it translates characters, it does it TWICE,
so instead of 'ó' (that's 'option-e o', we have 'o%C3%83%C3%83' which may have worked if it had
only been '%C3%83', without the extra o, or the extra %C3%83.
I am so glad I found this, but I'm furious at Apple for making me rebuild my development system 3 times!
...someone really needs to do better QA on a product used by so many users.
I changed the name of my disk from Olórin to Olorin and Interface Builder works fine!
The PROBLEM all along was the name of my development disk ! ! !
Someone at Apple, please NOTE!
Someone please tell me how to report this, and maybe get Apple to hire me even if just for better QA!
-Carl

Interface Builder w/ Xcode folder refs

when i set up xcode with folder refs interface builder does not see my images in the dropdown list. i actually have to type out the path and ib will show a broken image. is there anyway to fix this?

Note that *AppleScript Studio* has been deprecated in Snow Leopard - AppleScriptObjC is the new framework. You can still edit Studio projects, but the project templates have been removed and you will need to enable the AppleScript palette - see the release notes.
Assigning a handler (IBaction) to a button (or any object) is pretty easy - create a handler in your script that takes a single parameter and name it with a trailing underscore (the naming conventions are also in the release notes), for example:on doButtonStuff_(sender) it will appear in *Interface Builder* under the *Connections Inspector* for your application delegate - from there you can make a connection from your object to the handler. MacScripter has some tutorials for AppleScriptObjC in Xcode, and I also have a button example project (it's not much of a tutorial, though).

After answering the three security questions on itunes connect the submit button is still grayed out. It looks like it could be an error on the website. Has anyone encountered this issue?

After answering the three security questions to update an app on itunes connect the submit button is grayed out. It looks like an error on the website. Has anyone ran into this problem before? Any help would be greatly appreciated.

Hi evanVIT,
Welcome to the Apple Support Communities!
I understand that issues like the one you are experiencing can be very frustrating. For this situation however, for update errors in the range of 3000-3020, I would recommend the troubleshooting steps located in the attached article. Please use the steps and information as a reference.
Error 3194, Error 17, or "This device isn't eligible for the requested build"
Cheers,
Joe

Load Class in Interface Builder 3

Hello,
i am trying to get started with Cocoa after having worked a while with Xcode & smaller AppleScript based projects.
As my idea was to create a menubar-based (NSStatusItem) service app for myself i started with this tutorial:
http://files.semaja2.net/NSStatusItem%20-%20ObjC.html
Unfortunaly it seems like there was a change in Interface Builder regarding loading Classes from Version 2 to IB version 3
The tutorial tells me to (about the middle of the tutorial):
Rename the “NSMenu1” to “StatusItem”, following this in “Interface Builder” >>choose from the menu “Classes > Read Files..” now select the AppController.h >>file, Once the file has been read it should change out project view to “Classes” >>from here find the AppController item and right click on it and select >>“Instantiate AppController”:
I was able to follow the tutorial until there without problems but it looks like the Classes-Tab is gone in IB 3.x.
So i feel somehow unable to finish this small tutorial.
how would i do this step in Interface Builder 3.x ?
Any help is heavily appreciated.
Best regards
fidel

fidel-castro wrote:
I was able to follow the tutorial until there without problems but it looks like the Classes-Tab is gone in IB 3.x.
So i feel somehow unable to finish this small tutorial.
how would i do this step in Interface Builder 3.x ?
You're right, this has changed. I'm currently using IB 3.1.1 but I believe the changes appeared in IB 3.
Once you've done the "Read class files" and selected your AppController.h file IB should know about your class.
In order to instantiate your AppController in IB first go to the Library window and find the "NSObject" (it will appear as a blue cube). Drag one of these NSObject's from the Library window and drop it into your MainMenu.xib window along with the other icons that appear there (File's Owner, First Responder, Application... etc).
Now you will have created an instance of an NSObject in your MainMenu.xib file. And, since your AppController class is a subclass of NSObject (and IB knows this since you've had it read in your AppController.h file) you can now change this NSObject instance into an instance of your AppController.
Select the NSObject icon in the MainMenu.xib window then go to IB's Inspector window and click on the next to last icon in the top tool bar. This should change the Inspector window's title bar to say "Object Identity" and the Class Identity in the first text field should be set to NSObject. You should be able to type "AppController" into this field (or click the popup and it should show up in the popup list. Once you've done this it will transform the NSObject instance into an AppController instance.
You'll see another slight difference between IB 3.x and the tutorial when you do the <Control>-Drag between items to connect up the outlets and actions. Instead of finalizing the connections in the Inspector window like the tutorial says you'll get a small popup window right next to the item you're connecting to that will list the available outlets/actions you can connect to. Simply click the one you want. You can still double-check your connections in the inspector window though.
Steve

Looking for simple sample of iphone apps without using Interface Builder

I successfully went through the 'iphone app tutorial' and used Interface Builder, but now want to try creating apps without it.
The UI Catalog sample is too complex, but didn't see anything that just had a view and a button or label.
Ideally I want code that doesn't require any IB usage, but I can't tell if that is possible yet...
Anyone have a link to an easy sample?
Or has anyone created a test app themselves and wouldn't mind posting?
I took a stab at creating one and posted it on the "101" forum, but it would be hard for somebody to try and figure out what I was attempting
Thx for any links/___sbsstatic___/migration-images/migration-img-not-avail.png
ps
I really need a good book, especially "cookbook" style

hey dear
I have one solution of your problem
just go to in iphone developer search for FAQ
In faq their is one section how to use prohramming in this you can see
the how to ceate label,button etc.
after that simply add the view or remove theview.

Height parameter is 'grayed out' in interface builder?

Similar Messages

Maybe you are looking for