|
pokeyman posted:When you said the omission isEqualToManagedObject: wasn't an oversight. I took that to mean you wouldn't implement the method yourself. My assumption is that such a method doesn't exist because managed objects can't logically be equal to other managed objects, so the default pointer comparison is sufficient. I didn't mean to imply that specialized methods are required for every class no matter what. I take advantage of them when they're available and if I know both objects are instances of that class. quote:What's a value class? And what about classes that simply use pointer equality, should those have specialized equality methods? Why not? Apple defines a value object as "an object-oriented wrapper for a simple data element such as a string, number, or date." So things like NSString and other primitive data classes of the Cocoa framework. And, of course, your app might have its own value objects. quote:I imagine you also override isEqual: for those classes. Does isEqual: in turn immediately call your specialized equality methods? Do your specialized equality methods claim increased performance? If I need something more than pointer equality, I follow the convention of implementing a class-specific method and calling that method from -isEqual: if the argument is an instance of that class. If I know two objects are of that class, I skip the check by calling the class-specific method directly. I don't claim increased performance for my particular methods and haven't bothered benchmarking them for that. quote:I feel like we're talking by each other at this point. Thanks very much for the discussion, I've learned a lot. It was fun! Here's a Mike Ash article on implementing equality and hashing. Toady fucked around with this message at 03:03 on Sep 30, 2011 |
# ? Sep 30, 2011 02:56 |
|
|
# ? Jun 1, 2024 05:42 |
|
How do I symbolicate a crash file in Xcode 4?
|
# ? Oct 1, 2011 05:06 |
|
Small White Dragon posted:How do I symbolicate a crash file in Xcode 4? If its not doing it automatically, try using this https://github.com/chrispix/symbolicatecrash-fix
|
# ? Oct 1, 2011 16:51 |
|
Small White Dragon posted:How do I symbolicate a crash file in Xcode 4? Ha! I just taught myself how to do this yesterday. Here are my notes: 1. Make sure you archive the Build Products of the exact version that generated the crash log. 2. Move the crash log, the app bundle, and the .dSYM file into the same directory. 3. Run the symbolicate script. You can make an alias: code:
code:
|
# ? Oct 1, 2011 18:24 |
|
Can someone explain this graphic result to me? I'm making a simple rect background with OpenGL, with different color corners to make a gradient. On my iPad 2, it looks like this: In the simulator, AND the first generation iPad 1, it looks like this: Why the difference? lord funk fucked around with this message at 20:22 on Oct 1, 2011 |
# ? Oct 1, 2011 18:27 |
|
pokeyman posted:If the .m file gets compiled and linked (i.e. has a target in Xcode), the class gains the methods. The .h file simply tells the compiler about the methods defined therein. If you want to keep the category methods out, remove the .m from the target. Correct, the binary is scanned for categories when it gets loaded and the categories are patched in at that time. In fact all of the code included in the target can potentially be compiled into the binary and loaded into memory, even if you never call it or reference it anywhere else.
|
# ? Oct 1, 2011 21:05 |
|
lord funk posted:Can someone explain this graphic result to me? I'm making a simple rect background with OpenGL, with different color corners to make a gradient. On my iPad 2, it looks like this: Insufficient color precision would be my guess. Are you using a 16-bit or 32-bit framebuffer?
|
# ? Oct 1, 2011 22:53 |
|
Doc Block posted:Insufficient color precision would be my guess. Are you using a 16-bit or 32-bit framebuffer? I'm not actually sure how to find out. I'm assuming it's somewhere where I create the framebuffer? Here's the code: code:
|
# ? Oct 1, 2011 23:43 |
|
From what I can remember it's where you make the OpenGL layer or EAGL layer or something. There's an option to have the actual framebuffer (not just a framebuffer object, which is what you're creating in that code snippet) be 16- or 32-bits. Sorry I can't be more specific, I'm not at my dev machine right now. edit: nm, you found it yourself. Doc Block fucked around with this message at 00:10 on Oct 2, 2011 |
# ? Oct 1, 2011 23:57 |
|
I think I found it:code:
|
# ? Oct 2, 2011 00:09 |
|
Who was the llvm guru on here? I think I have a bug where it generates code that fails to select the appropriate branch for some reason (if or switch) but I'm not good enough with ARM assembly to verify. It seems like it might be related to code length too? Compiling with pure GCC seems to produce desired results though.
|
# ? Oct 3, 2011 23:19 |
|
You're probably thinking of rjmccall http://forums.somethingawful.com/showthread.php?threadid=3400187&userid=123851
|
# ? Oct 3, 2011 23:31 |
|
That would be me. Please note that, while it's always possible that this is a compiler bug, it's much more likely that your code is broken in some way that just happens to not explode on GCC.
|
# ? Oct 3, 2011 23:34 |
|
iOS 5 dev chat: Interesting to see that Apple is using the volume button as a camera snapshot button in iOS 5. I seem to remember devs complaining that their apps were rejected if they used the volume buttons for anything other than volume.
|
# ? Oct 4, 2011 21:49 |
|
Speaking of rejected apps, I just had an app rejected (by an automated process) for non-public API use in almost every class (including, apparently, UIKit classes). I'm pretty sure I didn't do anything crazy enough to gently caress everything up, and a cursory google search indicates other people are having the same problem since earlier today, so I imagine it's just something to do with their updates today. Has anyone else had this problem, or even more interestingly, has anyone successfully submitted a binary today?
|
# ? Oct 4, 2011 22:41 |
|
PT6A posted:Speaking of rejected apps, I just had an app rejected (by an automated process) for non-public API use in almost every class (including, apparently, UIKit classes). I'm pretty sure I didn't do anything crazy enough to gently caress everything up, and a cursory google search indicates other people are having the same problem since earlier today, so I imagine it's just something to do with their updates today.
|
# ? Oct 4, 2011 22:46 |
|
Are there any iOS devices that support texture sizes greater than 2048x2048?
|
# ? Oct 5, 2011 00:14 |
|
Issue resolved -- there was a bug in iTunes Connect that didn't allow me (and presumably other people having the same problem) to accept the new contract amendments. That's been fixed, I accepted it, and my binary uploaded fine without any changes.
|
# ? Oct 5, 2011 02:25 |
|
lord funk posted:iOS 5 dev chat: Yeah, this was one of the sticking points in the "Apple is undercutting developers" discussions around the WWDC announcement, along with the builtin apps borrowing features from popular third party tools.
|
# ? Oct 5, 2011 02:34 |
|
kitten smoothie posted:Yeah, this was one of the sticking points in the "Apple is undercutting developers" discussions around the WWDC announcement, along with the builtin apps borrowing features from popular third party tools. I've never understood those complaints. When has Apple been anything but gleeful to implement features it likes regardless of the source? Anyone who isn't aware of this possibility simply isn't paying attention (which is fair enough if you're new to the platform). If anything, the complainers should take it as confirmation that their and Apple's tastes are well-aligned and that their apps will fit in well. And I don't mean that in the trite "imitation is the sincerest form of flattery" sense, but in the "the sole controller of the platform has blessed your work" sense.
|
# ? Oct 5, 2011 03:32 |
|
pokeyman posted:I've never understood those complaints. When has Apple been anything but gleeful to implement features it likes regardless of the source? Anyone who isn't aware of this possibility simply isn't paying attention (which is fair enough if you're new to the platform). If anything, the complainers should take it as confirmation that their and Apple's tastes are well-aligned and that their apps will fit in well. And I don't mean that in the trite "imitation is the sincerest form of flattery" sense, but in the "the sole controller of the platform has blessed your work" sense. Other than that fact that it is an intensely lame thing to do? Apple can only get away with it because they're the only paying game in town. If Android ever got its act together and made the hardware/software work well I suspect there would be a number of iOS developers that head for more friendly pastures.
|
# ? Oct 5, 2011 14:39 |
|
zorm posted:Other than that fact that it is an intensely lame thing to do? Apple can only get away with it because they're the only paying game in town. If Android ever got its act together and made the hardware/software work well I suspect there would be a number of iOS developers that head for more friendly pastures. Why do you consider it "intensely lame"? How likely do you think it is that the act of Android coming together ends with it looking a lot more like iOS, and Google like Apple, in terms of control of the platform?
|
# ? Oct 5, 2011 15:46 |
|
As much as it might suck having Apple poach your good ideas as a developer, consider the alternative: Apple would basically have to sit around, knowing there is an improvement which could easily be made to their platform, and ignore it, making the average user find (and possibly pay for) a 3rd-party app to do it. Speaking as a developer, I say it sucks. Speaking as an iPhone user (the ones who put money in Apple's pockets, and developer's pockets when you get right down to it) I think it's pretty great that Apple continues to improve the user experience on their devices.
|
# ? Oct 5, 2011 16:21 |
|
Quick question: If I provision an iPhone for (generic) development testing, can I still use it as my everyday iPhone or is it now development-only (and if so, what's different about a dev-only iPhone)?
stray fucked around with this message at 17:07 on Oct 5, 2011 |
# ? Oct 5, 2011 16:36 |
|
stray posted:Quick question: If I provision an iPhone for (generic) development testing, can I still use it as my everyday iPhone or is it now development-only (and if so, what's different about a dev-only iPhone)? Yeah, you can use it normally. I've never run a beta version of iOS, but I assume you can use that normally as well if you want (with some added instability, because it's beta).
|
# ? Oct 5, 2011 16:39 |
Holy cow. With automatic reference counting, how much of the memory management is automatically handled now? I'm still really early in learning Objective-C, but I don't need to do any releasing or NSAutoreleasePool stuff (at least in what I'm working on) if it's on when making a new exercise/project.
|
|
# ? Oct 5, 2011 16:51 |
|
If you need to use CoreFoundation objects, you'll still have to retain and release those yourself. You'll also have to watch out for reference cycles, which will cause leaks. Otherwise, it's pretty much taken care of for you.
|
# ? Oct 5, 2011 18:41 |
|
PT6A posted:As much as it might suck having Apple poach your good ideas as a developer, consider the alternative: Apple would basically have to sit around, knowing there is an improvement which could easily be made to their platform, and ignore it, making the average user find (and possibly pay for) a 3rd-party app to do it. Speaking as a developer, I say it sucks. Speaking as an iPhone user (the ones who put money in Apple's pockets, and developer's pockets when you get right down to it) I think it's pretty great that Apple continues to improve the user experience on their devices. They should really be doing the same thing that they did with Siri though, and buy out the app/company that produced it so that the original developers get their fair share. I also view it as "intensely lame" because Apple is essentially outsourcing all of the risk & development time to app developers without paying them. Then if said app developers make something that is successful or a good idea they poach the idea and leave the developers with nothing. Look at Microsoft, the courts and developers have tied their hands over time. They have a hard time adding basic things to their core OS now without huge problems. I agree that this makes for a bad user experience but as a developer it is a huge win. If you look at what Apple has been adding, the only things that are really safe for app developers to develop for iOS are games and apps in extremely vertical markets.
|
# ? Oct 5, 2011 19:05 |
|
zorm posted:They should really be doing the same thing that they did with Siri though, and buy out the app/company that produced it so that the original developers get their fair share. And education apps. They're not making their own, and are in fact heavily promoting 3rd party education apps to schools!
|
# ? Oct 5, 2011 19:39 |
|
What is configd, why is it taking so much memory on my iPad, and why does my app get jettisoned when it tries to launch but others don't? Here is the "LowMemory-2011-10-05-140147.log" it makes: quote:Incident Identifier: 9EF6760E-D92B-48A2-B616-4A2B36F970A4
|
# ? Oct 5, 2011 20:14 |
|
zorm posted:I also view it as "intensely lame" because Apple is essentially outsourcing all of the risk & development time to app developers without paying them. You mean aside from the $3 billion paid to developers since the App Store opened. Not to mention said developers would have no job without Apple expanding the mobile app market from pittance to $billions. iOS developers are well-compensated for their time and effort for any app they can sell. Apple boosts tons of third-party apps in commercials, websites, and iTunes all for free, and the flip side is if you do a really good job your feature might be immortalized in the OS itself. I can understand an initial negative reaction when your app suddenly becomes irrelevant, but that's always a risk on any platform. There's no guarantee that your app is forever safe to earn you your 'fair share', and I'm not sure why you think you're entitled to any such thing.
|
# ? Oct 5, 2011 23:33 |
|
Well I guess the old "nuclear option" of an email to steve jobs when poo poo goes haywire with the appstore that once saved my business isn't available anymore.
|
# ? Oct 6, 2011 03:22 |
|
edit: Wrong thread, not YOSPOS
|
# ? Oct 6, 2011 03:40 |
|
Martytoof posted:edit: Wrong thread, not YOSPOS
|
# ? Oct 6, 2011 03:42 |
|
zorm posted:
Sounds like there should be some sort of legal protection for the research and development of software... some sort of software... patent...
|
# ? Oct 6, 2011 05:03 |
|
Software patents are bullshit, lets not talk about those.
|
# ? Oct 6, 2011 05:52 |
|
Figured I'd round up some posts about Steve from developers. These are just the blogs I follow so post any others you have. Steven Frank Neven Mrgan Peter Ammon Jeff LaMarche Marco Arment Gus Mueller
|
# ? Oct 6, 2011 10:22 |
|
EDIT: I'm really dumb. I have fixed this problem by myself.
Heisenberg1276 fucked around with this message at 19:50 on Oct 7, 2011 |
# ? Oct 7, 2011 17:34 |
|
I got tired of not having a good image of accelerometer / gyroscope motions for the iPad, so I made my own. Figured I'd share if anyone else wanted it for a manual or something: Illustrator file and PDF: https://rapidshare.com/files/2834131909/ipad-device-motion-vector.zip
|
# ? Oct 7, 2011 18:18 |
|
|
# ? Jun 1, 2024 05:42 |
|
lord funk posted:I got tired of not having a good image of accelerometer / gyroscope motions for the iPad, so I made my own. Figured I'd share if anyone else wanted it for a manual or something: Awesome, thanks!
|
# ? Oct 7, 2011 20:25 |