height based
on its contents layout.
> On Mar 9, 2018, at 8:21 AM, Gary L. Wade wrote:
>
> @Cosmo
>
> My collection items contain label, so I don’t know the exact sizes before
> hand.
>
___
Cocoa-dev mailing list (Cocoa-dev@lists.
Where I work we have spent a fair amount of trying unsuccessfully to get
self-sizing collection view cells to work as described by Apple documentation
with UICollectionViews that have any sort of complexity. I would suggest trying
to implement the sizeForItemAtIndexPath delegate method to see if
You might find this site helpful:
http://useyourloaf.com/blog/swift-string-cheat-sheet/
> On Sep 2, 2016, at 2:08 AM, Gerriet M. Denkmann wrote:
>
> How to translate this into Swift (current version, i.e. the one before 3.0):
>
> UITextView *uitv = …
> NSRange selectedRange = uitv.selectedRan
If I understand correctly, simply unchecking the “Is Initial Controller”
checkbox for the viewController in the Storyboard should fix your problem.
> On Nov 26, 2015, at 5:27 AM, Roland King wrote:
>
> I would like to create the main viewcontroller in my
> applicationDidFinishLaunching:withOpt
Is there any chance you have Zombie checking turned on in your scheme settings?
In my experience that might account for what you’ve described.
> On Aug 14, 2015, at 1:29 PM, Richard Kennaway wrote:
>
> I've written an iOS app that, according to Instruments, seems to very slowly
> allocate more
Also not enough time to make specific suggestions, except for checking out this
blog post:
http://natashatherobot.com/ios-autolayout-scrollview/
It recently helped me conquer a scrollview layout issue on iOS.
> On Aug 27, 2015, at 8:07 AM, Jerry Krinock wrote:
>
> In a hurry here, but, I know
Sorry. I was inaccurate in my language. I’m actually calling these methods on
the superclass, not on instances of it.
> On Jun 6, 2015, at 4:58 PM, Graham Cox wrote:
>
>
>> On 7 Jun 2015, at 8:47 am, Cosmo wrote:
>>
>> I should have explained that I’m calling th
Thanks for the response.
> On Jun 6, 2015, at 3:15 PM, Quincey Morris
> wrote:
>
> On Jun 6, 2015, at 14:35 , Cosmo wrote:
>>
>> Can somebody explain to me why I’m getting this different behavior. Is there
>> anything I can do to achieve my goal?
>
>
I’m trying to send messages from a class to one of its subclasses. I have a
method that returns the class I want to forward to. If I use it in the
following manner, it works:
+ (void)logout
{
// subclasses handle it
[[self classToUseForBackend] logout];
}
By setting breakpoints in this
I remember having problems similar to this several months ago, until I switched
from using Google Chrome to Safari. Could that be the issue here?
> On May 28, 2015, at 4:19 AM, Roland King wrote:
>
>
>> On 27 May 2015, at 09:53, Doug Hill wrote:
>>
>> I’ve noticed very long loading times for
A while back I had a similar sounding issue in an iOS project I was working on.
The memory usage kept growing, although I could find no obvious culprits in my
code after hours of exploration. My solution probably doesn’t pertain to you,
but I thought I’d pass it along just in case it’s something
I wonder if anybody can tell me what I might be doing wrong. I used layout
constraints in InterfaceBuilder to define the layout for a UITableView
cell. The cell renders correctly, but I get a warning for each cell
displayed that contains a reference to a "FittingSizeHTarget" constraint
that I did n
Is it just me, or is there something broken with debugging Swift in the Xcode 6
beta? I am running into problems like: local variables that are within scope
not appearing in the debugger’s variables list; values for string variables not
being displayed; no summary for the Quicklook view when try
As somebody who did a lot of development work on early versions of Simple Help
Editor, I’d like to point out a misstatement. It does not require one to write
their own HTML. It does a quite capable job of translating styled text into
HTML, but does offer the ability to handle custom HTML for thi
14 matches
Mail list logo
