|
Welp, turns out I hadn't supplied a terms and conditions link for all five localisations... my bad.
|
#
?
Sep 14, 2014 16:55
|
|
|
|
| # ? Jun 5, 2024 13:28 |
|
|
Removed Text because I broke the page. EDIT: Disregard this. The server logs were being cluttered by another persons problem. The server is getting the certificate and the problem seems to lie further down the line in their server code. I feel less crazy. mrbass21 fucked around with this message at 19:16 on Sep 16, 2014 |
|
#
?
Sep 15, 2014 20:39
|
|
|
I'm following the Ray Wenderlich tutorials and I don't think I understand this passage.Ray Wenderlich posted:Finally, select your table view, and select the sixth Inspector (the Connections Inspector). You’ll see two entries for dataSource and delegate – drag the buttons to the right of those over to your view controller in the Document Outline. As in I don't know where to control-drag to.
|
|
#
?
Sep 15, 2014 21:39
|
|
|
PleasureKevin posted:I'm following the Ray Wenderlich tutorials and I don't think I understand this passage. Typically you want to control drag to your ViewController's class extension category, which would be on top of your implementation (.m) and look something like: code:edit: doh, I misunderstood - I thought you were asking about IBOutlets, but that doesn't look like that is the case. I think it's telling you to drag to your view controller (it's probably on the left side of your xib/storyboard, with a yellow circle next to its name)
|
|
#
?
Sep 15, 2014 21:52
|
|
|
PleasureKevin posted:I'm following the Ray Wenderlich tutorials and I don't think I understand this passage. On the left side of interface builder, you probably see a vertical bar of icons about 48px wide. At the bottom of that bar, to the right, should be a little right-pointing arrow, which will expand that bar into a full outline of everything in your view with full names. That's the Document Outline.
|
|
#
?
Sep 15, 2014 21:55
|
|
|
So who else has an extension/widget that probably won't work tomorrow? https://devforums.apple.com/thread/245432?tstart=0
|
|
#
?
Sep 16, 2014 21:29
|
|
|
This is not really programming related but, is it normal for all prices to appear in US dollars on the Korean iTunes store? Is there any case where we would want the prices to appear in won?
|
|
#
?
Sep 16, 2014 22:16
|
|
|
I foresee a lot of pain in my future with universal storyboards. I've spent the past couple of days just trying to get this one stupid square resizing to stay 1:1 and adjust a few labels and images and such all around it on both 4 and 3.5 inch screens. I'm about to rip my dick off in frustration. Of course it's a subview in a xib by itself, so I can't use the preview pane to help, as far as I can tell. I think I have some kind of mental block when it comes to constraints. I set everything up right but end up somehow putting a constraint on a tiny UI element that ends up propagating all the way up through every view and making everything in the wrong place again.
|
|
#
?
Sep 17, 2014 00:45
|
|
|
So iTunes Connect, it sucks, but it's been working fine until I upgraded to the 6.1 Xcode GM. Now I'm trying to submit something tonight and getting hit with this useless error on the last step:  I can login to iTunes Connect fine with the same credentials. According to google it could be five hundred different things, including trouble on Apple's end. I've been at it for hours and I'm out of ideas. Anything?
|
|
#
?
Sep 17, 2014 03:01
|
|
|
NOTinuyasha posted:6.1 Xcode GM On the off-chance that this isn't simply a typo: are you submitting with the Xcode 6.0 GM? 6.1 hasn't hit GM yet and shouldn't be used for submission.
|
|
#
?
Sep 17, 2014 04:55
|
|
|
That's a typo, I meant 6.0.
|
|
#
?
Sep 17, 2014 04:56
|
|
|
Is there some way to get Xcode to build an archive suitable for a device when I have an unsuitable device plugged in? For example, I can't find a way to submit an app requiring iOS 8 while an iPhone 4 is plugged in. If I pick a simulator then I can't pick "Archive", and if I pick the only device listed, the iPhone, then "the run destination iPhone is not valid for Archiving". Maybe I can permanently enable the generic "iOS Device" menu item? NOTinuyasha posted:That's a typo, I meant 6.0. Ah, ok. I'm out of ideas then, sorry!
|
|
#
?
Sep 17, 2014 05:24
|
|
|
As long as "Build active architecture only" is turned off for the build configuration used by the archive action/scheme/whatever then I don't think it matters. You basically just have to be telling it you want to build for the actual device.
|
|
#
?
Sep 17, 2014 05:38
|
|
|
Doc Block posted:As long as "Build active architecture only" is turned off for the build configuration used by the archive action/scheme/whatever then I don't think it matters. You basically just have to be telling it you want to build for the actual device. I'm stuck at the actual "archive action" step. If I plug in an iPhone 4 by itself, I seemingly can't perform the archive action.
|
|
#
?
Sep 17, 2014 06:04
|
|
|
pokeyman posted:I'm stuck at the actual "archive action" step. If I plug in an iPhone 4 by itself, I seemingly can't perform the archive action. You should be able to do what you want on the command line; you can specify a generic iOS device destination that way.
|
|
#
?
Sep 17, 2014 06:33
|
|
|
pokeyman posted:I'm stuck at the actual "archive action" step. If I plug in an iPhone 4 by itself, I seemingly can't perform the archive action. Odd. Just to throw my datapoint in there, I didn't have a problem archiving after I selected the application target and generic 'iOS Device' earlier today.
|
|
#
?
Sep 17, 2014 08:04
|
|
|
Anyone know anything about Cocos2D? I'm using version 2, and I'm moving tiles by pointing it to a CCSprite and changing the position. Unfortunately it still behaves as if the tile is in it's old location (I can test and see that a tile is there) even though graphically the position has moved.code:LP0 ON FIRE fucked around with this message at 16:25 on Sep 17, 2014 |
|
#
?
Sep 17, 2014 15:17
|
|
|
eschaton posted:You should be able to do what you want on the command line; you can specify a generic iOS device destination that way. Oh right, there's some new(ish?) flags for xcodebuild. That'll have to do! Doctor w-rw-rw- posted:Odd. Just to throw my datapoint in there, I didn't have a problem archiving after I selected the application target and generic 'iOS Device' earlier today. Right, that works for me too. It's when I have an unhelpful device plugged in, so the generic "iOS Device" is replaced by e.g. "iPhone 4", that I cannot choose the Archive action.
|
|
#
?
Sep 17, 2014 17:28
|
|
|
I saw that in iOS 8, Mail is getting a swipe left action on its table view cells. Are us mortals getting a hook in UITableView for that, or do we have to create our own implementation?
|
|
#
?
Sep 17, 2014 17:46
|
|
|
Today, I figured out that -[NSNumber isEqualToNumber:] crashes on nil. That is to say:Objective-C code:code:code:
|
|
#
?
Sep 17, 2014 20:17
|
|
|
pokeyman posted:Is there some way to get Xcode to build an archive suitable for a device when I have an unsuitable device plugged in? For example, I can't find a way to submit an app requiring iOS 8 while an iPhone 4 is plugged in. If I pick a simulator then I can't pick "Archive", and if I pick the only device listed, the iPhone, then "the run destination iPhone is not valid for Archiving". Unplug and select iOS Device. That's what I always do just on general principal.
|
|
#
?
Sep 18, 2014 00:40
|
|
|
Am I trying to do something stupid with constraints? I want a vertical space above a view that has a minimum value but can grow if other constraints force the issue (meaning the space grows and the view shrinks). I wanted to do this with two constraints, but this seems impossible. IB will not allow me to create it, and if I do so manually in XML, Xcode crashes whenever I open the file.
If I neglect the equals constraint with 500 priority, the view starts tiny with way too much space. I want it to start big and shrink only if needed. edit: Of course, as soon as I post this, I find another constraint to do the job. I made a 500 priority constraint for the view's height instead of the space above it. This ends up having the exact same effect, but it does it without having two constraints on the same dimension with different values. I'm still curious if the above is a bug or if I am abusing autolayout. ManicJason fucked around with this message at 02:02 on Sep 18, 2014 |
|
#
?
Sep 18, 2014 01:59
|
|
|
Doctor w-rw-rw- posted:Am I crazy to expect those to work like isEqual: instead of crashing? I don't think so, but maybe someone on the Foundation team violently disagrees with you. If you want to cite things in your bug report, I believe -[NSString isEqualToString:] gracefully handles nil. Ender.uNF posted:Unplug and select iOS Device. That's what I always do just on general principal. Alright. It just feels wrong somehow, like I'm missing something.
|
|
#
?
Sep 18, 2014 03:02
|
|
|
I'm learning the hard way that autolayout is a horrible mistake if you have anything remotely complicated or not stock UIKit. I want the last week of my life back. I especially love how it seems to randomly decide to shift everything around by 0.5 and that breaking when it happens just shows you bog standard CALayer things with no hint as to why in the world autolayout just had a stroke. ManicJason fucked around with this message at 04:42 on Sep 18, 2014 |
|
#
?
Sep 18, 2014 04:39
|
|
|
That's how I would do it. Let the height constraint be lower priority so it gets sacrificed if needed. ManicJason posted:I'm learning the hard way that autolayout is a horrible mistake if you have anything remotely complicated or not stock UIKit. I want the last week of my life back. Don't give up. Autolayout is cool and powerful, but you have to approach it in a completely different way. I wish I could come up with a good explanation. Once you "get" it, creating complicated layouts is fairly easy. For the record I tried to learn and use it three times and gave it up as bullshit twice before it stuck.
|
|
#
?
Sep 18, 2014 05:09
|
|
|
I understand the advantages of auto layout when it comes to bog standard UI. The problem is that I have a giant chain of custom views. I'm sure this is all because I didn't perfectly follow the UIView contract to handle resizing/redrawing, and I'm paying the price big time right now when using auto layout. This project turned into a giant mess in a hurry. There is core animation stuff being drawn based on coordinates converted from other views. That kind of thing is where auto layout is boning me when it twitches around and causes me to redraw stuff.
|
|
#
?
Sep 18, 2014 05:20
|
|
|
Ender.uNF posted:Don't give up. Autolayout is cool and powerful, but you have to approach it in a completely different way. I wish I could come up with a good explanation. Once you "get" it, creating complicated layouts is fairly easy. For the record I tried to learn and use it three times and gave it up as bullshit twice before it stuck. Having in the past dealt with its opaque resolution scheduling, and having just dealt with nonsensical and seemingly irrecoverable constraint failure of a layout defined by someone else, I would call it "cool and powerful" in the same way regular expressions are: Autolayout constraints seem to be mostly write-only, the intent is clearest when you're the one who created it, you don't control or have insight into what exactly is executing (more important when animating than when dealing with text), and difficult to debug. And yet, occasionally, the easiest, quickest way from point A to B. I'd consider using it for any app I don't anticipate caring about more than a couple of months after its writing, but not much else. EDIT: spelling Doctor w-rw-rw- fucked around with this message at 05:47 on Sep 18, 2014 |
|
#
?
Sep 18, 2014 05:21
|
|
|
Doctor w-rw-rw- posted:Having in the past dealt with its opaque resolution scheduling, and having just dealt with nonsensical and seemingly irrecoverable constraint failure of a layout defined by someone else, I would call it "cool and powerful" in the same way regular expressions are: That's remarkably accurate. edit: Nevermind. No one wants to hear my bitching about auto layout. Suffice it to say I am unhappy with the experience and have found it impossible if you want to animate anything. edit2 with maybe useful info: My constraint animation problem was that you now have to explicitly call [[viewToAnimate superview] layoutIfNeeded] inside of the animation block. If you don't do that, the views just disappear instantly instead of animating. ManicJason fucked around with this message at 05:46 on Sep 18, 2014 |
|
#
?
Sep 18, 2014 05:22
|
|
|
ManicJason posted:I'm learning the hard way that autolayout is a horrible mistake if you have anything remotely complicated or not stock UIKit. I want the last week of my life back. I think I've posted about it a couple times already but man I fuckin hate autolayout. It sounds cool in theory, but any time I've tried to use it it's just made everything significantly more complicated than if I just did the layout myself. I wonder how long we'll be able to avoid it entirely. When I use the new 10.10 NSViewController APIs to present a view controller in a popover or sheet, the view controller shits a bunch of constraints all over my views that are coded to layout manually. I have no clue how it even decides to generate those constraints -- they're translated autoresizing mask constraints but none of the views even have an autoresizing mask set. Depending on how it's set up it'll either complain about unsatisfied constraints and break the app, or just complain that the views still need to be laid out after calling layout. I hope this isn't Apple's way of forcing us towards autolayout. I haven't found a good workaround yet aside from not using the new APIs. Hacks like overriding autolayout properties and methods seem to do nothing or just break things more.
|
|
#
?
Sep 18, 2014 05:46
|
|
|
Taking a break from autolayout discussion for a moment: Ari Grant, from Facebook, presented recently at @Scale 2014 on Facebook's iOS infrastructure: https://www.youtube.com/watch?v=XhXC4SKOGfQ View reuse and major infrastructure performance problems definitely plagued iOS at FB for quite some time, both for the main app and Paper. Replacing Core Data with Mem Models was tremendous for performance and thread affinity problems, and Components seem pretty cool (I wasn't there for the Objective-C version of that).
|
|
#
?
Sep 18, 2014 07:52
|
|
|
Doctor w-rw-rw- posted:Today, I figured out that -[NSNumber isEqualToNumber:] crashes on nil. That is to say: The documented convention is that, when passed nil, -isEqual: returns NO and -isEqualTo*: throws an exception, but this isn't consistent across all of Cocoa.
|
|
#
?
Sep 18, 2014 09:07
|
|
|
Since everyone just loves auto layout, would anyone recommend one of those DSL-like libraries like Masonry? I find my biggest problems when I need to use auto layout in code are:
Something that fixes both of those at once would be fantastic.
|
|
#
?
Sep 18, 2014 20:30
|
|
|
xpost:ultramiraculous posted:Hey, FYI there's vector images in XCode 6 which could really make everything easier.
|
|
#
?
Sep 19, 2014 04:43
|
|
|
pokeyman posted:[url=https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Appendices/Properties.html] Just submit with the status bar showing like everyone has since forever. Or turn the status bar off to take your screenshots. Use QuickTime in Yosemite to take your screenshots and it will show a Perfect Status Bar instead of the real one.
|
|
#
?
Sep 19, 2014 05:52
|
|
|
Perfect indeed, 9:41 AM. That's awesome.
|
|
#
?
Sep 19, 2014 05:59
|
|
|
The "No status bar allowed!" thing is an anachronism from when the status bar was completely separate from the app, and if you cropped it out the App Store would show a Steve-Approved Status Bar. Now that the status bar is just overlaid on top of the app's views, it doesn't really make sense to crop it out. I've submitted multiple updates to an app with the status bar visible in the screenshots and sailed through the approval process. Lots of other apps' screenshots show the status bar. Make a game of it, look at apps on the App Store and try to guess where the developer is from based on the carrier name in the status bar.
|
|
#
?
Sep 19, 2014 06:13
|
|
|
So jumping back into iOS dev after a year long hiatus. Can someone check me on SOP for doing this? I have a NavigationController. Using that, my main screen is a List view, which leads to a Detail view. On the Detail view there is an action you can take which requires a Modal popup. When the Modal is dismissed, I want to go back to the List view, which has now updated to reflect the action performed. So to recap: List -> Detail -> Modal (user performs action here) -> List View I currently have the NavController handling List -> Detail, and the Detail View handling the Modal. Something like: Detail -> implements ModalDelegate List -> implements DetailDelegate So the Modal view sends the ModalDelegate event to the Detail view, dismissing the Modal. The Detail view then sends the DetailDelegate event to the List view, which dismisses the Detail view. Is that correct? Or is there some better way I am missing?
|
|
#
?
Sep 19, 2014 12:06
|
|
|
Thats probably fine for small getting started projects. The standard of practice for app architecture changes drastically with the size of the app, the size of the team, fashion etc. Right now FRP, and MVVM are popular and you can see parts of them within in MVC depending on where you draw the boundaries of responsibilities. Consider a Model/Store layer. Your List view just represents the current state of Lists Members. Your Detail View just represents a List Member, your Modal Edit just dispatches a change request to your Model/Store layer which initiates a redraw of anything currently representing anything that changed. So your in your example the arrows only move in one direction Store -> Views, Collection -> Item. Your navigationcontroller informs the listcontroller what its collection is, and your list informs the detailcontroller what its item is, and your modal editor just issues a change request to the store, which (via various means) cascades downward. One example of something similar is the video linked by Doctor666, even apple experiments with different ways of doing things see WWDC videos which discuss architecture.
|
|
#
?
Sep 19, 2014 13:59
|
|
|
|
| # ? Jun 5, 2024 13:28 |
|
|
ultramiraculous posted:xpost: gently caress yes.
|
|
#
?
Sep 19, 2014 16:35
|
|
